Bug 139139

Summary:	cannot set advanced settings for legacy screensavers
Product:	[Unmaintained] kscreensaver	Reporter:	Oliver Grimm <logistikka>
Component:	general	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED INTENTIONAL
Severity:	normal	CC:	khashayar.lists, mgraesslin, soren
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Oliver Grimm 2006-12-22 20:07:13 UTC

Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

With XScreensaver some of the available savers have a tab "advanced settings" that is not available in KScreensaver. To reproduce do

- right click the KDE desktop background
- choose "set up desktop"
- choose "screen saver"
- choose screen saver "GL slideshow"
- click "settings"
- read the info text: it says "...to set up the working directory see advanced settings"
- there is no button "advanced settings" to click

Comment 1 Oliver Grimm 2007-06-03 23:33:56 UTC

still a bug in KDE 3.5.7

Comment 2 Oliver Grimm 2008-03-02 13:48:11 UTC

still a bug in KDE 3.5.8

Comment 3 Oliver Grimm 2008-05-26 13:10:56 UTC

still a bug in KDE 3.5.9

Comment 4 Oliver Grimm 2008-12-07 16:19:14 UTC

still a bug in KDE 3.5.10

Comment 5 Soren Stoutner 2012-09-04 04:00:46 UTC

This is a duplicate of bug 306228:

https://bugs.kde.org/show_bug.cgi?id=306228

Comment 6 Oswald Buddenhagen 2012-09-04 04:37:58 UTC

*** Bug 201671 has been marked as a duplicate of this bug. ***

Comment 7 Oswald Buddenhagen 2012-09-04 04:38:21 UTC

*** Bug 306228 has been marked as a duplicate of this bug. ***

Comment 8 Martin Flöser 2015-01-23 14:40:05 UTC

The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.