Bug 8246 - KDE Screensaver always locks, notwithstanding settings selected in KDE Control Center
Summary: KDE Screensaver always locks, notwithstanding settings selected in KDE Contro...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: UPSTREAM
: 8353 8506 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-11-29 22:03 CET by Juergen Harms
Modified: 2013-02-20 22:30 CET (History)
7 users (show)

See Also:
Source RPM: lib64kscreensaver5
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Juergen Harms 2012-11-29 22:03:52 CET 
Description of problem:

When a KDE desktop is left idle, it always locks after the timeout period set for the Screensaver (now called Screen Locker) - even if the "Screen locker type" radiobutton in KCC is set to "Screen saver". This is extremely annoying when doing work where you alternately display data and than need some time to handle the data off-screen.

An evident work-around would be to turn the screen-saver altogether off (or set it to a long timeout) - but that is not good for the screen.


Version-Release number of selected component (if applicable):
lib64kscreensaver5 (guessing)

How reproducible:
100%

KCC -> Hardware -> Display & Monitor -> Screenlocker
Check Screen saver Radio button
Start automatically after (5) minutes


Steps to Reproduce:
1. KCC -> Hardware -> Display & Monitor -> Screenlocker
2. Check "Screen saver" (Screen locker type) Radio button
3. Check the "Start automatically after" checkbutton and select a meaningful time value.

Note: it appears that KCC correctly sets the contents of .kde4/share/config/kscreensaverrc but that this setting is not correctly interpreted by KDE
Juergen Harms 2012-11-29 22:05:46 CET

Priority: Normal => High
Source RPM: screensaver always lock, => lib64kscreensaver5

Manuel Hiebel 2012-11-30 18:51:42 CET

CC: (none) => balcaen.john
Assignee: bugsquad => nicolas.lecureuil

Comment 1 Nicolas Lécureuil 2012-11-30 19:35:28 CET 
upstream bug see: https://bugs.kde.org/show_bug.cgi?id=310871

See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=310871

Manuel Hiebel 2012-11-30 20:23:56 CET

Keywords: (none) => UPSTREAM

Hans Micheelsen 2012-12-31 12:17:37 CET

CC: (none) => micheelsen

Comment 2 user7 2013-01-13 17:17:47 CET 
*** Bug 8506 has been marked as a duplicate of this bug. ***

CC: (none) => jarillon

Ben Bullard 2013-01-25 19:24:52 CET

CC: (none) => benbullard79

Comment 3 Manuel Hiebel 2013-01-29 21:49:29 CET 
*** Bug 8353 has been marked as a duplicate of this bug. ***

CC: (none) => eeeemail

Sander Lepik 2013-01-29 21:50:47 CET

Priority: High => release_blocker
CC: (none) => sander.lepik

Sander Lepik 2013-01-29 21:51:01 CET

Hardware: x86_64 => All

Manuel Hiebel 2013-01-29 21:51:34 CET

Hardware: All => x86_64

Manuel Hiebel 2013-01-29 21:55:29 CET

Hardware: x86_64 => All

Comment 4 Luc Menut 2013-02-19 22:16:55 CET 
This bug should be fixed with kdebase4-workspace-4.10.0-3.mga3 (upstream patches from KDE/4.10 branch).
https://git.reviewboard.kde.org/r/108425/
http://commits.kde.org/kde-workspace/72ca24bb6484b014ea4d91a323b8a7c8a44085aa

regards,
Luc

CC: (none) => lmenut

Comment 5 Hans Micheelsen 2013-02-20 09:04:45 CET 
I can confirm that it works as intended now.

Wonderful. This day starts very well indeed!
Comment 6 Luc Menut 2013-02-20 22:30:47 CET 
so closing as fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.