Bug 156644 - Frozen when kscreensaver *assumes* that the screen is off
Summary: Frozen when kscreensaver *assumes* that the screen is off
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-25 14:25 UTC by David
Modified: 2015-01-26 07:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2008-01-25 14:25:18 UTC
Version:            (using KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The screensaver starts after x minutes, then the screen switches off after y minutes, everything OK.

The problem comes when, very often, the screen switches on again spontaneously (I do not know why), kscreensaver does not realise, and the animation stays frozen. 

The only workaround afaik is to select black screen as the screensaver (and I do not like it :-)  ).

OK, you can claim that the bug is really in another application (energy saving?), but I think it is not a excuse for kscreensaver :-)  I left the computer overnight and this morning I saw the screensaver frozen. How many hours will it have been damaging the monitor?

It is sensible to stop the screensaver when the screen is supposed to be off, in order not to consume memory. But then we have this bug. Maybe a compromise solution could be, when the screen goes off, to switch the screensaver to black screen, instead of just freezing the animation.
Comment 1 Martin Flöser 2015-01-26 07:45:02 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.