Version: (using KDE KDE 3.3.0) Installed from: SuSE RPMs OS: Linux When I choose a screensaver nothing happens. The preview doesn't show anything and Test only produces a short flicker, when I press a key or the mouse.
I've had the same problem. The screensaver components from KDE are expecting the xscreensaver files in /usr/lib/xscreensaver, but SuSe installs the files in /usr/X11/lib/xscreensaver. 1. This should be configurable 2. As a workaround create a symlink from /usr/lib/xscreensaver to /usr/X11/lib/xscreensaver and re-login
Thanks for the workaround.
*** Bug 88246 has been marked as a duplicate of this bug. ***
Since Bug 88246 has been marked as a duplicate of this bug, it seems appropriate to copy my report here. ---- Downloaded and ran rpm for kdeartwork3-xscreensaver obtained from both kde.org and and from SuSE site. After this was done, more screensavers appeared in listing of Control Center, but none of them work. Just get blank screen after timeout to launch screensavers. When I double-click on any screensaver, get error "Screensaver not configured", but did run SuSEconfig after running the rpm scripts. After further investigation under the GUI, I found that when the function tries to launch a screensaver, an error is produced -- kxsconfig: Cannot connect to X server. It is not obvious how I might configure these screensavers. Resolved the problem temporarily by removing the kdeartwork3-xscreensaver package, but find that some of the remaining screensavers, the ones that were installed with the original SuSE 9.1 CDs, now are also not configured, so that when the Random selection picks one, just get a white screen with an error message "Screensaver not cofigured", or a blank dark screen. The Control Center, when one gets a "not configured" error, should offer a button to "Configure the screensaver" or "Configure all ------ Additional comment: This problem is not associated only with the rpm from the SuSE site or using YaST as the installer. It also occurred using the rpm from ftp://ftp.gtlib.cc.gatech.edu/pub/kde/stable.3.3/SuSE/ix86/9.1/ which is linked from kde.org. It also is not limited to the new screensavers but also breaks the old ones, which does not sound like just installing them in the wrong directory.
One more point: After installing the kdeartwork3.xscreensaver package, all the new screensavers were listed along with the old ones by kcontrol. If the installation directory is the only thing that is going on, one would expect the listing to include only the new screensavers, or only the old ones. One would also not expect some of the old screensavers to remain unconfigured after removing the new kdeartwork3-xscreensaver package.
Okay, created the symlink from /usr/lib/xscreensaver to /usr/X11/lib/screensaver and reinstalled the kdeartwork3.xscreensaver rpm. It does indeed now seem to work as expected.
But I notice one other thing that seems anomalous. A screen saver how begins, as expected, but then, after running for 6 minutes, the screen goes blank for 30 minutes, then the screensaver resumes again and continues thereafter. Anyone else experience this blackout period?
I am having the same problem. When I create the link, I can see the screensavers in both preview and actual mode but I still can't configure them. I am having this problem on my home computer. I had the same problem at work but I managed to fix it somehow. All I can remember is that it was either a permissions issue (which doesn't seem likely as they are fine on my home pc) or I reinstalled the kdeartwork3 package and then it started working.
I "fixed" the problem on my home computer by removing kdeartwork3-xscreensaver-3.3.0-3 through yast and then installing version 3.2.1 from the SuSE 9.1 CD's. Everything seems to work fine now.
imo, this was simply a packaging bug. trying to deal with every installation problem automatically would be counterproductive.