Bug 145957

Summary:	Although disabled screensaver starts automatically after locking screen
Product:	[Unmaintained] kscreensaver	Reporter:	Olivier Vitrat <ovit.debian>
Component:	general	Assignee:	kscreensaver bugs tracking <kscreensaver-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Olivier Vitrat 2007-05-25 16:14:56 UTC

Version:            (using KDE KDE 3.5.5)
Installed from:    Debian stable Packages

Reported in Debian BTS at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380544


I have wondered why my screen sometimes blanks after 5 minutes even 
though power management is set to 30 minutes. I found out that i had the 
5 minutes set up in the KDE screensaver-dialog, but that the screensaver
itself was disabled. Using "xset q" i found out that after changing 
that value to (lets say) 20 minutes the scrensaver values are correct:

Excerpt from 'xset q'
---------------------
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
---------------------

(to change the value i had to activate the scrensaver, change the value, 
then deactivate it again)

If i now lock the screen of my computer with the KDE-lockicon in the 
taskbar the screensaver comes up (as configured and expected). But after 
unlocking the screen the screensaver somehow has read its timeout-value 
from the config-file, even though it is still disabled:

Excerpt from 'xset q'
---------------------
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  1210    cycle:  600
---------------------

The timeout-value in the X-Server will return to zero if you change the 
timeout in KDE as described above.

The workaround is obvious: set the timeout to a value that will not 
disturb you (like 240 minutes, your eyes would be squares by then ;-) 
but it irks me and may confuse people, hence i reported that little 
bug...

Comment 1 Milko Krachounov 2007-09-20 21:09:42 UTC

(Disclaimer: I cite KDE versions below. From my memory. I'm terrible at remembering numbers, they can be wrong by magnitude of 10.)

I can confirm this. It happens on my two PCs since forever (it was intruduced in KDE 3.5.0 or one of the first versions afterwards). I was about to post a bug report, as I was able to find a way to reproduce it, until I found yours.

I'm using Gentoo, and the bug was fixed in a patch that the ebuild for KDE was applying in KDE 3.5.4, but the patch was removed, and I didn't have time to adapt the patch for newer versions.

It renders my desktop PC completely unusable after locking, as it sets the screensaver timeout to 9 seconds. It doesn't matter what KDE screensaver is configured to, it simply does so. I tried setting KDE screensaver to 357913941 minutes, and it still happens.

Here is output from 'xset q' before and after locking:

On my desktop PC (x86):

$ xset q  > 1
$ xset q  > 2
$ diff 1 2
12,13c12,13
<   prefer blanking:  yes    allow exposures:  no
<   timeout:  0    cycle:  600
---
>   prefer blanking:  yes    allow exposures:  yes
>   timeout:  9    cycle:  600

On my laptop PC (x86_64):

$ xset q > 1
$ xset q > 2
$ diff 1 2
12,13c12,13
<   prefer blanking:  yes    allow exposures:  no
<   timeout:  0    cycle:  600
---
>   prefer blanking:  yes    allow exposures:  yes
>   timeout:  310    cycle:  600

Comment 2 Milko Krachounov 2007-09-20 21:11:04 UTC

Another note, I was using Slackware on my desktop before. The 9 seconds thing is from there.

Comment 3 Milko Krachounov 2007-09-21 12:18:45 UTC

Ok I just "fixed" this on my desktop, KDE 3.5.7. Setting the timeout to "6001 минута" fixed it. I was trying to set it to "600", but the input box doesn't work and it does append the string "1 минута" to any value I enter.

Comment 4 Oswald Buddenhagen 2007-11-01 19:25:55 UTC

fixed for kde 4.0 and 3.5.9