Bug 79205 - system freezes when screensaver is running
system freezes when screensaver is running
Product: Red Hat Raw Hide
Classification: Retired
Component: XFree86 (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Mike A. Harris
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-12-07 03:15 EST by David Monniaux
Modified: 2007-04-18 12:48 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-12-19 01:47:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Monniaux 2002-12-07 03:15:44 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
[XFree86 4.2.99 CVS 0.20021126.8]

If the machine is left running alone for several hours, it runs the screensaver.
The system then freezes. I don't know whether it's actually X related, it's
still a hypothesis.

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

How reproducible:

Steps to Reproduce:
1.Run Gnome with the random screensaver setup
2.Leave machine alone for 8 hours

Actual Results:  Machine is frozen: it does not do anything if a key is pressed,
including Control-Alt-F1.

Expected Results:  It should have come back from the screensaver or switching
VCs depending on the key.

Additional info:

i830M chipset
Comment 1 Mike A. Harris 2002-12-08 07:47:16 EST
Please attach X log, config file, and /var/log/messages as individual
file attachments using link below.

Comment 2 Mike A. Harris 2002-12-11 13:18:33 EST
Comment 3 Mike A. Harris 2002-12-15 04:40:55 EST
This is likely related to bug #77345
Comment 4 Mike A. Harris 2002-12-19 01:47:31 EST
No feedback, means I can't do squat about this problem.  2 way communication
is needed in order to troubleshoot issues.  Closing bug WONTFIX.

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