screen fails to lock on waking from sleep

[Robert Persson]

When I woke my laptop (Thinkpad R61i running Intrepid) this evening the desktop appeared unlocked. This is the first time that this has happened in the 10 or 20 times I have woken the machine since upgrading to Intrepid. I do not yet know if this will happen again; I shall be able to report on that in the future when I have a little time. I am reporting this now rather than later because it is a security issue.

[somekool (somekool)]

I was about to fill a similar Bug.

running 8.10 on a Dell D820.

Kubuntu always wake up from sleep unlocked.

[somekool (somekool)]

what if we do not use gnome?

[Tormod Volden (tormodvolden)]

Is this still a problem in Ubuntu 9.04 or Ubuntu 9.10 Beta?

[Daniel (daniel-jacobs)]

In Ubuntu 9.04 the screen was always locked after suspend for me, but in Ubuntu 9.10 the screen is unlocked after waking up.

This is a real security issue! Why is the importance set to low?

[Tormod Volden (tormodvolden)]

Importance is low because it has not been confirmed that it is a widespread or valid issue. Works fine here. How do you enter suspend? Indicator-applet or some special keyboard/hardware button?

[Tormod Volden (tormodvolden)]

I'll be d*mned, this _worked_ fine in Ubuntu 9.10 but not any longer. I can confirm it, using my "sleep" keyboard button.

[Tormod Volden (tormodvolden)]

Oh I am such an i*. I had disabled gnome-screensaver while debugging some xscreensaver stuff. It does work fine. Please check whether gnome-screensaver is running before and after the resume cycle.

[Tormod Volden (tormodvolden)]

This was originally reported in gnome-power-manager, but I am sure that bug got fixed. The later comments are due to indicator-session. If you suspend via the indicator applet menu, gnome-power-manager is not being used, since indicator-session calls devicekit to do the suspend.

If you use a hardware button, gnome-power-manager will take care of suspending, and also locks the screen.

[Daniel (daniel-jacobs)]

For me gnome-screensaver was disabled, too! I can't remember that I did it. Seems that in my case the error was produced 20cm before the screen.

Now everything is working pretty perfect for me!

Sorry for that noise!

If this bug does not appear for somekool anylonger the bug should be closed.

[Tormod Volden (tormodvolden)]

I'll close this bug now. I can not reproduce it, and if it reappears, it is mostly due to other reasons than what was originally reported here, so a new bug should be filed.