Bug 8506

Summary:	KDE screen locker cannot be removed
Product:	Mageia	Reporter:	Pierre Jarillon <jarillon>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	bittwister2, wassi
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Pierre Jarillon 2012-12-26 13:25:15 CET

After a fresh install of Mageia 3 beta1, the screen locker of KDE is active and the user is prompted to give his password.
With the KDE control center, I can change the delay, select Screen saver with diaporama, but I cannot remove the necessity to give the user password to unlock the screen.

The file ~/.kde4/share/config/kscreensverrc contains: Lock=false 
but that's false! The locker is still active...

Comment 1 Bit Twister 2012-12-26 22:50:02 CET

(In reply to comment #0)
 
> The file ~/.kde4/share/config/kscreensverrc contains: Lock=false 
> but that's false! The locker is still active...

You indicated a fresh install but was /home left over from previous install?
Reason I ask, there is no kscreensverrc. There is
$ cat kscreensaverrc
[ScreenSaver]
Enabled=false
LegacySaverEnabled=false
Lock=false
LockGrace=60000
PlasmaEnabled=false
Timeout=300

I suggest you create another account, say junk, log into junk, use the kde control center and disable and test.

I disabled locker for two users on 4 different installs, and they all disabled without problem.

CC: (none) => junk_no_spam

Comment 2 Pierre Jarillon 2012-12-27 12:03:36 CET

To test Mageia, I use only one partition which is formated. Then I am sure that I have a completely fresh installation.
I have created the user junk and open/close/open a session with KDE.
You are true: kscreensaverrc is not created.
You are false: kscreensaverrc is created as soon as you modify anything in the screen locker... And the locker is active!

Comment 3 user7 2013-01-13 17:17:47 CET

IINM, this was already reported, see bug 8246

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

Status: NEW => RESOLVED
CC: (none) => wassi
Resolution: (none) => DUPLICATE