Red Hat Bugzilla – Bug 64166
xscreensaver's blaster locks up requiring reboot
Last modified: 2014-03-16 22:27:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
Description of problem:
Code in blaster generates invalid coordinates for XDrawLine function calls
causing a freeze that requires reboot at least for savage4.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Select blaster in xscreensaver with either no parameters or combination that
allows laser fire among robots.
2. Let it run for a few seconds.
Actual Results: Screen freezes and will not respond to <CTRL><ALT><BACKSPACE>
or terminal switching. At least, it will generate some laser fire from robots
with random coordinates (extremely large positive and negative int values).
Expected Results: Screensaver should continue until terminated.
I have created a patch that fixes this problem.
Created attachment 55584 [details]
Patch to repair xscreensaver's blaster
this bug is very close to your bug:
that laptop also has S3 Savage videocard.
to you see any freezes with the critical screensaver ?
hayastan132, you are not going to believe this, but after posting my blaster
patch here, I did a query for other xscreensaver stuff and found bug 63916
before you posted under mine. LOL. I tried critical right after reading it and
it locked up my desktop just as you described it did on your laptop.
So it prompted me to create a patch for critical as well.
The connection I found was that the individual screensavers didn't initialize a
coordinate for XDrawLine which caused savage (or maybe others) drivers to crash.
Regardless of the driver used, the screensavers need to be corrected so it will
display properly with the correct coordinates, but something needs fixing in X
itself to keep it from crashing.
I'll post my critical patch and my findings under 63916.
*** Bug 64419 has been marked as a duplicate of this bug. ***
This appears to be fixed in 4.05-1.