Lock screen dialogue freezes on correct password

Bug #363361 reported by SteveH
60
This bug affects 13 people
Affects Status Importance Assigned to Milestone
GNOME Screensaver
Expired
High
gnome-screensaver (Ubuntu)
Triaged
Medium
Tejal

Bug Description

Binary package hint: gnome-screensaver

Running 9.04 release candidate (upgraded from 8.10)
gnome-screensaver version 2.24.0-0ubuntu6 (I think this is the package that handles the lock screen dialogue?)

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.

Perhaps related to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/285763 ?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, May you please get us a screensaver debug log? please do the following:

killall -9 gnome-screensaver
gnome-screensaver --no-daemon --debug > /tmp/gs.log 2>&1

Reproduce the issue and attach that resulting file to the report, thanks in advance.

Changed in gnome-screensaver (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
SteveH (steve-fullvolume) wrote :

Hi, thanks for the response. Attached it the debug log you asked for.

It is also worth noting that, whilst creating this log, I noticed that the bug only occurs once per boot:
The first time I kill gnome-screensaver, start it in debug mode and lock screen the bug occurs.
Any further time I kill gnome-screensaver, start it in debug mode and lock screen the unlocking works flawlessly.

I will attach the same form of debug log for when the unlocking succeeds in my next comment.

Revision history for this message
SteveH (steve-fullvolume) wrote :

As stated in my last comment this bug only occurs once per boot.

Attached is the debug log of the second attempt to lock/unlock which works properly.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the logs you provided, changing this to confirmed to be looked by a developer.

Changed in gnome-screensaver (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug should be sent to software writters on bugzilla.gnome.org by somebody having the issue

Revision history for this message
SteveH (steve-fullvolume) wrote :
Revision history for this message
bj mccormick (bjmccormick) wrote :

Would like to add that this happens to me as well. I found that sticking a usb HD into a slot will get it going again. The only thing in the logs that was odd was some EXT4 stuff
Jun 5 09:22:28 bj-desktop kernel: [112677.880983] ext4: find_group_flex failed, fallback succeeded dir 130977
Jun 5 09:22:44 bj-desktop kernel: [112693.979505] ext4: find_group_flex failed, fallback succeeded dir 5591
Jun 5 09:25:46 bj-desktop kernel: [112876.171814] ext4: find_group_flex failed, fallback succeeded dir 130977
Jun 5 09:29:51 bj-desktop kernel: [113121.428864] ext4: find_group_flex failed, fallback succeeded dir 4438
Jun 5 09:29:51 bj-desktop kernel: [113121.435315] ext4: find_group_flex failed, fallback succeeded dir 4438
Jun 5 09:29:51 bj-desktop kernel: [113121.437846] ext4: find_group_flex failed, fallback succeeded dir 4438
Jun 5 09:29:52 bj-desktop kernel: [113122.125480] ext4: find_group_flex failed, fallback succeeded dir 4438
Jun 5 09:30:51 bj-desktop kernel: [113180.797784] usb 1-3.2.4: reset full speed USB device using ehci_hcd and address 8

Changed in gnome-screensaver (Ubuntu):
status: Confirmed → Triaged
importance: Low → Medium
Changed in gnome-screensaver:
status: Unknown → New
Revision history for this message
Mark Nevill (nevillm) wrote :

I had this issue but it seems to be working now. Current version of gnome-screensaver: 2.27.0-0ubuntu3. I do not know which version fixed the issue, as I disabled automatic screen locking as a temporary workaround.

Revision history for this message
Christian Funder Sommerlund (zero3) wrote :

I can confirm that it still exists in 9.04 (gnome-screensaver 2.24.0-0ubuntu6). I have the the "black screen" screensaver enabled, but not "lock desktop while screensaver is active".

Are you running 9.10 alpha?

Revision history for this message
Mark Nevill (nevillm) wrote :

Yes, hence the newer gnome-screensaver version.

Revision history for this message
Martin U. (martin-werbewahn) wrote :

I still have the same issue running 9.10 and gnome-screensaver 2.28.0. Killing the gnome-screensaver-dialog enables unlocking after it freezes, but it's pretty annoying. :/

Revision history for this message
Jason (beatme101) wrote :

I just had the issue on 9.10 as well.

Revision history for this message
EJD (emlynjdavies) wrote :

I have this problem on my home machine (Ubuntu 9.10).

I have a slightly different problem at work (just upgraded from Ubuntu 9.04 > 9.10) in that when I click "Lock Screen" nothing happens at all.

Revision history for this message
narnie (signupnarnie) wrote :

I am still having this problem.

From syslog, it shows

Apr 1 17:53:57 localhost gnome-screensaver-dialog: pam_sm_authenticate: Called
Apr 1 17:53:57 localhost gnome-screensaver-dialog: pam_sm_authenticate: username = [woodnt]

which as I suspected in the first place makes it seem that it is a problem with the calling of the password authentication module.

I confirm this on 9.10 as well with an updated system on a Toshiba laptop 64 bit install.

With thanks,
Narnie

Changed in gnome-screensaver:
status: New → Incomplete
Changed in gnome-screensaver:
importance: Unknown → High
Revision history for this message
narnie (signupnarnie) wrote :

I can also confirm this bug on a fresh install of 10.04. Sorry it took me so long to report it.

Changed in gnome-screensaver:
status: Incomplete → Expired
Revision history for this message
narnie (signupnarnie) wrote :

Why was this changed from Incomplete to Expired? It looks like everything that was asked for has been given.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

narnie, someone needs to answer the question upstream asked a few weeks ago:

"What process is using 100% cpu? Can you try to attach gdb to it and get a
backtrace while that is occuring? Thanks."

and reply in the upstream report. thanks.

Revision history for this message
Tomas Vigouroux (tvigouroux) wrote :

I everybody, Yesterday I installed 10.10 RC and I having the same problem: When I enter the correct password at lock screen, the window freezes at "checking". The only way to take control is killing the process.

Can somebody review the following debug log?

Revision history for this message
Cyril Jaquier (cyril-jaquier) wrote :

I have this bug on only laptop since several Ubuntu release (maybe since 9.10!?). The unlock screen will stay in the "checking..." state until I "killall gnome-screensaver" from another virtual terminal. After that, gnome-screensaver will work perfectly (even after suspend/resume). So this still happens with 10.10.

Tejal (tejalravih)
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Tejal (tejalravih)
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.