[kscreenlocker] [Bug 481143] pam_u2f didn't work
https://bugs.kde.org/show_bug.cgi?id=481143 Christopher W. changed: What|Removed |Added Resolution|DOWNSTREAM |NOT A BUG --- Comment #3 from Christopher W. --- Found the issue. I had 2 keys in key file. That caused a problem with first key in file. Now kscreenlocker works. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481143] pam_u2f didn't work
https://bugs.kde.org/show_bug.cgi?id=481143 --- Comment #2 from Christopher W. --- I didn't ask them. I could try to ask in the arch forums. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 481143] New: pam_u2f didn't work
https://bugs.kde.org/show_bug.cgi?id=481143 Bug ID: 481143 Summary: pam_u2f didn't work Classification: Plasma Product: kscreenlocker Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: chris200...@googlemail.com Target Milestone: --- SUMMARY I configured successfully lightdm with PAM modul "pam_u2f" from yubico but with kscreenlocker didn't work. STEPS TO REPRODUCE 1. sudo pacman -S extra/pam-u2f 2. sudo mkdir /etc/fido_key 3. sudo sh -c 'pamu2fcfg -u user >> /etc/fido_key/u2f_keys' 4. sudo sh -c 'cat /etc/pam.d/login >> /etc/pam.d/kde' 5. sudo sh -c 'echo "auth sufficient pam_u2f.so authfile=/etc/fido_key/u2f_keys" >> /etc/pam.d/kde' 6. Lock the Screen and try to unlock OBSERVED RESULT because of "sufficient" and not "required" it unlocks the screen immediately without Touching the Button on the Fido2 Stick after entering the password EXPECTED RESULT Unlock the screen if Touched the Button on Fido2 Stick after entering the password SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel-Version: 6.7.3-arch1-1 (64-bit) Wayland ADDITIONAL INFORMATION - -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 --- Comment #16 from Christopher W. --- I just updated to QT 5.15.5 now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 --- Comment #15 from Christopher W. --- I have expierienced since then one time that issue. It seems not 100% fixed. But it is better than before. I don't know why. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 --- Comment #9 from Christopher W. --- after some Updates, it disappeared for me. I had no problem for 1-2 weeks now on Arch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451386] Black Screen with Movable Cursor after Screens Resume from Sleep
https://bugs.kde.org/show_bug.cgi?id=451386 Christopher W. changed: What|Removed |Added CC||chris200...@googlemail.com --- Comment #7 from Christopher W. --- I also have an LG Monitor connected via HDMI and if i set to Sleep Mode and Wake up with Wayland i get a Cursor and some Applications i used are open but nothing more open. I can switch tty and close the Apps as intended. -- You are receiving this mail because: You are watching all bug changes.
