Bug 211620

Summary: Screensaver start although the check box is not selected in the screensaver preferences dialog
Product: [Applications] systemsettings Reporter: Jose <kikoloche>
Component: kcm_screensaverAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dmurczak, drf, periliocastrol, picander78, spectral
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jose 2009-10-24 09:40:17 UTC
Version:            (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

Screensaver start although the check box is not selected in the screensaver preferences dialog
Comment 1 Marco Gusy 2009-11-20 17:05:20 UTC
i confirm. It also starts when mplayer is running, very annoying!
Comment 2 Emilio 2009-12-15 15:31:53 UTC
It may be related to https://bugs.kde.org/show_bug.cgi?id=186908
Comment 3 Marco Gusy 2009-12-15 19:45:56 UTC
looks like gwenview in fullscreen triggers this problem too
Comment 4 Jonas Nyrén 2010-03-22 03:07:52 UTC
I have the same problem. In system settings/desktop/screen saver everything is disabled. I never touch these settings. Once in a while (I cannot understand what triggers it though) the screen blanker is starting up after a minute of inactivity, and nothing is changed in the settings. The only way to make it stop is to go into screen saver settings, click the "start automatically after 1 minute" and untick it and apply/save. It has happened lately when I play a file in dragonplayer, but I am unsure if this is the cause.
Comment 5 Jonas Nyrén 2010-03-22 03:09:31 UTC
And of course i forgot to mention.. this is KDE 4.4.1 on arch linux on x86_64
Comment 6 Dennis Murczak 2010-03-30 22:36:26 UTC
Confirming the problem with the screensaver activating after using Gwenview in fullscreen mode (Sidux with KDE 4.3.4).
Comment 7 Oswald Buddenhagen 2010-03-31 08:26:36 UTC
and if not this one, then bug 179144

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