[armel] screensaver hangs on unlock, eats cpu
Bug #458501 reported by
Paul Larson
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".
Changed in gnome-screensaver (Ubuntu): | |
status: | New → Confirmed |
Changed in gnome-screensaver (Ubuntu): | |
importance: | Undecided → High |
Changed in gnome-screensaver (Ubuntu Karmic): | |
assignee: | nobody → David Sugar (dyfet) |
description: | updated |
Changed in gnome-screensaver (Ubuntu Karmic): | |
milestone: | none → karmic-updates |
Changed in gnome-screensaver (Ubuntu Lucid): | |
milestone: | none → lucid-alpha-2 |
summary: |
- screensaver hangs on unlock, eats cpu + [armel] screensaver hangs on unlock, eats cpu |
Changed in gnome-screensaver (Ubuntu Karmic): | |
status: | Confirmed → Won't Fix |
To post a comment you must log in.
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 :).