Bug 76536

Summary: Interrupting screensaver as it starts to fade to black leaves you unable to access access desktop
Product: [Retired] Red Hat Linux Reporter: Adrian Gartland <rhbugzilla>
Component: xscreensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-04 06:28:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adrian Gartland 2002-10-22 22:58:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020809

Description of problem:
After leaving computer idle (reading a long web page) the screen
saver kicks in and begins to fade to black. If you interrupt the mouse
as it begins to to fad to black it returns you to the the desktop
but there is no mouse or keyboard input.

A similar experience (had to do it a few times to make it break)
is to
[See "Steps to reproduce"]



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1) killall xscreensaver
2) run xscreensaver in an xterm
3) click settings
4) click "preview" and wiggle he mouse immidiately
   (might take a few attempts)
5) if 4) doesn't work....keep hammering the preview button
   so it goes in and out of the screensaver very quickly
   over and over.

Additional info:
The gfx card/driver I'm using is a geforce 2GTS with the
default redhat supplied nv driver

Comment 1 Ray Strode [halfline] 2004-11-04 06:28:27 UTC
Hi Adrian,

I assume this problem was fixed a long time ago.  I can't reproduce it
with a recent version of xscreensaver.  If you still experience
problems, feel free to reopen this bug report.