Bug#180107: xserver-xfree86: [ati/radeon] SEGVs when using NerveRot xscreensaver hack with the default or dense settings
Brice, Did any of you guys reproduce the problem recently? I've not seen it for a long time. Cheers, Markus
Bug#180107: xserver-xfree86: [ati/radeon] SEGVs when using NerveRot xscreensaver hack with the default or dense settings
Brice Goglin wrote: Hi, About 4 yours ago, you reported (or replied to) a bug in the Debian BTS regarding a crash related to screensaver and GL. The issue has been discussed until 2004. But now, the only recent followup to this bug seems to be unrelated. Did any of you guys reproduce the problem recently? If not, I will close this bug in the next weeks. It's fixed for me, at least :) -Stian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#180107: xserver-xfree86: [ati/radeon] SEGVs when using NerveRot xscreensaver hack with the default or dense settings
On Sat, Jan 06, 2007 at 01:32:53AM +0100, Brice Goglin wrote: Hi, About 4 yours ago, you reported (or replied to) a bug in the Debian BTS regarding a crash related to screensaver and GL. The issue has been discussed until 2004. But now, the only recent followup to this bug seems to be unrelated. Did any of you guys reproduce the problem recently? If not, I will close this bug in the next weeks. I had to reinstall the notebook a couple of times since then, so the software installation has changed, ie I am using xorg now. I did not have xscreensaver-gl installed, but I did just now and there is no problem running atlantis or nerverot on the machine. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#180107: xserver-xfree86: [ati/radeon] SEGVs when using NerveRot xscreensaver hack with the default or dense settings
Hi, About 4 yours ago, you reported (or replied to) a bug in the Debian BTS regarding a crash related to screensaver and GL. The issue has been discussed until 2004. But now, the only recent followup to this bug seems to be unrelated. Did any of you guys reproduce the problem recently? If not, I will close this bug in the next weeks. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]