Bug 620186 - The fading of the screen when GNOME screensaver start is not interruptible
Summary: The fading of the screen when GNOME screensaver start is not interruptible
Keywords:
Status: CLOSED DUPLICATE of bug 620264
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-01 13:16 UTC by Akos Ladanyi
Modified: 2015-01-14 23:25 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-08 16:01:35 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Akos Ladanyi 2010-08-01 13:16:05 UTC 
When GNOME screensaver starts to blank the screen there is a fading effect which takes a few seconds and is not interruptible by moving the mouse or pressing keys. This is very annoying. This should be interruptible by input actions, like the screensaver.
Comment 1 Matt Chan 2010-08-08 16:00:33 UTC 
I can confirm this behaviour. It has been present since the switch to F13. In previous versions, the screensaver fade would deactivate if keys are pressed or if the mouse is moved. However, in F13 it seems that the screensaver will fully fade to lock no matter what you do.
Comment 2 Matt Chan 2010-08-08 16:01:35 UTC 

*** This bug has been marked as a duplicate of bug 620264 ***
Comment 3 Tim Taiwanese Liim 2010-08-10 04:21:21 UTC 
These 4 bugs seems to be related, or are the same one.
  bug612620 Fade-out to screensaver cannot be interrupted 
            with xorg-x11-server-Xorg-1.8.2-1.fc13
  bug615786 As screensaver activates and screen dims cannot intervene 
            with mouse/keys
  bug620186 The fading of the screen when GNOME screensaver start is 
            not interruptible  
  bug620264 gnome-screensaver activates whether or not activity occurs 
            once dimming starts
Note You need to log in before you can comment on or make changes to this bug.