GNOME Bugzilla – Bug 572141
X Error on startup
Last modified: 2010-10-13 17:21:34 UTC
Steps to reproduce: Users report getting the crash notification on login. Stack trace: .
+ Trace 212627
Thread 1 (process 20265)
Other information: From https://bugs.launchpad.net/bugs/321041 First reported with gnome-settings-daemon 2.25.3-0ubuntu1
Quite probably a dupe of bug 546767 (which may not be a duplicate after all), but hard to tell. Stacktraces for XErrors that have been created without the --sync parameter to the crashing application are pretty much useless, unfortunately. You need to get one of the users to run gdb --args .../g-s-d --sync then break in gdk_x_error, and post the result of a "bt full". The output of --debug might be helpful, too.
There have been no reports of this bug since 2.26, it looks like the problem has disappeared. The downstream report has been closed.
Thanks for the heads-up.
Created attachment 137233 [details] gdb output
Created attachment 137234 [details] gsd output
Please reopen. It still happens in 2.26.1 (Ubuntu jaunty). I have attached a sync’ed backtrace and --debug output. Upstream report is at https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/390875.
Created attachment 137246 [details] gdb output with more debug symbols
That trace is still missing symbols from gsd itself. You also need to run gsd with --sync to get a meaningful trace.
Created attachment 137253 [details] gdb output with all symbols
gsd is being started like this /usr/lib/gnome-settings-daemon/gnome-settings-daemon --no-daemon --sync --debug
Hm. What version of libxklavier is that?
It’s libxklavier12 version 3.9-0ubuntu1.
Sergey? Any ideas? Looks like xklavier to me.
Jens - you might want to take a look at https://bugs.freedesktop.org/show_bug.cgi?id=23562, which describes what I think is a bug in Xorg (or a bug in the xlib documentation), which triggers the crash here.
Chris, even if that's the case I'd still argue that there's a problem in gsd, too. It shouldn't reference destroyed windows.
Jens - I agree, but I think the problem is in libxklavier and not gsd
Well, that I agree with. ;-) Calling Sergey...
We are discussing this on IRC
*** Bug 587296 has been marked as a duplicate of this bug. ***
(In reply to comment #18) > We are discussing this on IRC And what came out of it?
Seems that the bug was ultimately solved, or was a problem in libxklavier.