GNOME Bugzilla – Bug 594082
gnome-screensaver ignores input when fading to black
Last modified: 2010-09-07 14:26:07 UTC
Description of problem: This issue was observed in Fedora 11. I took much of the description from [1] directly. When gnome-screensaver is fading the screen to black, it doesn't pay any attention to user input that should interrupt the fade and give me my normal interaction back. Version-Release number of selected component (if applicable): gnome-screensaver-2.26.1-2.fc11.i586 How reproducible: always Steps to Reproduce: 1. set g-ssaver idle delay to 1 minute, Lock screen when active, theme=Cosmos (any theme will do). 2. Wait 1 minute. 3. Watch the screen start to fade, wiggle the mouse, hit a key. 4. The screen still locks. Actual results: The screen fades to black and locks, but it takes a couple of seconds. Expected results: Either the screen should immediately drop into locked mode and present me with a password input (much less desirable, but okay), or it should restore me to normal interaction. Having it ignore my input, then fade to black, and require me to hit another key after waiting for the fade to complete, is impressively frustrating considering how minor it sounds. Additional Info: [1] Original bug in Fedora 11, reported by Bryan O'Sullivan: https://bugzilla.redhat.com/show_bug.cgi?id=508979 bug508979 gnome-screensaver ignores input when fading to black 2. In Fedora 10, g-ssaver worked fine; the fade was interruptible. gnome-screensaver-2.24.1-2.fc10.i386.rpm
Having the same problem. Exceptionally annoying in my case since I set my screensaver to a 1 or 2 minute activation for security reasons. It does seem that the fade is slower in these cases, as James Ettle from the Feodra bug states, but I was assuming that was my imagination. The problem seems to be more likely the longer the user has been logged-in. For example, if I restart my computer, the first time or first few times it starts to fade, I can recover by moving my mouse. However, eventually the problem starts and it does not go away until I restart my machine (perhaps logging out would accomplish the same goal, I do not know).
This problem went away for me after this morning's Fedora 11 updates were installed. In case this is relevant(?): Sep 12 06:45:57 Updated: lohit-fonts-common-2.4.0-1.fc11.noarch Sep 12 06:45:58 Updated: gnome-python2-extras-2.25.3-7.fc11.i586 Sep 12 06:46:27 Updated: selinux-policy-3.6.12-82.fc11.noarch Sep 12 06:46:28 Installed: wine-fonts-1.1.29-1.fc11.noarch Sep 12 06:47:03 Updated: selinux-policy-targeted-3.6.12-82.fc11.noarch Sep 12 06:47:06 Updated: lohit-maithili-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:09 Updated: lohit-telugu-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:12 Updated: lohit-hindi-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:15 Updated: lohit-kannada-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:18 Updated: lohit-punjabi-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:21 Updated: lohit-gujarati-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:24 Updated: lohit-bengali-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:27 Updated: lohit-tamil-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:30 Updated: lohit-oriya-fonts-2.4.0-1.fc11.noarch Sep 12 06:47:51 Installed: wine-core-1.1.29-1.fc11.i586 Sep 12 06:47:57 Updated: xulrunner-1.9.1.3-1.fc11.i586 Sep 12 06:47:59 Updated: gnome-python2-gtkmozembed-2.25.3-7.fc11.i586 Sep 12 06:48:00 Updated: wine-cms-1.1.29-1.fc11.i586 Sep 12 06:48:01 Updated: wine-pulseaudio-1.1.29-1.fc11.i586 Sep 12 06:48:01 Updated: wine-ldap-1.1.29-1.fc11.i586 Sep 12 06:48:02 Updated: wine-capi-1.1.29-1.fc11.i586 Sep 12 06:48:03 Updated: wine-twain-1.1.29-1.fc11.i586 Sep 12 06:48:04 Updated: cloog-ppl-0.15.7-1.fc11.i586 Sep 12 06:48:06 Updated: postgresql-libs-8.3.8-1.fc11.i586 Sep 12 06:48:21 Updated: Miro-2.5.2-4.fc11.i586 Sep 12 06:48:47 Updated: yelp-2.26.0-7.fc11.i586 Sep 12 06:48:49 Updated: wine-nas-1.1.29-1.fc11.i586 Sep 12 06:48:50 Updated: wine-jack-1.1.29-1.fc11.i586 Sep 12 06:48:51 Updated: wine-esd-1.1.29-1.fc11.i586 Sep 12 06:48:52 Updated: gnome-python2-libegg-2.25.3-7.fc11.i586 Sep 12 06:48:53 Updated: gnome-python2-gtkhtml2-2.25.3-7.fc11.i586 Sep 12 06:48:54 Updated: alsa-plugins-pulseaudio-1.0.21-2.fc11.i586 Sep 12 06:48:55 Updated: wine-desktop-1.1.29-1.fc11.noarch Sep 12 06:48:57 Installed: wine-common-1.1.29-1.fc11.noarch Sep 12 06:49:02 Updated: firefox-3.5.3-1.fc11.i586 Sep 12 06:49:03 Updated: wine-1.1.29-1.fc11.i586 Sep 12 06:49:30 Erased: wine-tools
Me too, problem went away; still no idea why/how. Good anyway. Close this bug.
Please close this bug, since it's verified. I tried to close it just now, but had no permission. Thanks for fixing this issue!
I'm using gnome-screensaver 2.30.0 and am experiencing this bug. If I catch it early enough in the fade sequence then it'll stop fading, but after 1-2 seconds I have to wait for the fade to complete before I can get my screen back. The fade takes about 10 seconds which is quite annoying. I'm using Arch Linux with the following related packages: - gnome-screensaver 2.30.0-2 - gnome-menus 2.30.2-1 - gnome-desktop 2.30.2-1 - libgnomekbd 2.30.2-1 - libxklavier 5.0-1 - libgl 7.8.2-1 - libnotify 0.4.5-1.1
Nikosapi, You are probably seeing a later incarnation of this bug (bug594082). Please see [1][2] for details. [1] bug612620 Fade-out to screensaver cannot be interrupted with xorg-x11-server-Xorg-1.8.2-1.fc13 https://bugzilla.redhat.com/show_bug.cgi?id=612620 [2] bug622651 Xext/sync.c IDLETIME counter sometimes fails to fire negative transition alarms https://bugzilla.redhat.com/show_bug.cgi?id=622651
Cool, thanks Tim! For the time being I've disabled the screensaver until one of your fixes gets accepted.
*** This bug has been marked as a duplicate of bug 625374 ***