> One problem about this testing is that you have to reboot, then remove the package containing an offending screensaver
If you open gconf-editor and go to apps/gnomescreensaver, you can change the contents of the "themes" key, which is the selected saver (or all of them if you choose "random"). Leave gconf-editor open while you change screensaver properties and you'll see how it works. > Then I went back to Sonar - this time it locked the system up Sonar is actually a GL saver, in the wrong package. This is fixed in Debian but not yet in Ubuntu. Anyway, if it crashes (and does not cause system lock-up), you can provide debug information according to https://wiki.ubuntu.com/DebuggingProgramCrash - you might need to install libgl1-mesa-dri-dbg as well as the xscreensaver dbg packages. > I've attached my current xorg.conf in case there are any other settings I might try I am afraid I am not an openchrome expert, but maybe you could try Option "NoAccel" "true" which should make every very slow but stable. I guess I should reassign this bug to the openchrome driver. Can you please open a separate bug for the one saver that crashed without lock- up if you can reproduce it? ** Summary changed: - AntSpotlight screensaver causes system to lock up immediately + [K8M800] AntSpotlight screensaver causes system to lock up immediately ** Package changed: xscreensaver (Ubuntu) => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- [K8M800] AntSpotlight screensaver causes system to lock up immediately https://bugs.launchpad.net/bugs/455954 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in ubuntu. _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
