Bug 129062

Summary:	odd kscreensaver dpms interaction
Product:	[Unmaintained] kscreensaver	Reporter:	Colin J Thomson <colin.thomson>
Component:	general	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	rdieter
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Colin J Thomson 2006-06-12 21:19:48 UTC

Version:            (using KDE KDE 3.5.3)
Installed from:    Fedora RPMs

Screensaver works only once after login. FC4, kde-redhat-3.5.3 RPMS. 
Rex applied the Patch from bug #128610 which helped, in that the Screen went "black" after the set period however none of the Screensavers worked.
So I set "Enable display power management" in Peripherals > Display On and set all options to "disabled" then the Screensaver worked but only once. 
IE the Screensaver works once here after initial login, but there after fails to start.
Locking the screen manually works fine.

Comment 1 Chris Jones 2006-06-18 23:22:37 UTC

I can confirm, I also see this problem, using the same KDE redhat RPMS

Comment 2 artklein99 2006-07-14 22:55:24 UTC

I had the same problem while using Fedora Core 3 and the kde-redhat rpms for version 3.5.3. This issue has been fixed for me with an updated kdebase version with, from the change log, the "use [of] freebsd's xscreensaver patch".

The kdebase version I am using is:
kdebase-3.5.3-9.1.fc3.kde

Comment 3 Colin J Thomson 2006-07-24 18:56:11 UTC

FYI its 99% fixed here, if you boot your machine and don't do *anything* when the Screensaver activates you will get a blank screen. There after the Screensaver starts up fine.
(2) Booting the machine and working straight away, the Screensaver behaves as it should.

kdebase-3.5.3-9.1.fc4.kde

Comment 4 johnfw 2006-11-02 02:18:34 UTC

*** This bug has been confirmed by popular vote. ***

Comment 5 Oswald Buddenhagen 2007-05-18 21:37:39 UTC

i'm pretty convinced that this *is* the same ...

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