Bug 121903

hmm, pretty complex. If you have that stuck X cursor: please tar up 
~/.xession-errors, /var/log/kdm.log /var/log/Xorg*.log /var/log/messages 
 
we should concentrate on that one first. I somehow suspect your kernel oopses 
and leaves the system inconsistent from what you describe. 

Should I tar up the logs while KDE/KDM is still hangine, or can I kill the X
server and then tar up the logs?

Files attached.

Created attachment 54215 [details]
kdm.log

Created attachment 54216 [details]
xorg.0.log

Created attachment 54217 [details]
xorg.1.log

Created attachment 54218 [details]
xorg.99.log

Created attachment 54219 [details]
messages log

Created attachment 54220 [details]
xsession-errors

Created attachment 54221 [details]
xsession-errors

Created attachment 54222 [details]
the REAL xsession-errors

Please use the last xsession-errors, I submitted the wrong one 2 times :(

The only thing that looks halfway interesting is this piece from your messages (#8 - all others are just pointing out your X server stoped, not KDE):

Oct 16 23:46:05 r098088 su: (to root) michael on /dev/pts/2
Oct 16 23:46:16 r098088 kernel: st: Version 20050501, fixed bufsize 32768, s/g segs 256
Oct 16 23:47:33 r098088 syslog-ng[4401]: SIGHUP received, restarting syslog-ng
Oct 16 23:47:34 r098088 syslog-ng[4401]: new configuration initialized
Oct 16 23:48:59 r098088 syslog-ng[4401]: Changing permissions on special file /dev/xconsole
Oct 16 23:48:59 r098088 syslog-ng[4401]: Changing permissions on special file /dev/tty10
Oct 16 23:48:59 r098088 kdm[5399]: X server for display :0 terminated unexpectedly

So the X server crashed the very moment, syslog-ng restarted (and set some permissions). Did you do that syslog-ng restart on purpose? Can you trigger something using that method?

P.S. bugzilla is dumb, please help it in selecting the "this is a text file" option when creating attachments.

First of all uninstall the nvidia driver when you want to use the nv driver.

-->   nvidia-installer --uninstall

If the problem still occurs attach the new Xorg.0.log and .xsession-errors.

I don´t have a nvidia driver any more on my system, I uninstalled it before I copied the logs.
The X server doesn´t crash, it lock up (I see only the cursor) and when I press CTRL+ALT+BACK KDM doesn´t respawn, I get the console. This is when I copied the logfiles.

Of course you have it still installed

[...]
(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
	compiled for 4.0.2, module version = 1.0.7174
	Module class: XFree86 Server Extension
	ABI class: XFree86 Server Extension, version 0.1
(II) Loading extension GLX
[...]
(EE) Failed to initialize GLX extension (NVIDIA X driver not found)

I uninstalled it using the installer and when I run it it says that no driver was installed.
I´ll remove the "glx" module from startup and see if the bug reappears.

I reinstalled the ATI driver and the warning is gone

ATI driver? You use a nvidia board! Attach the new logfile, please.

I switched from a nVidia card to an ATI card!
The bug happened again and so I attach the new logs.

Created attachment 54462 [details]
xorg.0.log

Created attachment 54463 [details]
xorg.1.log

Created attachment 54464 [details]
xsession-errors

Created attachment 54465 [details]
xorg.99.log

Would you please try the radeon driver first? I probably will fail in trying to fix ATI "fglrx" driver bugs ...

There is no indication of any crash in the log file robably because the server got restarted again.
Please attach Xorg.0.log.old.

Created attachment 54610 [details]
xorg.0.log.old

This occurs with both nvidia drivers, ATI proprietary and open-source drivers.

According to this logfile the Xserver did not crash ...

The X server doesn´t crash, it locks up (I see only the cursor) and when I
press CTRL+ALT+BACK KDM doesn´t respawn, I get the console. This is when I
copied the logfiles.

I already posted this above, if I stated somewhere before thet the server crashed then sorry for that.

Please try again with Alpha2. We switched to X.Org CVS for Alpha2. It doesn't make much sense to investigate X.Org 6.8.2 issues, when these might already fixed with X.Org CVS.

No feedback. Please reopen if the problem persists. Thanks.

I can´t install Alpha2 on any of my systems, the installed system isn´t bootable so I can´t test this further.

Michael:
> The X server doesn´t crash, it locks up (I see only the cursor) and when I
> press CTRL+ALT+BACK KDM doesn´t respawn, I get the console. This is when I
> copied the logfiles.

Does 'lock up' mean, that the mouse cursor doesn't move when you move the mouse? Generally when kdm tells the xserver to shut down it is conceivable that the server hangs someplace. But since you can 'zap' it it means that the server is still servicing the main loop so that's not really conceivable.
It's strange however that kdm doesn't attempt to start another Xserver. It should try 3 times before it decides to give up.

Beta2 didn´t work for me at all, so I´ve to test beta3 in the next days. Then I´ll see if the bug is fixed in Xorg CVS

Any news on this one? 10.1 Alpha4 is available since Dec 15 2005.

I don´t have luck with your alphas *g
Alpha4 is unusable as Alpha3 was, at least on my system. I already filed a bug report for this.

That's unfortunate. Anyway, as long as I can't get the appropriate feedback I can't work on this bugreport. I assume this one now as FIXED. Feel free to reopen if you ever manage to install a 10.1 (Alpha/Beta/final) and the problem persists.