Bug 88246 - Install of kdeartwork3-xscreensaver package breaks screensaver function
Summary: Install of kdeartwork3-xscreensaver package breaks screensaver function
Status: RESOLVED DUPLICATE of bug 87889
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmscreensaver (show other bugs)
Version: 2.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-27 18:38 UTC by Jon Roland
Modified: 2008-06-18 22:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jon Roland 2004-08-27 18:38:59 UTC
Version:           2.0 (using KDE 3.3.0, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.104-default

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 screensavers".
Comment 1 Chris Howells 2004-08-27 23:29:59 UTC

*** This bug has been marked as a duplicate of 87889 ***