After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582952 - Lock screen dialogue freezes on correct password
Lock screen dialogue freezes on correct password
Status: RESOLVED INCOMPLETE
Product: gnome-screensaver
Classification: Deprecated
Component: dialog
2.24.x
Other All
: Normal major
: ---
Assigned To: gnome-screensaver maintainers
gnome-screensaver maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-17 15:50 UTC by steve
Modified: 2011-09-23 13:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
Log of test-passwd (1.74 KB, text/plain)
2009-10-04 10:54 UTC, David Kohen 		Details
backtrace of the process using 100% cpu when this happens (17.59 KB, text/plain)
2011-09-23 13:16 UTC, Andy Poling 		Details

Description steve 2009-05-17 15:50:20 UTC 
Please describe the problem:
When confronted with the lock screen dialogue (whether produced from Lock Screen, switching back from guest session, or restoring from suspend mode) it is impossible to unlock. If the correct password is given the dialogue freezes at the status message "Checking..." and fails to respond. The fan then starts up so I suspect the CPU is being used at 100%

This bug occurs with and without desktop effects. I'm running a laptop with an integrated intel graphics driver.

Steps to reproduce:
1. Lock Screen
2. Enter correct password
3. Click Unlock


Actual results:
Screen stops at the status message "Checking..."

Expected results:
Screen to unlock

Does this happen every time?
Once per boot, every boot. The second time this is attempted (after a killall gnome screensaver) it works flawlessly.

Other information:
Original bug report and debug logs at https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/363361
Comment 1 William Jon McCann 2009-08-21 03:16:51 UTC 
Please try the test-passwd program as described here:
http://live.gnome.org/GnomeScreensaver/FrequentlyAskedQuestions#head-d50bc17e7d6f3a51c4715f02c657195e80e26c2c

Most likely this is a PAM configuration problem on your distro.
Comment 2 David Kohen 2009-10-04 10:54:41 UTC 
Created attachment 144703 [details]
Log of test-passwd

I have this bug as well, and test-passwd doesn't seem to complain.
In addition, killing the gnome-screensaver-dialog enables an unlock after a bad password.
Comment 3 Tobias Mueller 2010-04-04 16:38:52 UTC 
Hm. Reopening as the test-passwd program apparently has been used.
Comment 4 William Jon McCann 2010-06-21 19:02:32 UTC 
What process is using 100% cpu?  Can you try to attach gdb to it and get a backtrace while that is occuring?  Thanks.
Comment 5 Felipe Besoaín Pino 2010-09-28 15:34:28 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 6 Andy Poling 2011-09-23 13:16:49 UTC 
Created attachment 197352 [details]
backtrace of the process using 100% cpu when this happens

I'm attaching the output of a gdb session with a backtrace of the process in question.

I'm running gnome-screensaver 2.30.0-0ubuntu2.1 in case it matters.
Comment 7 André Klapper 2011-09-23 13:40:33 UTC 
Andy Poling: Please file a new bug report if this still happens in a recent version (2.32/3.0). 2.30 is too old and not maintained anymore.