[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-08-27 Thread utux
https://bugs.kde.org/show_bug.cgi?id=339452 --- Comment #9 from utux --- Update: Very likely a duplicate of bug #375536 I found the problem on/in my distro: wrong mode of /sbin/unix_chkpwd Status: worksforme -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-08-27 Thread utux
https://bugs.kde.org/show_bug.cgi?id=339452 utux changed: What|Removed |Added CC||b...@ultratux.org --- Comment #8 from utux --- I see th

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-08-01 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=339452 TraceyC changed: What|Removed |Added CC||grrlieg...@elenari.net -- You are receiving this mai

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-08-01 Thread Twisted Lucidity
https://bugs.kde.org/show_bug.cgi?id=339452 --- Comment #7 from Twisted Lucidity --- I tried the kcheckpass thing (/usr/lib/x86_64-gnu/libexec/kcheckpass) and all I got was the error "Only binary protocol supported". Does that provide any more information? What other logging can I provide? --

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-06-27 Thread Twisted Lucidity
https://bugs.kde.org/show_bug.cgi?id=339452 --- Comment #6 from Twisted Lucidity --- I saw the exact same thing in my auth.log, but didn't realise it would provide enough detail to the devs. -- You are receiving this mail because: You are watching all bug changes.

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-06-27 Thread Philipp
https://bugs.kde.org/show_bug.cgi?id=339452 Philipp changed: What|Removed |Added CC||pplogm...@gmail.com --- Comment #5 from Philipp ---

[ksmserver] [Bug 339452] Unable to unlock session from screen locker

2017-06-23 Thread Twisted Lucidity
https://bugs.kde.org/show_bug.cgi?id=339452 Twisted Lucidity changed: What|Removed |Added CC||lucidlytwis...@gmail.com --- Comment #4 from