GNOME Bugzilla – Bug 359605
Password rejected due to timeout after resume
Last modified: 2006-11-25 22:48:48 UTC
Forwarded from: https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/40022 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?
Richard, is gpm_hal_suspend or the HAL .Suspend() async? In other words is there any chance that the function returns before the execution is stopped? I'm wondering if the reporter is getting to the .poke() part before the system is down. This may or may not help... 2006-10-12 William Jon McCann <mccann@jhu.edu> * src/gs-lock-plug.c: (remove_cancel_timeout), (gs_lock_plug_response), (dialog_timed_out), (restart_cancel_timeout), (gs_lock_plug_show), (switch_page), (gs_lock_plug_show_prompt), (entry_key_press), (gs_lock_plug_finalize): Don't poll timers to determine when the dialog has timed out. Just rely on when a timeout source gets triggered. The polling was a remnant of when we used to have a progress bar in the dialog. May fix #359605
It's syncronous, i.e. the method returns when we resume. That's why we have to filter the error message incase dbus timed out in that period.
From https://launchpad.net/distros/ubuntu/+source/gnome-screensaver/+bug/40022/comments/6 "Seems like this issue has been disappeared with Edgy. At least I do not remember bumping into this any more =)" Closing the bug.