Bug 73849 - Xscreensaver dies randomly on Millennium II system
Summary: Xscreensaver dies randomly on Millennium II system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver
Version: 8.0
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-12 05:34 UTC by Todd Nemanich
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-10 20:19:22 UTC
Embargoed:


Attachments (Terms of Use)
output from xscreensaver (61.15 KB, text/plain)
2002-09-12 05:35 UTC, Todd Nemanich
no flags Details

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


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