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

[John Carlyle-Clarke]

Binary package hint: gnome-settings-daemon

This happened after updating my Karmic Alpha 4 install to more or less Alpha 5, and rebooting.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Sep 4 16:25:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Package: gnome-settings-daemon 2.27.91-0ubuntu1
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_log_domain_get_handler_L (
 IA__g_logv (log_domain=<value optimised out>, log_level=-1074778836,
 _gdk_region_get_xrectangles (region=0x9c877c0,
 xkl_process_error () from /usr/lib/libxklavier.so.15
 _XError () from /usr/lib/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in g_log_domain_get_handler_L()
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner vboxusers video

[Apport retracing service (apport)]

StacktraceTop:_gdk_region_get_xrectangles (region=0x9c877c0,
xkl_process_error (dpy=0x9c877c0, evt=0xbff02ebc)
_XError (dpy=0x9c877c0, rep=0x9d38920)
_XReply (dpy=0x9c877c0, rep=0xbff02fd0, extra=0, discard=0)
XGetWindowProperty (dpy=0x9c877c0, w=8388612, property=416,

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?
 * Do you still get the issue?

 This will help us to find and resolve the problem.

[John Carlyle-Clarke (jpcc)]

Hi. I've not been able to reproduce this bug and haven't seen it again since the one time that it occured.

[Chris Coulson (chrisccoulson)]

What version of xorg-server were you running at the time of the crash? This issue was resolved in 2:1.6.3-1ubuntu5 with this change:

xorg-server (2:1.6.3-1ubuntu5) karmic; urgency=low

  * Add 185_dix_badwindow.patch: dixLookupWindow may return BadMatch if
    the window in question isn't actually a window. In this case,
    GetProperty needs to return BadWindow - not BadMatch. Fixes unexpected
    crash in some GNOME applications not expecting to get BadMatch returned
    from this function call.
    (LP: #321041)

[Chris Coulson (chrisccoulson)]

Oops, I think our comments collided there ;)

I'll close this then, as this bug is resolved in Karmic (well, it doesn't crash anymore)

[John Carlyle-Clarke (jpcc)]

Agreed. Thinking some more about it, this crash happened a *lot* (every time I booted) in the Alpha 3/4 stage. Since updating to Alpha 5 or thereabouts it has not happened once. So my perception is that it has been fixed.