From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724 Description of problem: The "starwars" screensaver locks up my computer hard when I try and exit it. A hardware reset is necessary. All other screensavers work fine. Version-Release number of selected component (if applicable): xscreensaver-4.05-2 How reproducible: Always Steps to Reproduce: 1.Preview "starwars" screensaver 2.Read a bit of the kernel readme 3.Press esc and BAM! Actual Results: Computer locks up Expected Results: Back to my desktop... Additional info: I made sure the file was not corrupt with rpm -V. All the other screensavers work fine. "Starwars" is in the default "Random" screensaver group, so if it's iffy, maybe it should be disabled...
What sort of video card do you have?
I had a Matrox G200 when I opened this bug report. I know have a ATI Radeon 7000, and that screensaver does not lock up on me anymore.
Tim Smith has found a bug in the DRI locking which is believed to account for this. We may have a test fix soon.
Also locks up on an ATI 7500 Radeon VE: (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (--) RADEON(0): Chipset: "ATI Radeon VE QY (AGP)" (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xc0000000 (--) RADEON(0): MMIO registers at 0xcfef0000 (--) RADEON(0): BIOS at 0xcfec0000 (--) RADEON(0): VideoRAM: 65536 kByte (64-bit SDR SDRAM)
Well, this just locked up on me with my Radeon 7000, so I'll be able to test it after all...
It'll lock up on *every* card that uses the DRI. To provoke it reliably, crank the rotation/speed etc. sliders for the "starwars" screensaver to maximum using xscreensaver-demo.
This problem is believed to be fixed now, and affected pretty much all DRI enabled drivers. Please test the latest rawhide X and kernel either using the Red Hat Linux (Null) beta, or once the new release of Red Hat Linux is completed and released. After testing this out with our latest kernel/X, please provide updated status, and if the problem persists, please attach your X server log and config file. Most likely however, the problem will not occur in the lastest packages.
Closing as fixed in RAWHIDE, as no users have reported the problem persisting for quite some time now since the packages have been updated.