Bug 148229

Summary: GDM doesn't restart when X server is killed
Product: [openSUSE] SUSE Linux 10.1 Reporter: Andreas Kleen <ak>
Component: GNOMEAssignee: Dan Winship <danw>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: debug log file

Description Andreas Kleen 2006-02-04 17:00:25 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.
Comment 1 JP Rosevear 2006-02-04 18:12:03 UTC 
Are you killing it with ZAP? We've seen this occasionally, but not consistently.  I could not duplicate this time on beta3.
Comment 2 Andreas Kleen 2006-02-04 18:26:38 UTC 
With the hotkey yes. I've seen it several times - happens pretty consistently
here.
Comment 3 JP Rosevear 2006-02-06 12:39:47 UTC 
Any specific hardware or just x86?
Comment 4 Andreas Kleen 2006-02-06 12:43:56 UTC 
x86-64 on a Intel Glenwood system with Dual Core/Hyper Threading (4 threads)
and a Radeon card. Probably falls under your "just x86".
Comment 5 JP Rosevear 2006-02-06 13:02:36 UTC 
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?
Comment 6 Andreas Kleen 2006-02-07 21:58:55 UTC 
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)
Comment 7 Andreas Kleen 2006-02-07 22:01:10 UTC 
Created attachment 66886 [details]
debug log file

includes multiple tries, only the last ones are really showing 
the issue.
Comment 8 Dan Winship 2006-03-23 21:59:14 UTC 
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.)
Comment 9 Andreas Kleen 2006-03-23 23:24:08 UTC 
I need a x86-64 rpm
Comment 11 Andreas Kleen 2006-03-27 20:05:35 UTC 
I can produce the problem anymore with a newer beta and your gnome session.
So I suppose it has been fixed somehow.
Comment 12 Dan Winship 2006-03-27 20:16:05 UTC 
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.