Description of problem: After upgrading to the current version of xscreenaver and rebooting the machine most xscreensaver demo's crash the gnome session on my Acer1700. Version-Release number of selected component (if applicable): 5.03-12.fc7 How reproducible: do not know, since I did this on one machine only. Steps to Reproduce: 1.upgrade xscreensaver packages to 5.03-12.fc7 2.reboot 3.run xscreensaver either as screensaver or demo's in "preview" mode Actual results: crash of gnome session Expected results: nice annimation on the screen Additional info:
What video driver, and which screensavers?
It is a SIS M650 video card, using a "standard" driver from F8. Most demo's crash i.e : I just let it crash with Voronoi But the same holds for many others
Sorry I'm not running F8 but F7.
I'm not sure, but I think all GL-modes give the problem
Would you "attach" the following? - /etc/X11/xorg.conf - /var/log/Xorg.0.log - the result of "rpm -qa | sort" Please don't write directly on this bug report but attach the log.
Created attachment 243561 [details] /etc/X11/xorg.conf
Created attachment 243571 [details] /var/log/Xorg.0.log
Created attachment 243581 [details] output of "rpm -qa | sort"
(In reply to comment #8) > Created an attachment (id=243581) [edit] > output of "rpm -qa | sort" > xscreensaver-5.03-12.fc7 xscreensaver-base-5.03-12.fc7 xscreensaver-debuginfo-5.03-12.fc7 xscreensaver-extras-5.03-12.fc7 xscreensaver-gl-extras-5.03-12.fc7 Well, this should not be. Did you upgrade xscreensaver by yum? Now xscreensaver-gl-extras 5.03-12.fc7 requires xscreensaver-gl-base $ rpm -qp --requires xscreensaver-gl-extras-5.03-12.fc7.i386.rpm | grep xscreensaver xscreensaver-gl-base = 1:5.03-12.fc7
thanks that helped. I sed yumex to update. As far as I know this is a graphical shell around yum. It should have picked up the dependencies. Jouk
So would you check if your problem still appears if you install xscreensaver-gl-base?
As I said: it helped. The problem is gone after installation of xscreensaver-gl-base
Oh.. I missed it... (In reply to comment #10) > thanks that helped. Thank you for verifing this. *** This bug has been marked as a duplicate of 336331 ***
*** Bug 361741 has been marked as a duplicate of this bug. ***