[Bug 238652] New: kdm restarts X in endless loop
https://bugzilla.novell.com/show_bug.cgi?id=238652 Summary: kdm restarts X in endless loop Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers@suse.de ReportedBy: lnussel@novell.com QAContact: qa@suse.de For some reason my X server didn't start up anymore when run from kdm maybe due to some quirk with nvidia driver. Anyways kdm didn't detect that there is something wrong and continuously restarted X. Only after I pressed ctrl-alt-backspace a couple of times kdm gave up. Maybe there is some code path in kdm that doesn't lead to giving up? Jan 25 11:53:54 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:53:54 tripoli kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jan 25 11:53:54 tripoli kernel: agpgart: Device is in legacy mode, falling back to 2.x Jan 25 11:53:54 tripoli kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Jan 25 11:53:54 tripoli kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode Jan 25 11:53:56 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:53:59 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:01 tripoli kernel: eth0: no IPv6 routers present Jan 25 11:54:01 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:04 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:07 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:07 tripoli kernel: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. Jan 25 11:54:07 tripoli kernel: agpgart: Device is in legacy mode, falling back to 2.x Jan 25 11:54:07 tripoli kernel: agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode Jan 25 11:54:07 tripoli kernel: agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode Jan 25 11:54:09 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:11 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:14 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:17 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:19 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:22 tripoli kdm[3277]: X server for display :0 terminated unexpectedly Jan 25 11:54:25 tripoli kdm[3277]: X server for display :0 terminated unexpectedly .. Jan 25 12:08:37 tripoli kdm: :0[5124]: IO Error in XOpenDisplay Jan 25 12:08:37 tripoli kdm[4832]: Display :0 cannot be opened Jan 25 12:08:37 tripoli kdm[4832]: Unable to fire up local display :0; disabling. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652 dmueller@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com ------- Comment #1 from dmueller@novell.com 2007-01-25 07:12 MST ------- Jan 25 12:08:37 tripoli kdm[4832]: Unable to fire up local display :0; disabling. even after that line in the log it started the x server ?! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | ------- Comment #2 from lnussel@novell.com 2007-01-25 07:21 MST ------- No of course not. That's the point where I manually intervened by hammering the system with ctrl-alt-backspace until kdm gave up. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652 coolo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lnussel@novell.com ------- Comment #3 from coolo@novell.com 2007-01-25 08:21 MST -------
From /opt/kde3/share/config/kdm/kdmrc
[X-:*-Core] # How often to try to run the X-server. Running includes executing it and # waiting for it to come up. # Default is 1 #ServerAttempts=1 Can you please check if setting it to e.g. 2 changes anything? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|lnussel@novell.com | ------- Comment #4 from lnussel@novell.com 2007-01-25 09:24 MST ------- doesn't help. It's the wrong place in the code anyways. I found out that the X server crashes when a client connects that uses opengl (was caused by overwritten libglx), simpler clients like xterm don't cause a crash. Ie the XOpenDisplay kdm does works and it assumes the server is running. Then it runs the greeter which crashes the server. In the ReapChildren function only crashes of the watcher process (I guess that -:0 thing) are checked for too frequent restarts. Crashes of the xserver itself are not counted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652 dmueller@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |coolo@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=238652#c5 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Stephan Kulow <coolo@novell.com> 2007-07-04 07:34:26 MST --- ok, after staring at the bug for a half year, I decided I won't care. It's not nice, but it doesn't sound like a likely problem that's causing it. I filed http://bugs.kde.org/show_bug.cgi?id=147538 though in case Oswald thinks differently. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com