gnome-screensaver segfaults at login screen instead of giving back login screen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Screensaver |
Fix Released
|
Unknown
|
|||
gnome-screensaver (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-screensaver
Hello,
This bug may be the parent of #99647, #58963, #185554. All these reports (closed because of missing info) mention a failure when resuming.
I face the same issue, but I think it's not at all suspend/resume related: I noticed the bug happens also when I simply check the "lock screen when screensaver is active".
_What should happen_: in cases where the screensaver "end" returns to the login screen (i.e. after resuming or if the user configured it this way in the screensaver conf panel), moving the mouse / hitting a key should return the login screen.
_What happens_: the screensaver runs, and as soon as I move the mouse or hit a key, the screen flickers a bit, and the screensaver continues to run (instead of returning to the login screen).
See the attached file with the segfaults (from /var/log/syslog) and feel free to ask more info, I'll be tracking this bug closely.
Intrepid uptodate as of october 19th.
Video : Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
gnome-screensaver:
Installed: 2.24.0-0ubuntu2
Candidate: 2.24.0-0ubuntu2
Version table:
*** 2.24.0-0ubuntu2 0
500 http://
100 /var/lib/
Changed in gnome-screensaver: | |
status: | Unknown → New |
Changed in gnome-screensaver: | |
status: | New → Fix Released |
And BTW, when the box I mention is unchecked, the screensaver simply fails to load.