gnome-settings-daemon crashed with signal 5 in _XReply()

Bug #903973 reported by Francesco Fumanti
372
This bug affects 53 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
High
Chris Coulson
Precise
Invalid
High
Chris Coulson
xorg-server (Ubuntu)
Fix Released
High
Chris Halse Rogers
Precise
Fix Released
High
Chris Halse Rogers

Bug Description

The crash happened right after logging in. I launched the onscreen keyboard Onboard and the Synaptic Package Manager; but I don't know whether it is related to the bug occurring.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Dec 13 23:09:36 2011
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowAttributes () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to precise on 2011-12-09 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Francesco Fumanti (frafu) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XGetWindowAttributes (dpy=0x11bea10, w=<optimized out>, attr=<optimized out>) at ../../src/GetWAttrs.c:149
 xkl_engine_select_input_merging (engine=0x132ada0, win=37748737, mask=6291456) at xklavier.c:459
 xkl_engine_process_create_window_evt (engine=0x132ada0, cev=0x7fff5fed5240) at xklavier_evt.c:465
 xkl_engine_filter_events (engine=0x132ada0, xev=0x7fff5fed5240) at xklavier_evt.c:52
 gsd_keyboard_xkb_evt_filter (xev=<optimized out>, event=<optimized out>) at gsd-keyboard-xkb.c:735

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
tags: added: bugpattern-needed
Revision history for this message
Steve Langasek (vorlon) wrote :

I think I've just run into this bug; we'll wait for the retracer to confirm it. But this looks like a recent regression somewhere in the X stack that's causing a lot of duplicates, so marking as 'high' accordingly.

Changed in gnome-settings-daemon (Ubuntu):
importance: Medium → High
Revision history for this message
Sebastien Bacher (seb128) wrote :

Chris, you debugged similar issues before, do you remember what was useful in such cases? Do we need a sync version of the stacktrace or the .xsession-errors after the issue?

visibility: private → public
Changed in gnome-settings-daemon (Ubuntu Precise):
assignee: nobody → Chris Coulson (chrisccoulson)
Revision history for this message
Sebastien Bacher (seb128) wrote :

(note that --sync got replaced by GDK_SYNCHRONIZE=1 use nowadays, if a sync stacktrace is required)

it seems that the issue started some weeks ago but g-s-d didn't change a lot, could be something else in the stack...

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

The crash is because XGetWindowAttributes is throwing a BadMatch error, which is unexpected. It will throw a BadMatch error (from dixLookupWindow) if the specified window isn't really a window. This might happen if a window is destroyed and replaced with a drawable of the same ID whilst gnome-settings-daemon is handling the original CreateNotify event.

This looks like it's basically the same issue as https://bugs.freedesktop.org/show_bug.cgi?id=23562, except with XGetWindowAttributes instead of XGetWindowProperty.

Perhaps XGetWindowAttributes needs a similar fix?

(Subscribing the other Chris for a second opinion)

Changed in xorg-server (Ubuntu Precise):
assignee: nobody → Chris Halse Rogers (raof)
importance: Undecided → High
status: New → Confirmed
Changed in xorg-server (Ubuntu Precise):
status: Confirmed → In Progress
Revision history for this message
Chris Halse Rogers (raof) wrote :

Urgh. It looks like the patch you originally submitted upstream is more correct than the patch that got committed - all manner of window calls are broken, not just XGetWindowAttributes.

Let's see if the xorg-devel mailing list agrees.

Revision history for this message
Sebastien Bacher (seb128) wrote :
Revision history for this message
Graham Lucking (lucking) wrote :

I have not had gnome session daemon crash for a long time. In the past it was due to obsolete packages and so was not reportable, but easily fixed. This time I ran Update Manager to get the daily updates. This completed without any problems but as it included a kernel update, I rebooted and as soon as the desktop appeared Gnome setting daemon crashed. And this time it was reportable.

Revision history for this message
Brian Murray (brian-murray) wrote :

Bug 907052 may be a duplicate of this one.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Bug 907052 looks like it's a different issue

Revision history for this message
Sebastien Bacher (seb128) wrote :

closing the g-s-d part it seems an xorg issue and the fix is pending commit

Changed in gnome-settings-daemon (Ubuntu Precise):
status: Confirmed → Invalid
Changed in xorg-server (Ubuntu Precise):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xorg-server - 2:1.11.3-0ubuntu8

---------------
xorg-server (2:1.11.3-0ubuntu8) precise; urgency=low

  * debian/patches/224_return_BadWindow_not_BadMatch.diff:
    - Fix the error values of a whole slew of window-related calls.
      Fixes some gnome-settings-daemon aborts in XLib (LP: #903973)
 -- Christopher James Halse Rogers <email address hidden> Mon, 23 Jan 2012 16:09:29 +1100

Changed in xorg-server (Ubuntu Precise):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.