From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131
Description of problem:
When the screen saver on my workstation starts to activate there is a 3-5 second
period when it slowly "steps" to black. If I move my mouse during this period,
the screen saver doesn't unlock and I have to wait until the screen goes bnlack
before any mouse movement cancels the screen saver.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Wait until screen starts to step to black
2. Move mouse
Actual Results: Nothing happens.
Expected Results: Screen saver would immediately cancel.
I am using a Riva TNT2 with 4Mb and the "nv" driver. Monitor is "DCCPROBED" Generic
Millions Of Colors
Horizontal Sync: 30.0-70.0
Vertical refresh: 50.0-160.0
91dpi x 91dpi physical resolution
Here is the screen saver command line:
rorschach -root -offset 7
Please attach X server log and config file using the link below.
I think this is xscreensaver "behavior"
To reproduce: Hat/Lock Screen, immediately start constantly moving the mouse
Results: screen fades and screen saver is activated regardless of mouse activity
"Mouse or keyboard activity causes skipping of the fade-out effect and immediate
opening of the unlock dialog".
[The mouse movement might be accidental and not an attempt to skip the fade-out
effect, but since all it does is bring up the dialog, it does not matter much.]
Similarly, if the screensaver triggers due to idle time, the screensaver is
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.