Bug 73849

Summary: Xscreensaver dies randomly on Millennium II system
Product: [Retired] Red Hat Linux Reporter: Todd Nemanich <todd>
Component: xscreensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-10 20:19:22 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:
Attachments:
Description Flags
output from xscreensaver none

Description Todd Nemanich 2002-09-12 05:34:21 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020809

Description of problem:
Xscreensaver occasionally dies on my Matrox Millennium II system leaving no
errors in .xsession-errors

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


How reproducible:
Sometimes

Steps to Reproduce:
1. Start xscreensaver on a millennium II system
2. let the screensaver start, and possibly power down the monitor
3. repeat until xscreensaver does not start (usually takes several attempts)
	

Additional info:

As suggested, I ran the following to start xscreensaver:
xscreensaver -sync -verbose -no-capture 2> saverlog &
Comment 1 Todd Nemanich 2002-09-12 05:35:33 UTC 
Created attachment 75864 [details]
output from xscreensaver
Comment 2 Per Bothner 2002-09-17 15:05:08 UTC 
I too have the screensaver freeze up on (null).
I'm running Gnome.  /sbin/lspci says I have a
Millennium G400 with 16MB.  Let me know if you want me
to ty an experiemnts.  (I disabled the screensaver,
and haven't noticed any other serious problems.)
Comment 3 Ray Strode [halfline] 2004-11-10 20:19:22 UTC 
Hi,

This bug is quite old now.  Given the lack of activity on this report and the
likelihood that this bug has already been fixed, I am going to close it.  If you
encounter the problem discussed in this report with Fedora Core 3 or a recent
version of xscreensaver, feel free to reopen.

Thanks