[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2021-06-21 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=375536 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|---

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2019-03-16 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #17 from Reuben --- I spoke too soon. I left the laptop for a couple hours and it suspended; the keyboard was unresponsive (to KDE) when I returned. Alt sysrq reisub worked, but I couldn't restart X or switch to different TTYs. -- You are

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2019-03-16 Thread Reuben
https://bugs.kde.org/show_bug.cgi?id=375536 Reuben changed: What|Removed |Added CC||k...@flavor8.com --- Comment #16 from Reuben ---

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2018-09-01 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #15 from Mihai Sorin Dobrescu --- This fixed it for me: chmod +s /sbin/unix_chkpwd -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2018-08-29 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375536 alex...@gmx.net changed: What|Removed |Added CC||alex...@gmx.net -- You are receiving this

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2018-08-17 Thread Mihai Sorin Dobrescu
https://bugs.kde.org/show_bug.cgi?id=375536 Mihai Sorin Dobrescu changed: What|Removed |Added CC||msdobre...@gmail.com --- Comment #14

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-08-27 Thread utux
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #13 from utux --- Ah! Good news from/for me at least. On my system, somehow /sbin/unix_chkpwd ended up as root:root 0711. I checked on two other systems, they both had root:root 4711. After I changed the rights the

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-08-27 Thread utux
https://bugs.kde.org/show_bug.cgi?id=375536 utux changed: What|Removed |Added CC||b...@ultratux.org --- Comment #12

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-04-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #11 from nono31...@gmail.com --- No I haven't. Or at least not willingly. I don't remember ever touching anything called PAM. I have however had a few issues a few months ago with SDDM and successively installed and uninstalled other

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-04-02 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #10 from Martin Gräßlin --- (In reply to nono31393 from comment #9) > When I run kcheckpass (in /usr/lib in Arch) from Konsole while logged in I > have an "Authentication failure" error message and a return code of 1.

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #9 from nono31...@gmail.com --- When I run kcheckpass (in /usr/lib in Arch) from Konsole while logged in I have an "Authentication failure" error message and a return code of 1. -- You are receiving this mail because: You are watching all

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-24 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #8 from Martin Gräßlin --- Please try to invoke the application "kcheckpass" directly on the command line. It takes your password and should return 0 if it authenticated you. Please note that kcheckpass is in a weird

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #7 from nono31...@gmail.com --- I am currently running KDE 5.9.4. When I try to log in after locking my PC from KDE, I can effectively now see the characters I'm typping thanks to the eye icon. The characters I am typing are effectively

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-24 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #6 from Martin Gräßlin --- > I'll wait for Plasma 5.9 then and come back with the results then. any news? -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-23 Thread Kestutis
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #5 from Kestutis --- It was my own fault, after messing with /etc/shadow and /etc/gshadow, I had them in a wrong group. chgrp shadow /etc/shadow and /etc/gshadow fixed it. -- You are receiving this mail because:

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-09 Thread Kestutis
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #4 from Kestutis --- ok, so I manage to find some logs related to this: /var/log/auth.log 9 14:13:12 DebianStretchPC unix_chkpwd[6242]: check pass; user unknown Mar 9 14:13:12 DebianStretchPC unix_chkpwd[6243]: check

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-03-09 Thread Kestutis
https://bugs.kde.org/show_bug.cgi?id=375536 Kestutis changed: What|Removed |Added CC||kestuti...@gmail.com ---

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-01-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #2 from nono31...@gmail.com --- Thanks, I'll be reporting bugs more quickly in the future. I just checked and unfortunately I do not have a selection icon on the lock screen for changing the keyboard layout. I'll wait for Plasma 5.9 then

[kscreenlocker] [Bug 375536] Password error after suspend / sleep / lock

2017-01-25 Thread Martin Gräßlin
https://bugs.kde.org/show_bug.cgi?id=375536 --- Comment #1 from Martin Gräßlin --- > I was expecting to see it fixed with an update but as this is still going on > I though I'd better do a bug report. This issue has not been reported yet. In future better directly report