http://bugzilla.novell.com/show_bug.cgi?id=540482 User vuntz@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=540482#c70 --- Comment #70 from Vincent Untz <vuntz@novell.com> 2009-10-15 11:33:28 MDT --- (In reply to comment #68)
(In reply to comment #65)
Sorry about the question: are you pretty sure? This because the chvt to VT1 in /etc/init.d/rc interferes with the X-Servers VT switch.
I've never seen gdm start on something lower than vt7. I've seen it on vt7, vt8, and maybe also vt9, but that's all. So my understanding of the code and my experience makes me pretty sure (let's say 95% sure), yes. (In reply to comment #69)
(In reply to comment #66)
Failsafe moide means normally use an XTerm as session controlling process. That is that no X-Server will be (re)started on shutdown. The question is why GDM (re)start an X-Server in case of system shutdown. It should no do that as this not only may lock chvt but also takes system resources during reboot/halt procedure.
Here's what's happening: + gnome-session tells ConsoleKit to reboot + ConsoleKit call "shutdown -r now" + gnome-session exits + gdm sees that the user session has ended and so restarts a new greeter So, yes, gdm restarts a new X server because it's not aware of what ConsoleKit did and I'm not sure ConsoleKit has any way to tell it about this. However, I still don't see why gdm has to be aware of this. I see how having it aware of this would make this work, but this feels like a workaround to me, since I imagine the issue could happen in other cases. As far as I know, there's no way to tell gdm to not restart. We could possibly look at not attempting a restart of the interface if runlevel is now 0 or 6, but that might again be racy since the runlevel could be changed after that... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.