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

[Pedro Villavicencio]

Binary package hint: gnome-settings-daemon

crashed while log in, I'm using the Inverted theme.

ProblemType: Crash
Architecture: i386
Date: Mon Aug 4 10:54:51 2008
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
NonfreeKernelModules: ath_hal
Package: gnome-settings-daemon 2.23.5-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-settings-daemon
StacktraceTop:
 gdk_x_error (display=0x8065d20, error=0xbfcee048)
 xkl_process_error () from /usr/lib/libxklavier.so.12
 _XError () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XGetWindowProperty () from /usr/lib/libX11.so.6
Title: gnome-settings-daemon crashed with signal 5 in gdk_x_error()
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

[Apport retracing service (apport)]

StacktraceTop:gdk_x_error (display=0x8065d20, error=0xbfcee048)
xkl_process_error (dpy=0x8065d20, evt=0xbfcee048)
_XError (dpy=0x8065d20, rep=0x81d72d8)
_XReply (dpy=0x8065d20, rep=0xbfcee13c, extra=0, discard=0)
XGetWindowProperty (dpy=0x8065d20, w=23068673, property=39,

[Pedro Villavicencio (pedro)]

After latest updates it doesn't happens anymore for me. May the subscriber of the duplicate can confirm this? thanks.

[DarkMageZ (darkmagez)]

doesn't appear to be happening anymore here as well.

[lightningserpent (tim-lightningserpent)]

my appearance settings do not completely apply. if i click appearance it generates an error about bonobo or KDE application running. if i click OK the appearance box opens if i then close it and then re-open it i do not get an error and my theme applies. i can run the gnome-settings-daemon command from the command prompt and my theme will apply that way. how can i avoid having to do these things and have my theme work properly

[Sebastien Bacher (seb128)]

There is some duplicate using GNOME 2.23.6, sent upstream on http://bugzilla.gnome.org/show_bug.cgi?id=546767

[Samuel Lidén Borell (samuellb)]

This happened for me when I logged in today so it's not fixed. I also got a lot of error messages about panel programs that exited unexpected. But when I logged out and logged in again it worked as it should.

[Atanas Atanasov (thenasko)]

It happened to me today after I restarted due to updated. I am using the Human theme.

[Henry S. (snowball2050-gmail)]

me too

[Pedro Villavicencio (pedro)]

this is fixed in Intrepid with gnome-desktop 2.24.0

[Nizar Kerkeni (nizarus)]

This bug is marked as fixed, but i still have the same issue on jaunty : https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/327547

[Hew (hew)]

Reopened, there are lots of Jaunty dupes appearing.

[Sebastien Bacher (seb128)]

there is no indication the jaunty issue is the same crasher don't reopen closed bugs

[Hew (hew)]

Jaunty issue taken to bug 321041

[Sebastien Bacher (seb128)]

the bug is fixed the jaunty issue has a new bug

[Sebastien Bacher (seb128)]

could somebody having the issue in jaunty get a stacktrace using gdb --sync?

[wavded (wavded)]

I'm getting this error in Karmic Alpha 4 - after login

[Chris Coulson (chrisccoulson)]

Please open a new bug report if you're still experiencing this issue in Jaunty or Karmic

[Arnaud Faucher (arnaud-faucher)]

Bug #413163 in Karmic.

However, Launchpad automatically marks Karmic bugs as duplicates of bug #254671, and removes all apport attachments...

[Matt Eskes (matt.eskes-deactivatedaccount)]

Still getting the error on Karmic Alpha 4

and like #20 stated every time I try to submit for *this* bug, the samething that happens to him happens to me.

I guess the "Bug must not exist" any more.

[Chris Coulson (chrisccoulson)]

There is a bug - it's bug 413163 as Arnaud pointed out. We're currently investigating the new bug - I have a reasonable idea of what sequence if events trigger it now, and a possible workaround too.

[asabjorn (andreas-saebjoernsen)]

I'am still experiencing this problem when running a fully updated and dist-upgraded Natty in a an instance of the latest VMWare Fusion.