Bug 151547 - Restoring lock session does not restore correct screen saver timeout
Summary: Restoring lock session does not restore correct screen saver timeout
Status: RESOLVED FIXED
Alias: None
Product: kcontrol
Classification: Unmaintained
Component: kcmscreensaver (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords: needs_verification
Depends on:
Blocks:
 
Reported: 2007-10-30 05:17 UTC by rfc469
Modified: 2008-11-25 06:42 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rfc469 2007-10-30 05:17:22 UTC 
Version:            (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
Compiler:          gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1) 
OS:                Linux

I have the screen saver disabled in the KDE Control Center.  As expected when I run "xset q" it confirms the screen saver timeout is 0.

When I select Lock Session the screen blanks immediately.  I enter my password and the screen unlocks.  Here's the problem: my screen saver timeout is now 70 instead of 0.  Apparently because the timeout in kdesktoprc is 70.

As a workaround I've been having to run "xset s 0" in a shell every time I unlock my session.  That's a couple times/day, every day for the past year or so.
Comment 1 FiNeX 2008-11-24 13:25:29 UTC 
Do you have the same problem even with more recent KDE version like KDE 3.5.10 or KDE 4?
Comment 2 rfc469 2008-11-25 06:42:26 UTC 
Sorry I think this was fixed in either 3.5.8 or 3.5.9.  Thanks for checking!