[kscreenlocker] [Bug 455874] Screen locker is broken and unlocking is not possible

https://bugs.kde.org/show_bug.cgi?id=455874 --- Comment #2 from Andrej Falout --- (In reply to Nate Graham from comment #1) > Can you please paste the output of `coredumpctl list kscreenlocker_greet`? coredumpctl list kscreenlocker_greet No coredumps found. -- You are receiving this m

[kscreenlocker] [Bug 455874] Screen locker is broken and unlocking is not possible

https://bugs.kde.org/show_bug.cgi?id=455874 --- Comment #6 from Andrej Falout --- (In reply to ratijas from comment #3) > > No coredumps found. > > Is coredump service enabled at all? It might be turned off by default. > > https://wiki.archlinux.org/title/Core_dump T

[kscreenlocker] [Bug 455874] Screen locker is broken and unlocking is not possible

https://bugs.kde.org/show_bug.cgi?id=455874 --- Comment #8 from Andrej Falout --- (In reply to Nate Graham from comment #7) > > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > > Cannot find user-level thread for LWP 317551: generic error

[kscreenlocker] [Bug 455874] Screen locker is broken and unlocking is not possible

https://bugs.kde.org/show_bug.cgi?id=455874 --- Comment #5 from Andrej Falout --- (In reply to Nate Graham from comment #4) > Looks like you'll need to get the backtrace manually. Here's how you can do > it. > > 1. run `gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreen

[kscreenlocker] [Bug 440055] Can't unlock the screen if the user has an empty password

https://bugs.kde.org/show_bug.cgi?id=440055 Andrej Falout changed: What|Removed |Added CC||and...@falout.org -- You are receiving

[kscreenlocker] [Bug 454706] 8dbec4a153be35bcab4a1877ee524a7cbcb72e84 inappropriately shows the user the "no password unlock" screen after they supply their fingerprint

https://bugs.kde.org/show_bug.cgi?id=454706 Andrej Falout changed: What|Removed |Added CC||and...@falout.org -- You are receiving

[kscreenlocker] [Bug 455712] Unlock button even with password user

https://bugs.kde.org/show_bug.cgi?id=455712 Andrej Falout changed: What|Removed |Added CC||and...@falout.org -- You are receiving

[kscreenlocker] [Bug 455712] Unlock button even with password user

https://bugs.kde.org/show_bug.cgi?id=455712 --- Comment #2 from Andrej Falout --- Same problem with face login (Howdy). This comes just after the "Screen locker is broken and unlocking is not possible" (455874) was apparently fixed. Lost count how many times that one regressed. It

[kscreenlocker] [Bug 455874] New: Screen locker is broken and unlocking is not possible

https://bugs.kde.org/show_bug.cgi?id=455874 Bug ID: 455874 Summary: Screen locker is broken and unlocking is not possible Product: kscreenlocker Version: 5.25.0 Platform: Neon Packages OS: Linux Status: REPORTED

[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors

https://bugs.kde.org/show_bug.cgi?id=456210 Andrej Falout changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors

https://bugs.kde.org/show_bug.cgi?id=456210 Andrej Falout changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

[kscreenlocker] [Bug 456210] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing

https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #77 from Andrej Falout --- (In reply to Stephane Travostino from comment #76) > There is a lot of talk about fingerprint sensors: this bug has nothing to do > with it. It's a red herring. > > It is perfectly reproducible on m

[kscreenlocker] [Bug 456210] Cannot unlock screen when using multiple monitors

https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #65 from Andrej Falout --- Reported: 2022-07-01 15:25 Importance: VHI critical Version fixed in: 5.26.4 I have 5.26 and I am fully up to date. When can I expect to see this fix on my PC? Thanks -- You are receiving this mail