Ubuntu
gnome-screensaver package

gnome-screensaver dialog MIA after resume

Bug #306319 reported by Noel J. Bergman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gnome-screensaver

This is not a duplicate of Bug 275957, even if the major consequence is the same. Bug 275957 is about a SIGSEGV in gnome-screensaver. That is not the problem here, given that (a) that particular defect appears to be fixed and (b) there are no log entries for gnome-screensaver, as there were for 275957.

Now, as for the specifics of THIS bug. Upon resume from suspend-to-RAM, after the system finishes waking up, the mouse pointer is present (yes, the the GUI one :-)), but the rest of the screen is blank. Typing and clicking don't cause anything to happen. Simply typing the password as if the dialog were invisible does not work.

What DOES work is simple: CTRL-ALT-F1, login, ps auxwww | grep gnome-screensaver-dialog, kill -HUP that process, CTRL-ALT-F7, and eh voila, there is the gnome-screensaver-dialog window.

I reported this exact same behavior against Fedora 10; it is not Ubuntu specific.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: gnome-screensaver 2.24.0-0ubuntu2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Uname: Linux 2.6.28-2-generic x86_64

Tags: apport-bug
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Revision history for this message
goto (gotolaunchpad) wrote :

I cannot help you with the bug directly, but you can add the fedora bug to the launchpad bug tracker here, so we have a better overview about this bug.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Actually, I just tested it on Fedora 10 after recent updates, and it no longer happens there.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

Not sure what's changed, but slightly new behavior now, matching what I had started to see with Fedora 10 yesterday.

Fedora 10 and Jaunty both give me the dialog when I recover from suspend, BUT it does not work -- the first time. The dialog accepts the fingerprint and/or password, says that it is checking, but fails and has to timeout. It works the second time.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

OK, I am becoming convinced that this defect is related to Bug 306310. If I suspend programmatically (via pm-suspend or menu) the problem described in this defect does not manifest. It only manifests if I suspend via hot-key.

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
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-screensaver (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Noel J. Bergman (noeljb) wrote :

Sorry, Pedro. I never saw your request. This defect was fixed for Jaunty ages ago, so it should be marked as FIX RELEASED.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.