Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 77682 - Blaster/Critical xscreensaver hacks lock system
Blaster/Critical xscreensaver hacks lock system
Status: CLOSED DUPLICATE of bug 64419
Product: Red Hat Linux
Classification: Retired
Component: xscreensaver (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 2002-11-11 17:54 EST by Peter Fales
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-11 17:54:46 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 Peter Fales 2002-11-11 17:54:40 EST
Description of Problem:

On the IBM Thinkpad T23 (uses the S3 Savage), running the xscreensaver hacks
"Blaster" and "Critical" cause hard lockups.  (No response to mouse/keyboard,
and network connections are also dead.  This is not a problem on other systems.

How Reproducible:


Steps to Reproduce:
1. On an IBM Thinkpad T23, run xscreensaver-dem
2. Select Blaster, and click "Demo"
3. Be prepared to reboot the system

Actual Results:

System locks up

Expected Results:

No lockup 

Additional Information:  XF86Config-4 is pretty generic - built with
Comment 1 Bill Nottingham 2002-11-11 19:14:08 EST

*** This bug has been marked as a duplicate of 64419 ***
Comment 2 Peter Fales 2002-11-12 09:44:52 EST
Tracing the dependency tree back to bug 64166 and bug 63916 implies that the
bug is closed because it's fixed in XFree86 4.05.  However, we're still seeing
the problem in RedHat 7.3 which used XFree86 4.2.  Did the XFree86 fix or
the the blaster fix get lost somewhere along the way.
Comment 3 Bill Nottingham 2002-11-12 11:28:44 EST
It's fixed in *xscreensaver-4.05*, although the underlying issue is an XFree86
driver bug in the savage driver.

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