gdm won't restart after zapping x

Bug #91818 reported by Colin
4
Affects Status Importance Assigned to Milestone
gdm (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

After zapping X (ctrl + alt = backspace) GDM has to manually killed and restarted. I am using the nvidia-glx driver + beryl on Feisty with the latest updates applied.

Colin (colinnc)
description: updated
Revision history for this message
Brian Murray (brian-murray) wrote :

The beryl packages are not from the official Ubuntu repositories, and as such are not supported here. Please either report this bug upstream at http://bugs.beryl-project.org/ or try to reproduce the bug without using beryl. Thanks!

Revision history for this message
Martin Pool (mbp) wrote :

This happened to me on feisty, and I am not using either nvidia or beryl (or compiz). So I'm reattributing it to gdm.

I had to zap the server because my gnome-panel had crashed. (Well, I guess I could have tried killing the gnome-session instead, but gdm ought to be robust against the server unexpectedly exiting.)

I couldn't seem to get much debugging information, except this from the daemon.log:

Mar 22 09:58:20 hope gdm[5298]: gdm_cleanup_children: child 5306 crashed of sign
al 9
Mar 22 09:58:20 hope gdm[5298]: gdm_cleanup_children: Slave crashed, killing its
 children

gdb shows

(gdb) bt
#0 0xb75f9903 in ?? () from /lib/tls/i686/cmov/libc.so.6
#1 0x080a1410 in ?? ()
#2 0x080934e0 in ?? ()
#3 0x080a1418 in ?? ()

and strace shows it repeatedly

rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0

Changed in beryl-core:
status: Rejected → Confirmed
Revision history for this message
Martin Pool (mbp) wrote :

This is reproducible for me at the moment. I should also mention that it's the gdb child process that spins, using 100% of cpu. I can recover by either killing that process, or restarting gdm as a whole.

Here's my X log in case it helps.

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

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gdm:
assignee: brian-murray → desktop-bugs
importance: Undecided → Low
status: Confirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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