Red Hat Bugzilla – Bug 615786
As screensaver activates and screen dims cannot intervene with mouse/keys
Last modified: 2015-01-14 18:25:58 EST
Description of problem:
As the screensaver kicks in at the appointed timeout the screen slowly dims - previously at this time hitting a key or moving the mouse would prevent the screensaver coming on and return to a normal screen.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Set screensaver timeout
2. Wait for screen to start dimming
3. Hit a key such as shift or move the mouse
No response and no return to normal screen, until after screensaver is running
Key press should stop progress of dimming and return to normal screen before screensaver is running.
Additional info: The package mesa-dri-drivers-experimental-7.8.1-6.fc13.i686 is installed. The machine is running stock f13 and no nvidia proprietary drivers are or have been installed at any stage - only nouveau
Hardware is http://www.smolts.org/client/show/pub_d467135e-c9f3-4344-ac73-9e7ab147b5a3
Kernel is kernel-PAE-22.214.171.124-147.fc13.i686
I forgot to mention - this is in gnome
I only use screen blanking - (put screen to sleep when inactive .. ) same problem. Was working fine up till a couple weeks ago - was about the time i added mesa-dri-drivers-experimental ... f13.
I was quite annoyed when this started happening on my systems (both upgraded to F13, one from F11, the other from F12) as well and am looking forward to the fading out period becoming responsive to keyboard/mouse action again.
As a quick workaround though, I have used gconf-editor to set /apps/gnome-screensaver/lock-delay to something larger than 0, e.g. 1 or 2. This gives me a minute or two (*after* the unstoppable fadeout) to get rid of the screensaver by waving around the mouse, without needing to enter my password again.
This very useful option was removed from the GUI a few years ago, but I am glad it is still implemented...
I'm experiencing this bug on two F13 boxes. Normally, if I notice the screen saver has timed out and started dimming the screen, I hit a key to stop it. But now, once the dimming has started all mouse and keyboard input is ignored, so there is no way to stop the screen saver from kicking in. I have to wait through the entire dimming sequence and then enter the password. This is incredibly annoying as it happens many times per day. As a work around, I've increased the amount of time before the screen saver turns on but would like to see this fixed ASAP.
It's happening on a Dell Inspiron 531S desktop machine with an ATI video card as well as on my ancient Dell Inspiron 8600 laptop which has an nVidia graphics card.
This bug was not present in F12, F11, or older version of Fedora. I don't think I noticed it when I first upgraded to F13. But I'm not sure exactly when it started.
This looks like it should link to #612620
These 4 bugs seems to be related, or are the same one.
bug612620 Fade-out to screensaver cannot be interrupted
bug615786 As screensaver activates and screen dims cannot intervene
bug620186 The fading of the screen when GNOME screensaver start is
bug620264 gnome-screensaver activates whether or not activity occurs
once dimming starts
Yes, it does. I'll mark this one as duplicate. Thanks for the heads up guys.
*** This bug has been marked as a duplicate of bug 612620 ***