Computer hangs after switch user or lock screen

[oldei]

Ubuntu 8.04

I locked my screen for 5 minutes. When I decide to log back in, it hangs. It's just a blank screen. It can't even open the Log-in window. This also happens if I decide to switch to another user instead of locking the screen.

> Effects disabled
> Screensaver is just the black screen
> Power management options: all Never

Thank you.

--------------------------------------------
AMD Athlon 64X2 Dual Core 5000; MSI K9VGM-V
 Radeon 1550 video card; 2GB memory; 320 GB Hard disK

[Mathias (mathias-anlander)]

Im having the same problem after reistalling with 8.04, worked flawlessy in 7.10.

The funny thing is that when the computer "locks" after trying to return from screen saver, is that if I press the stand button (I have a laptop) the computer goes to stand by - then when pressng any key to wake it up, I get the usual dialog where I need to enter my password to get into the desktop again!

_____________________
Compaq Presario, AMD Turion 64, 2 gig RAM

[Chris Gardner (chris-gardner76)]

I'm having the same problem on an IBM/Lenovo ThinkCentre desktop. I didn't measure the length of time the screen must be locked before a login attempt hangs, though.

[[e-mail] (sbuttgereit)]

Same problem here. Lenovo Thinkpad, T60p with ATI video. I do have desktop effects enabled.

I usually don't notice it until I come back to work the next day (hours long wait, happens every day since 8.04 upgrade from 7.10), but today I experienced it in what must have been a few minutes of going into a black screen. Similar to other reports, there are other signs of life, when I press the power button I see disk activity as though something is responding to the button push. otherwise, no dice. just a black screen. There are other similar issues happing with the install, such as gnome-panel becoming unresponsive when I left click the clock applet; I'm presuming these are different & unrelated, but thought I'd mention just in case there's meaningful correlation. Also, virtualbox with windows xp guest is almost also running and is often times the last application I've used (keyboard capture?); again can't prove a correlation, but can't dismiss the possibility.

Don't know what other data I could provide that could be helpful. Would be happy to do so if feasible/guided.

[[e-mail] (sbuttgereit)]

One other observation... it doesn't happen all the time. I just left for about 10 minutes; on return screen was blanked and the system resumed normally.

[Boris Burtin (boris-burtin)]

I've also seen this. Happens once every week or two. After locking the screen, I type my password and never get my desktop back. I think it's just the login process, because I'm able to ssh in to shutdown or reboot.

[Sergio Barjola (sbarjola)]

associated to gnome-screensaver package.

[Shervin Asgari (shervin)]

I have the same problem. But this happens ONLY when I am in dual screen mode. When using single screen this problem does NOT happen.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you with Intrepid? Thanks in advance.

[Pedro Villavicencio (pedro)]

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!.

[Mathias (mathias-anlander)]

I did a "release" but Im unsure I did the right thing by doing that... anyway... this bug is fixed in Intrepid, at least it works perfectly on my Compac Presario with a nvidia board now! Thanks!

[Ram Gole (ram-gole-gmail)]

This happens extremely frequently. The screensaver is set to "Skyrocket" but I don't think that is the reason. Atleast once a day when I try to unlock the screen the machine hangs. The mouse I guess works because sometimes I have seen the cursor and it moves with the mouse. But nothing on the keyboard works. Only a hard reboot brings things back to normal.

Please help. Let me know of any additional test I should do etc. This has to be fixed at all costs.

[Ram Gole (ram-gole-gmail)]

The problem doesn't manifest since I changed the screensaver to blank. I think we should remove buggy screensavers like skyrocket.

[Shervin Asgari (shervin)]

When in dual screen I cannot go to the screensaver to change anything.
Hence I cannot put the screensaver to blank there.
What I need to do is kill the gnome-screensaver-helper two times, and then the log in appears.

At least its a workaround for me

[Célio Cidral Junior (ccidral-dev)]

The problem still happens to me. The steps:

1. Log in with user "john"
2. Fast switch to user "mary"
3. Fast switch to user "john"

The screen goes black. Can't restart gnome with CTRL-BACKSPACE. Can't open text terminal with CTRL+ALT+F[1-6].

Some info for now (I will provide detailed info soon):

- Ubuntu 8.10 (all updates applied until now).
- Integrated Intel video card.
- No 3D driver installed.
- Screensaver is completely disabled (the package is installed however).

[Sebastien Bacher (seb128)]

could you try on jaunty?

[Shervin Asgari (shervin)]

Sebastien Bacher wrote:
> could you try on jaunty?
>
>
I dont have this problem anymore.

Shervin

[Célio Cidral Junior (ccidral-dev)]

Sebastien Bacher wrote:
> could you try on jaunty?
>
>

Me neither.

[Pedro Villavicencio (pedro)]

awesome news, marking this as fixed then, please open a new report if you are still facing this issue with Jaunty, thanks all.

[JayeshBadwaik (jayeshb-work)]

Well, I'm sorry...
but i think it needs to be opened again....

I am facing the same problem again.....
though it occurs only when i give a keyboard input to get back to desktop
moving the mouse to get back to desktop works well
and when the keyboard works it takes a little longer (may be not really due to the same thing)

blank screensaver doesn't cause any problem
and the problem is there only when i activate "lock screen when screensaver is active" option in
System->Preference->Screensaver
and when i lock screen manually

[JayeshBadwaik (jayeshb-work)]

an update:
blank screensaver also causes problem
i am locking the screen manually.................
and i can confirm with 50/60 times that i've experienced the problem while using keyboard input
no problem while using mouse input to get back to normal screen

[hardke01 (hardke01)]

I can also confirm this problem Ubuntu 9.04 Jaunty
2.6.29-02062903-generic #02062903

Happens on average 2 - 3 times a week. only way to recover is a power off via button.
Thinkpad R60 with i945GM Intel graphics with compiz effects turned on and default black screensaver.

After locking the laptop the screen goes black and no amount of mouse or keyboard activity will enable the unlock login box to appear. Hard disk appears to have light activity when buttons are pressed but nothing displays.

Are there any logs i need to be looking for or enabling to debug this issue?

Thanks

[hardke01 (hardke01)]

Ok, i have had a look in the /var/log/messages log and received a load of these messages about the time that the crash/hung state occurred.

Jul 17 12:11:20 sy001428 kernel: [15502.322506] SysRq : HELP : loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W) dumpZ-ftrace-buffer

I have no idea what this means, however i'm sure its not good.

After these messages i removed then reinserted my USB mouse receiver which was correctly picked up in the log and identified properly, so it proves that the machine is still active in the background. It has also picked up a load of btnx commands sent from the mouse. I assume the restart at the end is the result of holding the power button down.

Jul 17 12:11:36 sy001428 kernel: [15518.272068] usb 2-1: USB disconnect, address 2
Jul 17 12:11:37 sy001428 kernel: [15520.000024] usb 2-1: new full speed USB device using uhci_hcd and address 3
Jul 17 12:11:37 sy001428 kernel: [15520.184762] usb 2-1: configuration #1 chosen from 1 choice
Jul 17 12:11:37 sy001428 kernel: [15520.192797] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0/input/input43
Jul 17 12:11:38 sy001428 kernel: [15520.244115] generic-usb 0003:046D:C51A.0003: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1/input0
Jul 17 12:11:38 sy001428 kernel: [15520.251387] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.1/input/input44
Jul 17 12:11:38 sy001428 kernel: [15520.292170] generic-usb 0003:046D:C51A.0004: input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1/input1
Jul 17 12:11:40 sy001428 kernel: [15523.169490] input: btnx keyboard as /devices/virtual/input/input45
Jul 17 12:11:41 sy001428 kernel: [15523.269132] input: btnx mouse as /devices/virtual/input/input46
Jul 17 12:11:41 sy001428 kernel: [15523.368534] input: btnx keyboard as /devices/virtual/input/input47
Jul 17 12:11:41 sy001428 kernel: [15523.368971] input: btnx keyboard as /devices/virtual/input/input48
Jul 17 12:11:41 sy001428 kernel: [15523.377477] input: btnx keyboard as /devices/virtual/input/input49
Jul 17 12:11:41 sy001428 kernel: [15523.416136] input: btnx mouse as /devices/virtual/input/input50
Jul 17 12:11:41 sy001428 kernel: [15523.421470] input: btnx keyboard as /devices/virtual/input/input51
Jul 17 12:11:41 sy001428 kernel: [15523.483108] input: btnx mouse as /devices/virtual/input/input52
Jul 17 12:11:41 sy001428 kernel: [15523.547808] input: btnx mouse as /devices/virtual/input/input53
Jul 17 12:11:41 sy001428 kernel: [15523.613848] input: btnx mouse as /devices/virtual/input/input54
Jul 17 12:13:23 sy001428 syslogd 1.5.0#5ubuntu3: restart.

Any insight into the Sysreq messages would be great.
Thanks