I'm trying to configure my screensaver in Ubuntu/Kubuntu install from the KDE system settings. Whenever I try though, it causes kdesktop to crash and then eventually reload, and systemsettings closes (crashes? it doesn't reload or give a crash handler dialog). It happens during the point after selecting "screensavers" and the list of screensavers being generated, the configuration screen itself does load and apparently querying the available screensavers is where the issue happens.

On top of that according to the window before systemsettings and kdesktop go away it's not configured to ask for a password to get out of the screensaver, but it seems to be presently set for lock screensaver.

what's going on? This is kde3, not kde4 btw.

I installed 7.10 a week ago and found the same or similar problem with its screensaver. It would freeze up so I would have to reboot. I found a button on the screensaver dialog box that allows a person to turn it off. That doesn't solve the problem but it does stop the system from freezing.

I definitely had the same issue.
However from my experience, I think the issue was more of problem with the more graphic extensive Screensavers.
I didn't really take the time to find out why it happened.
I just changed my setting to ensure it would not happen as often.

See, I can't even select a screensaver. It's the settings dialog for the screensaver that are giving me fits. The screensaver can kick on (though I think it's only set to "blank"). This issues I've seen aren't the screensaver itself locking up... though I've seen various GL screensavers irrecoverably crash a system in RH, SUSE, and Debian in every incarnation since they were first part of the screensavers selections.

What I don't get is it asking for the password when that's not selected during that brief glimpse of the settings before it and kdesktop disappear, and also why system settings and kdesktop don't like that settings option. Does Ubuntu use some centralised screensaver setting that has to be controled from another utility perhaps?