feisty logout crash

I can confirm this problem. I'm running a new installed system (kubuntu feisty beta + latest updates). When I want to log off, all I get is a black screen. Switching to a terminal is impossible.
I have a nvidia geforce fx 5200 go card with "nv" driver.

After the latest upgrade I've done everything is ok again. I can log out properly.
There were a couple of kde packages to upgrade. I don't know which one has resolved my problem.

This problem still exists for me with Kubuntu 7.04 beta: the X server crashes when logging out of KDE. There are two workarounds I know of:

1. Log out by doing Ctrl-Alt-Backspace - not very elegant!
or
2. Add the following line to the [X-*-Core] section in /etc/kde3/kdm/kdmrc:

TerminateServer=true

I got the same problem. I can't logout properly from my kde sessions.

Also using an nvidia card if that has anything to do with it.

Does this bug still occur in feisty final?

No, I could fix it very soon after this post with a trick I found in another post. Something about restarting the xserver more often than necessary.

Do you think I could remove this additional starts now in feisty final?

I'm not sure. I would if the problem was caused by a mistake of mine. If it didn't happen that way, you should associate this bug with the xserver package and update the description to state its feisty final (the date at the bottom gives the beta away).

Hmmm, I am not not sure that I understand this.
I would like to help you with this bug if possible, giving back to the community and all that.
Is there anything I can do for you about this?
Should I retry anything now and let you know the result?

Thanks for wanting to help; here's what you can do: Because the final version of Feisty was released (and this bug is still about 7.04 beta), you should repeat the steps you took to make 7.04 beta crash on 7.04 Final. This will let us know if this problem has been fixed or not. If you can make the error happen again, then we'll know that this is still a problem and in this case, you should close this bug and file a new one about Feisty final. If you can't make it happen then you can mark this bug as "Fix Released" or ask someone else to do so. Thanks again!

I can confirm this still happens in Kubuntu 7.04 Final, I've been using the TerminateServer workaround mentioned above.

I'm having this problem in the most up-to-date version of Hardy.

I just installed Ubuntu on a friend's Dell machine (pretty new Intel Core Duo, Intel graphics chipset I believe), and every time I logout, everything freezes. I get a black screen and the computer keeps running, but nothing works--no CTRL-ALT-BKSPC, CTRL-ALT-F1, ssh, anything. Can't access the server remotely. The only way to get it started again is to force power down and restart. I've disabled compiz and don't know what else to do.

Update: after freezing and restarting several times, the machine no longer starts at all. Ubuntu starts to load, then I hear a beep and I get nothing but a black screen. I would think it was a hardware issue but they tell me the computer was working fine with Windows.

I don't think this is a gdm bug. It happens even if I Ctrl-Alt-Bckspc (most of the time).

Please attach a full backtrace of the crash (see http://wiki.ubuntu.com/X/Backtracing for directions).

Another thing to try with these sorts of "blank screen on mode change" is to set the following in your xorg.conf and see if it makes the issue go away:

Section "Device"
   ...
   Option "ForceEnablePipeA" "true"
EndSection

If adding ForceEnablePipeA in xorg.conf does make the issue go away, then refer to bug #138256, and report a new bug following the directions there.

I'm having this problem also. It happens to me only when I am using the "switch users" functionality; it never seems to happen with just one user logging in and out. Ubuntu Hardy, Core2 Quad, Intel DP35DPM mainboard, no Compiz. I've tried with both the open source and restricted ATI driver for my Radeon card; same results. The system becomes completely unresponsive, even refusing to shut down when the button is pressed and failing to accept ssh connections.

Since the system is completely unresponsive, I've no idea how I would backtrace it.

I've just tried the "ForceEnablePipeA" fix, and got no relief there also. I've also tried the "hardy-proposed" fglrx X server; no help there either.

See http://wiki.ubuntu.com/X/Backtracing for directions on obtaining backtraces.

If you cannot ssh into the box, then that indicates it might be a kernel issue - check for kernel Oopses and so on (see debugging instructions for the kernel if this is the case.)

that's not a gdm issue

Seems like a kernel issue. Feel free to reopen against xorg if there's proof it's X and not the kernel at fault.

Hi Guys,

Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It might also be useful to attach your /var/log/kern.log.0 file after you experience this bug and have to reboot.

Additionally, if you could also confirm if this is still an issue with the latest Alpha for the upcoming Intrepid Ibex 8.10 that would be useful to know as well. You should be able to test via a LiveCD - http://www.ubuntu.com/testing. Please let us know your results.

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!