Bug 167185 - SlideShow screen saver doesn't always terminate properly
Summary: SlideShow screen saver doesn't always terminate properly
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: screensavers (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-22 05:53 UTC by Ron Eggler
Modified: 2015-01-26 07:43 UTC (History)
1 user (show)

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 Ron Eggler 2008-07-22 05:53:25 UTC
Version:           4.1 RC1 (using KDE 4.0.98)
Installed from:    SuSE RPMs
OS:                Linux

Hey,

First of all: I experienced this bug with KDE 3.5.8 as well.
The slide show screen saver doesn't always seem to terminate properly on mouse move or key press. The image just stays on screen and sometimes it closes after ~1 Minute and other times it doesn't go back at all and all I can do is ctrl-alt-backspace to terminate the X-server and log back in. I can't make out any thing that would make it happen or not happen, it seems to happen approximately 7 out of 10 times maybe.
I actually found out about it by using this screensaver with AmarokScreenSaver (http://www.kde-apps.org/content/show.php/AmarokScreenSaver?content=46488)and when brining the author's attention to my issue I got told I should check if it may not be the SlideShow screen saver itself (instead of ASS). And this is where the problem seems to be. 
Anyone else experiencing this problem?
Comment 1 Martin Flöser 2015-01-26 07:43:31 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.