Password rejected due to timeout after resume

Bug #40022 reported by Mikko Saarinen
16
Affects Status Importance Assigned to Milestone
GNOME Screensaver
Fix Released
Medium
gnome-screensaver (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

I have set the password protection on from the screensaver options. This causes the screen to lock when suspending or hibernating the machine.

When the machine is powered on again, I am greeted with the lock screen which asks for my password. If I start to type my password I get the time out -message and the password is rejected.

Seems like the timing starts from the moment the machine starts entering power-saving mode. Could it be changed so it starts when it has resumed?

Revision history for this message
Mikko Saarinen (mikk0) wrote :

Related to this, sometimes after the authentication is done and I should get my desktop back I am instead greeted with the window that pops up when you press the power button.

If I press the Cancel button, it gives me my session back. That is just another step I wouldn't bother taking.

Revision history for this message
Hezekiah Carty (hez) wrote :

I can confirm this. It seems to happen if there was some input after the screensaver was activated, but before the system suspended.

Changed in gnome-screensaver:
status: Unconfirmed → Confirmed
Revision history for this message
Ante Karamatić (ivoks) wrote :

I can confirm this. I noticed that if I enter my password before network-manager renews wifi connection, everything is fine. But, if I don't enter my password that fast, in the same time when network-manager renews wifi connection (can be seen by a flash of a notification in upper right corner, even if screen is locked), I get time out.

This was the case in Dapper and is also in Edgy.

Do you guys also run network-manager?

Revision history for this message
Mikko Saarinen (mikk0) wrote :

I'm not running network-manager, since it doesn't work with ra2500 using wpa...
But that's another issue ;-)

So for me this is not the cause.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :
Changed in gnome-screensaver:
status: Unknown → Unconfirmed
Changed in gnome-screensaver:
status: Unconfirmed → Needs Info
Revision history for this message
Mikko Saarinen (mikk0) wrote :

Seems like this issue has been disappeared with Edgy. At least I do not remember bumping into this any more =)

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for following up. Closing the bug.

Changed in gnome-screensaver:
status: Confirmed → Fix Released
Changed in gnome-screensaver:
status: Needs Info → Fix Released
Changed in gnome-screensaver:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.