Bug 290611 - cancelling fade out with mouse movement doesn't restore gamma settings
Summary: cancelling fade out with mouse movement doesn't restore gamma settings
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 7
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F8Target
TreeView+ depends on / blocked
 
Reported: 2007-09-14 10:38 UTC by James
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-09 17:58:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description James 2007-09-14 10:38:15 UTC
Description of problem:
Moving the mouse shortly after fade-out, but before the screensaver itself has
started, results in a black screen that cannot be unlocked. Session must be killed.

Version-Release number of selected component (if applicable):
gnome-screensaver-2.18.2-2.fc7

How reproducible:
Consistently

Steps to Reproduce:
1. Wait for fade-out.
2. Move mouse before screensaver starts, while screen is still black.
  
Actual results:
Session locks, no unlock dialog.

Expected results:
Unlock dialog, return to the session.

Comment 1 Ray Strode [halfline] 2007-09-14 13:29:54 UTC
if you type

alt-f2

xgamma -gamma 1.0

("in the dark" so to speak)

does it come back to life?

Adding to F8Target

Comment 2 James 2007-09-14 14:42:11 UTC
It do (with DISPLAY and XAUTHORITY environment variables set).

Comment 3 James 2007-09-14 14:45:08 UTC
[Should probably clarify above that I went through a text-mode console.]

Comment 4 Matthias Clasen 2007-10-09 17:57:29 UTC
Can you try again with current gnome-screensaver packages ? Ray added a patch
that should fix this problem.

Comment 5 Matthias Clasen 2007-10-09 17:58:24 UTC
Oh, sorry, I just see that this bug is against F7. 
The fix will be available in F8.


Note You need to log in before you can comment on or make changes to this bug.