[armel] screensaver hangs on unlock, eats cpu

Bug #458501 reported by Paul Larson
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Fix Released
High
Unassigned
Karmic
Won't Fix
High
Unassigned
Lucid
Fix Released
High
Unassigned

Bug Description

On a dove board with rc candidate image I was able to reproduce this reliably. I try to lock the screen, then unlock it and it just hangs there. I can go to a tty and login, and I see that gnome-screensaver is consuming 95%+ cpu, but strace on the pid does not show me any output.

Workaround:
Press Ctrl-Alt-F2 and login on the console, then run "killall gnome-screensaver".

Revision history for this message
Paul Larson (pwlars) wrote :
Tobin Davis (gruemaster)
Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed
Paul Larson (pwlars)
Changed in gnome-screensaver (Ubuntu):
importance: Undecided → High
Loïc Minier (lool)
Changed in gnome-screensaver (Ubuntu Karmic):
assignee: nobody → David Sugar (dyfet)
Revision history for this message
David Sugar (dyfet-deactivatedaccount) wrote :

This is my experience also with the rc candidate on my Dove Y0 board. The gnome-screensaver process goes to full cpu and (probably) never unlocks. It does not seem to matter which screensaver is selected, and it is my impression the forked instance of gnome-screensaver that unlocks the screen dies in some loop trying to authenticate the user. If you kill it and the base instance of gnome-screensaver, you can get back your screen, but that is not a user valid work-around :).

Loïc Minier (lool)
description: updated
Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

I have a similar problem too. When screensaver is running, sometime the machine seems locked. Switching to a virtual console and back normally show the unlock dialog. Even without switching console, typing the password blindly does the trick.

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Ah, not a dove board. Just a normal PC with AI graphics (flxgr driver)

Revision history for this message
Carey (carey) wrote :

I have observed both of these problems with gnome-screensaver on two different machines. Both are running freshly-installed final releases of Karmic with latest updates as of the past week. One machine is x64 with fglrx, the other is x32 eeePC (Intel Atom + Intel graphics).

The first problem is where gnome-screensaver crashes on unlock (my desktop will not function until I switch to a tty and kill gnome-screensaver).

The second problem, as another user has reported above, is sometimes when I go to unlock my screensaver: the screensaver will stop on key/mouse input as expected but no prompt is displayed. At first I thought this was a display freeze however I discovered I could type my password blindly and my desktop would unlock.

Major issue for average users who do not know how to switch to tty, check running processes and find by logic the culprit.

Paul Larson (pwlars)
Changed in gnome-screensaver (Ubuntu Karmic):
milestone: none → karmic-updates
Changed in gnome-screensaver (Ubuntu Lucid):
milestone: none → lucid-alpha-2
Martin Pitt (pitti)
summary: - screensaver hangs on unlock, eats cpu
+ [armel] screensaver hangs on unlock, eats cpu
Revision history for this message
Paul Larson (pwlars) wrote :

With today's image (20091218), I can no longer reproduce this bug. Seems to have been fixed in one of the recent updates

Changed in gnome-screensaver (Ubuntu Lucid):
status: Confirmed → Fix Released
Revision history for this message
Tom Vaughan (tvaughan) wrote :

This is back as of the latest Lucid release. I have a Dell Studio 15, and am running the 64-bit kernel.

Revision history for this message
David Sauvage (pariakanet) wrote :

This critical bug is still present on Ubuntu 10.04 i386 (Dell Inspiron 510m)
After entering the password to unlock the session, the gnome-screensaver application use about 80% to 90% CPU is hang on the "verifying" state.

The only way to proceed is to log in through a virtual console and kill -9 gnome-screensaver.

gnome-screensaver 2.30.0-0ubuntu2
linux-image-2.6.32-22-generic 2.6.32-22.36

855GM glasen ppa kernel fixed applied to be able to load ubuntu on this dell
https://launchpad.net/~glasen/+archive/855gm-fix

Revision history for this message
Loïc Minier (lool) wrote :

Folks, this bug is specific to ARM hardware; please open a new bug if you see similar issues on x86 (Intel or AMD) hardware running lucid or maverick.

Thanks,

Rolf Leggewie (r0lf)
Changed in gnome-screensaver (Ubuntu Karmic):
status: Confirmed → Won't Fix
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.