gnome-settings-daemon SIGABRT when gnome-session goes down

[Jason Warner]

just upgrade...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-daemon 3.2.2-0ubuntu14
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 1 11:45:15 2012
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
Title: gnome-settings-daemon crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2011-12-14 (48 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __GI___assert_fail (assertion=0x7f3fb95bfad8 "!xcb_xlib_threads_sequence_lost", file=<optimized out>, line=273, function=<optimized out>) at assert.c:81
 poll_for_event (dpy=<optimized out>) at ../../src/xcb_io.c:270
 poll_for_response (dpy=0xf68e20) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=0xf68e20, mode=<optimized out>) at ../../src/xcb_io.c:362
 XPending (dpy=0xf68e20) at ../../src/Pending.c:55

[Launchpad Janitor (janitor)]

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

[Christopher Kyle Horton (christhehorton)]

I got this crash when trying to reveal my launcher. The system kicked me back out to the login screen and it showed me this crash window a little while after logging back in.

[Robert Roth (evfool)]

Looks like a duplicate of bug #833694.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

[Octavian Damiean (mainerror)]

I can confirm what Christopher said. I've also tried to reveal the launcher which resulted in a X crash.

[psypher (psypher246)]

Compiz and gome-settings crash on me about 3-5 times a day while doing various tasks on the desktop. Clicking a indicator applet, launching the dash or launcher or just moving the mouse. Has been ongoing for about 3 weeks now. I loose work frequently and crashes my virtual machines when it bombs

[Bryce Harrington (bryce)]

Note the error here is an _assertion_ in libxcb rather than a segfault. That implies that it's not a bug in the library itself, but rather that the library is catching a fault that probably originated elsewhere in the stack.

Possibly this is similar to or even the same as bug #833694, which appears to be fixed upstream but not in ubuntu. In particular see this comment on the upstream bug, which explains what happened in the client code that cause this assertion to get tripped: https://bugzilla.gnome.org/show_bug.cgi?id=657255#c8

[Bryce Harrington (bryce)]

Bumping back to g-s-d since it's likely an error in that codebase, and quite likely is a dupe of 833694, but someone should test the upstream fix first.

[Alan Bell (alanbell)]

I have had this a number of times when moving the mouse between monitors, the mouse cursor freezes on the transition and all control is lost, can't ctrl+alt+f1 to get to a terminal even. I can ssh into the machine and restart lightdm, but restarting just unity did nothing. I think this has happened since the stickyness or pressure between monitors got added to do with the launcher reveal.

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

Yes, it seems to be related to the edge. I experience it when pushing towards the edge in order to reveal the launcher, even on single-monitor systems.

[psypher (psypher246)]

I experience this about once a day and it has nothing to do with the edge. Just moving the mouse anywhere, or opening fullscreen videos.

[Roman Yepishev (rye)]

This turns out to be not an actual bug in gsd, as the latter is crashes when X server goes away unexpectedly.

This is what was found in the syslog:
Mar 1 23:46:03 delorean gnome-session[1667]: ******************* START ********************************
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 0: /usr/bin/gnome-session() [0x419bf7]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 1: /usr/bin/gnome-session() [0x419fda]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 2: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7fc5f5d96cb0]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35) [0x7fc5f4b00445]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b) [0x7fc5f4b03bab]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 5: /lib/x86_64-linux-gnu/libc.so.6(+0x2f10e) [0x7fc5f4af910e]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 6: /lib/x86_64-linux-gnu/libc.so.6(+0x2f1b2) [0x7fc5f4af91b2]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 7: /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3d603) [0x7fc5f788b603]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 8: /usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3d621) [0x7fc5f788b621]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 9: /usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5d) [0x7fc5f788bd4d]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 10: /usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x5d) [0x7fc5f787d41d]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 11: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x4d824) [0x7fc5f693a824]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 12: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x183) [0x7fc5f4eccb73]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 13: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x480d6) [0x7fc5f4ecd0d6]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 14: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a) [0x7fc5f4ecd59a]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 15: /usr/lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main+0x8d) [0x7fc5f6d0784d]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 16: /usr/bin/gnome-session() [0x40b668]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 17: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7fc5f4aeb76d]
Mar 1 23:46:03 delorean gnome-session[1667]: Frame 18: /usr/bin/gnome-session() [0x40b8d5]
Mar 1 23:46:03 delorean gnome-session[1667]: ******************* END **********************************

<seb128> gnome-session/gdm-signal-handler.c: syslog (LOG_CRIT, "******************* START ********************************");
<seb128> gnome-session is the one preventing apport

[Giorgi Gzirishvili (giogziro95)]

I was just working in the Inkscape, clicked on unity global menu item and gnome-session crashed.

[Achim Behrens (k1l)]

It happens to me too, while just running the mouse form the right screen to the left one. when hitting the edge and the launcher should pop out xserver crashes.
i cant reproduce it on purpose. but like every 10th switch from monitors it crashes.

[psypher (psypher246)]

I no longer get the error popping up, yet about 2 - 3 times a a day my dual monitor setup switches back to low res mirror setup:

It does not happen when I am moving between screens. My hand can be off the mouse and this will occur

 tail -f /var/log/Xorg.0.log
[ 5661.656] (II) XKB: reuse xkmfile /var/lib/xkb/server-F80C2F641F2CD3A57342CD066CADC9C6FC55B1A4.xkm
[ 5679.086] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 5679.582] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 5679.582] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 5679.807] (II) Quirked EDID physical size to 0x0 cm
[ 19356.562] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 19356.562] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 19356.562] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 19356.780] (II) Quirked EDID physical size to 0x0 cm
[ 19358.370] resize called 1024 768

[Sebastien Bacher (seb128)]

Ok, I'm lowering the bug there, it seems like g-s-d just got unhappy when the session closes by hitting a bug (in opposite of being closed the standard way), comments suggests the g-s-d bug prompting was just a side effect of running into gnome-session or xorg segfaulting, those are the real issues and should be reported independently if they still happen. It's likely that part of the issue was due to the xorg barrier and fixes went there so it might be solved in the current versions

[psypher (psypher246)]

Sebastian,

With regards to my issue of my multi monitor setup breaking and reverting back to low res mirror setup, would you say that is Xorg or gnome-session? I am not sure under what to log it and what info to provide, as the ONLY errors that I receive, when this happens, in my logs are:

==> /var/log/kern.log <==
Mar 26 15:00:11 hostname kernel: [16224.830078] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
Mar 26 15:00:17 hostname kernel: [16230.185470] [drm] nouveau 0000:02:00.0: PMFB2_SUBP0: 0x037f0040
Mar 26 15:00:17 hostname kernel: [16230.185475] [drm] nouveau 0000:02:00.0: PMFB2_SUBP1: 0x037f0040

==> /var/log/Xorg.0.log <==
[ 16238.183] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16238.183] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16238.183] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16238.401] (II) Quirked EDID physical size to 0x0 cm
[ 16238.742] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16238.742] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16238.742] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16238.961] (II) Quirked EDID physical size to 0x0 cm
[ 16240.549] resize called 1024 768
[ 16245.573] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16245.573] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16245.573] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16245.790] (II) Quirked EDID physical size to 0x0 cm
[ 16246.158] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16246.158] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16246.158] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16246.377] (II) Quirked EDID physical size to 0x0 cm
[ 16246.700] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16246.700] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16246.700] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16246.920] (II) Quirked EDID physical size to 0x0 cm
[ 16247.727] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16247.727] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16247.727] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16247.947] (II) Quirked EDID physical size to 0x0 cm
[ 16248.267] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16248.267] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16248.267] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16248.484] (II) Quirked EDID physical size to 0x0 cm
[ 16278.631] (II) NOUVEAU(0): EDID vendor "LGD", prod id 541
[ 16278.631] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 16278.631] (II) NOUVEAU(0): Modeline "1600x900"x0.0 99.95 1600 1648 1696 1824 900 902 905 912 +hsync -vsync (54.8 kHz)
[ 16278.852] (II) Quirked EDID physical size to 0x0 cm

==> /var/log/kern.log <==
Mar 26 15:00:59 hostname kernel: [16...

[Sebastien Bacher (seb128)]

@psypher your issue seems a different one and rather an xorg issue

[psypher (psypher246)]

@Sebastien

Thanks, I have updated my original bug to reflect the extra info and that it's not a duplicate of this bug. Would you be able to confirm that I have supplied all the required info? I would really like to get this bug fixed asap, before stable release, as it detracts from all the hard work being done on multi monitor setups and is quite annoying. I am a power user of multiple monitors and having to fix the setup over and over every day is quite frustrating.

Thanks

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release