Bug 186400

Summary: KScreenSaver locks my screen randomly
Product: [Unmaintained] solid Reporter: Unknown <null>
Component: powermanagement-daemonAssignee: Dario Freddi <drf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: narny20, ossi
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Unknown 2009-03-06 23:02:36 UTC
Version:           ismeretlen (using 4.2.1 (KDE 4.2.1) "release 103", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.19-3.2-default

I use my desktop normally, but randomly the screensaver starts and locks my screen.
I even turned off its automatic starting in the control panel.
Comment 1 Andi Clemens 2009-04-11 22:13:43 UTC
Same here, especially when I return from suspend or if I manually locked the screen, the screensaver goes wild. When not moving the mouse or pressing some key, the screensaver starts after approx. 10 seconds, although 10 minutes is set.
I need to turn off the screensaver in the settings and enable it again to fix this.
Comment 2 Unknown 2009-04-25 18:14:34 UTC
Ok, it is not funny that something locks my screen in every 30th seconds...
And when my laptop is not plugged in, sends it to sleep.

While I was writing this 2 lines, my screen was locked 4 times! How can I remove the whole screensaver artifact? Of course, it is turned off completely for months.
Comment 3 Unknown 2009-04-25 19:12:35 UTC
Ok, I figured out a lot of things.

* First, this bug is in PowerDevil. When you go to the PD control panel > Edit Profiles > Performance > When the system is idle for more than xx min > "Lock Screen" and change to "Suspend to RAM" the whole screen locking transforms to sleeps. So somehow PD does not respect the idle time.
* After logging in KDE this bug occures more frequently than an hour after
* Sometimes automatic screen locking does only a half job: it locks my keyboard but my mouse and my screen is usable. See Bug 184645.
Comment 4 Oswald Buddenhagen 2009-04-26 09:11:07 UTC
why oh why am i not surprised the least?
Comment 5 Dario Andres 2009-06-20 21:34:51 UTC
*** Bug 194702 has been marked as a duplicate of this bug. ***
Comment 6 Oswald Buddenhagen 2009-10-11 19:55:47 UTC
i think that's pretty much the same issue ...

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