Bugzilla – Bug 148229
GDM doesn't restart when X server is killed
Last modified: 2006-03-27 20:16:05 UTC
When the X server is killed (either during gdm or during a session) then the X server doesn't restart in runlevel 5. It should and always did in previous releases.
Are you killing it with ZAP? We've seen this occasionally, but not consistently. I could not duplicate this time on beta3.
With the hotkey yes. I've seen it several times - happens pretty consistently here.
Any specific hardware or just x86?
x86-64 on a Intel Glenwood system with Dual Core/Hyper Threading (4 threads) and a Radeon card. Probably falls under your "just x86".
This might be related to bug 139592 which has reappeared. Could you edit /etc/opt/gnome/gdm/gdm.conf, go to the [debug] section and set Enable=true init 3, init 5 and then kill it and attach relevant syslog portions?
I played around a bit with it. It only happens when you log into GNOME (not with KDE) and wait until the desktop has fully loaded and the zap the x server. And then what happens is not that GDM doesn't restart, but you have to wait a minute or so looking at the console until it restarts (i didn't wait that long at the first report, sorry)
Created attachment 66886 [details] debug log file includes multiple tries, only the last ones are really showing the issue.
Could you please try installing this package: http://w3.suse.de/~danw/gnome-session-2.12.0-79.i586.rpm And then log in, zap the server (noting what time it was when you did that), wait for gdm to restart, and then attach your ~/.xsession-errors file to this bug. (That gnome-session package has extra debugging info that will hopefully help track down what's happening.)
I need a x86-64 rpm
http://w3.suse.de/~danw/gnome-session-2.12.0-83.x86_64.rpm
I can produce the problem anymore with a newer beta and your gnome session. So I suppose it has been fixed somehow.
Ugh. OK, well, you don't want that gnome-session rpm for normal use. It will fill up your ~/.xsession-errors with useless debug info.