Bug 187916 - Impossible to disable screensaver
Summary: Impossible to disable screensaver
Status: RESOLVED DUPLICATE of bug 179144
Alias: None
Product: kscreensaver
Classification: Unmaintained
Component: screensavers (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-23 10:44 UTC by Thomas Capricelli
Modified: 2009-06-01 14:48 UTC (History)
2 users (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 Thomas Capricelli 2009-03-23 10:44:09 UTC 
Version:            (using KDE 4.2.1)
OS:                Linux
Installed from:    Gentoo Packages

In system setting / desktop/ screen saver, i've UNCHECKED "start automatically", and the screensaver still starts after few minutes. I've tried to enable it / save / quit system settings / restart system settings / disable it /save.. but it still starts after few minutes. I have also tried to change the screensaver.

Moreover, it does some nasty sound when starting (well, why not), and it keeps on doing this very same sound for hours. Because of this i  need to shut down my speakers before going to sleep.. not fun!
Comment 1 Thomas Capricelli 2009-04-06 20:45:43 UTC 
the bug is still present using kde 4.2.2
Comment 2 Thomas Capricelli 2009-04-06 21:14:37 UTC 
a quick fix is :

sudo rm /usr/kde/4.2/lib64/kde4/libexec/krunner_lock
(on gentoo, change kde path for other distributions)
Comment 3 Médéric Boquien 2009-04-06 21:28:07 UTC 
This is indeed an important problem i can (unfortunately) reproduce. I cannot even watch a movie under KDE as the screen locks after ~10 minutes.
Comment 4 Thomas Capricelli 2009-05-07 18:26:00 UTC 
the bug is still present using kde 4.2.3

(i wonder if anywone cares.. )

Let's do it again:
sudo rm /usr/kde/4.2/lib64/kde4/libexec/krunner_lock
Comment 5 Lubos Lunak 2009-06-01 14:48:01 UTC 

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