Bug 142852

Summary:	kde screensaver does not start automatically after the specified period of time, if gnome-settings-daemon is running
Product:	[Unmaintained] kcontrol	Reporter:	Vadym Krevs <vkrevs>
Component:	kcmscreensaver	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bernhard, maksim, oliver.henshaw
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	4.10
Sentry Crash Report:

Description Vadym Krevs 2007-03-11 23:19:39 UTC

Version:            (using KDE 3.5.6 "release 31.4" , openSUSE )
Compiler:          Target: x86_64-suse-linux
OS:                Linux (x86_64) release 2.6.18.8-0.1-default

It seems that "Bug 20610: kcmscreensaver wait time" is back in the latest KDE 3.5.6 packages for openSuSE 10.2 for x86_64. 

My screensaver settings in the KDE control center are as follows:

Screen saver: "Random"
Start Automatically: checked
After: 1 min
Require password to stop: not checked

After 1 minute of inactivity nothing happens. Two minutes, threee, ... finally the "Sproinges (GL)" screensaver starts. Then I hit a key to dismiss the screensaver, wait for 1,2,3,... minutes and, guess what, the same "Sproinges (GL)" screensaver starts again! So much for "random" screensaver setting.

SuSE rpm versions:
xscreensaver-5.01-14
kdebase3-3.5.6-42.3
kdelibs3-3.5.6-31.4

There is also nothing special about 1 minute time interval - I've tried 2,3,4,5 - same effect. The screensaver seems to start at its own wish and there is no randomness at all.

Comment 1 Vadym Krevs 2007-03-18 22:32:58 UTC

Also, renaming /usr/lib64/xscreensaver/sproinges causes a blanc screen to be displayed instead of any screensaver.

Comment 2 Vadym Krevs 2007-04-01 21:06:19 UTC

It seems that gnome-settings-daemon is the culprit. My KDE session is configured to automatically start gnome-settings-daemon via a symlink in .kde/Autostart. Basically, if gnome-settings-daemon is running, then KDE screensaver never starts. If I disable automatic startup of gnome-settings-daemon, then KDE screensavers work fine until a gnome/gtk application is started, at which point gnome-settings-daemon is started, and KDE screensaver gets disabled again.

Comment 3 Maksim Orlovich 2013-03-04 18:12:03 UTC

FWIW just ran into this helping migrate a co-worker, to 4.8.5. The root cause appears to be that gnome-settings-daemon sets all DPMS time outs to 0, which the xautolock code interprets as an app blocking a screensaver. Not sure if this is still the case with the 4.10 version of the code.

Comment 4 Oliver Henshaw 2013-03-12 16:11:18 UTC

Yep. The new screenlocker isn't sensitive to how the DPMS timeouts are set anymore.