Description of problem: I installed xscreensaver-extras-5.03-1.fc6.1 and set my laptop up to do random screensavers. After running overnight, I found my laptop locked up and unresponsive. I ran each screen saver on my laptop to determine which ones were causing problems, and I found that these four will peg the CPU at 100% and render my machine unresponsive: IMSmap Interaggregate Vermiculate WhirlwindWarp Version-Release number of selected component (if applicable): xscreensaver-extras-5.03-1.fc6.1 How reproducible: Run the above screensaver Actual results: Laptop locks up - it is unresponsive from the keyboard but the mouse still works. Expected results: No lockup. Additional info: This is a Lenovo Thinkpad T60 with Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03) Note that I installed the xscreensaver packages from FC6 on RHEL 5, but I tested with FC6 as well and it does the same thing there.
Created attachment 207841 [details] sysreport for my laptop
Once reassign to X. Xgl maintainers, would you help?
Created attachment 208421 [details] Xorg.0.log from sysreport
Created attachment 208431 [details] xorg.conf from sysreport
Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it here.]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. {This is mass-closing of all obsolete bugs; if this bug was in your opinion closed by mistake, please, reopen it with additional information; thanks a lot and I am sorry for bothering you in such case.}