From kde-bugs-dist  Tue Oct 31 23:42:32 2006
From: Chris Jenks <chris () jenks ! us>
Date: Tue, 31 Oct 2006 23:42:32 +0000
To: kde-bugs-dist
Subject: [Bug 128610] kscreensaver does not launch screensaver after x
Message-Id: <20061031234232.31009.qmail () ktown ! kde ! org>
X-MARC-Message: https://marc.info/?l=kde-bugs-dist&m=116233816617445

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=128610         




------- Additional Comments From chris jenks us  2006-11-01 00:42 -------
An update: Today my yum update downloaded a new version of KDE (3.5.5-0.2), so I thought this bug might be fixed. No, it isn't, and I was mistaken when I said that the bug is absent under root. I tracked the problem down to these lines in ~/.kde/share/config/kcmdisplayrc:

[DisplayEnergy]
displayEnergySaving=false
displayPowerOff=60
displayStandby=0
displaySuspend=30

  When a user account is first created, these lines are absent from kcmdisplayrc and the screensaver/session locking work properly. If Display Power Management is enabled, these lines are generated in kcmdisplayrc with displayEnergySaving set to true, and the screensaver/session locking continue to work properly. If the Display Power Management is then disabled, the lines are retained in kcmdisplayrc but displayEnergySaving is set to false - and this causes the screensaver to fail to start and the session to not be locked. All that happens is that the screen goes dark at the time the screensaver should start.

  Yours,

    Chris