Black screen and keyboard unresponsive after logging out

[Bjorn Tipling]

On Ubuntu 8.04, Hardy after I log out of Gnome or Xmonad I end up with a black screen and the keyboard becomes unresponsive. My monitor does not go into hybernation, it is just black. Key commands like cntrl+alt+backspace, or attempts to open a virtual terminal fail. The only thing I have been able to do when this happens is restart the machine. This happens 100% of the time I try to log out. I am logging out via the 'log out' button on the Gnome pop up and Alt+shift+Q in xmonad.

What I expected to happen was to be given a login screen just as I see it when I first start up the machine.

[Robert Moerland (veel-mail)]

I have upgraded Xubuntu from 7.10 to 8.04, and I occasionally have the same problem. I need to killall gdm to shut down the X server from a normal terminal (CTRL+ALT 1), or simply do a sudo reboot. As it doesn't happen 100% of the time, I suspect that the suspend mode has something to do with it. The last time this phenomenon occured, my laptop had resumed operation from stand-by mode. I will report back with better statistics when I have them.

[Robert Moerland (veel-mail)]

I can consistently reproduce a black screen after putting my laptop in suspend mode. After resuming from suspend mode, log out closes all applications, I briefly see the terminal screen showing some stuff from booting, and then the screen goes black, presumably when the graphical login screen should be displayed.

I've attached the output of pstree, to show the processes running while the login screen is black.

[Sydney Early (sydneyearly)]

Linux 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux
Ubuntu 8.04.1

Steps to reproduce:
1. Log in as a User.
2. Wait for the screen to lock via screen saver.
3. Click Switch User.
4. Log in as a second user.
5. Click System -> Quit -> Log out.
6. The screen will go Black.

The only way I have found to recover is a hard reset.

I would be happy to provide any details about my system to help developers close this bug.

Thank you

[xteejx (xteejx)]

Can you confirm that this is still the case with all latest updates including backports?

Thanks

[Marlon Cisternas Milla (mcisternas-deactivatedaccount)]

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!

[Mark Asbury (mark-asbury)]

I have applied all the latest updates and I see the same problem using the steps reported by Sydney Early above. However, step 2 noted above about the screen saver does not have to occur.