[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 my desktop PC with no fingerprint and no > Howdy. Just bog-standard username and password. Do you have dual/multi monitor setup by chance? -- You are receiving this mail because: You are watching all bug changes.
[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 because: You are watching all bug changes.
[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|REOPENED --- Comment #63 from Andrej Falout --- (In reply to Nate Graham from comment #61) > > Using Howdy and dual monitors > Howdy is not formally supported so that's a different issue. Please file a > new bug report for it. Thanks! Issue has nothing to do with Howdy, I only mentioned it because few people mentioned PAM possibly being involved in tracing the origin of this bug that appears at the same time as did the second unlock button following the successful authentication. Issue still happens when I use password. -- You are receiving this mail because: You are watching all bug changes.
[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 |--- CC||and...@falout.org --- Comment #59 from Andrej Falout --- Unfortunately still here for me. Using Howdy and dual monitors, Plasma 5.26.4 updated fully as of today. Wayland, probably irrelevant. Defunct "Unlock" button on both screens, only way to use the machine is via terminal unlock session This absolutely critical but is still here after several months -- You are receiving this mail because: You are watching all bug changes.
[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 even comes with it's own instructions screen, that's how "popular" it is. And this one seems to be intentional: "This patch adds an explicit button that must be pressed if no other prompts were given during the authentication process." I am on the Neon "user" feed, and I must say, the stuff that ends up in it is not fit for daily use of an operating system. :( -- You are receiving this mail because: You are watching all bug changes.
[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 this mail because: You are watching all bug changes.
[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 this mail because: You are watching all bug changes.
[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 this mail because: You are watching all bug changes.
[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 > > Well that's weird. Apparently it's an issue in glibc??? > https://bugs.archlinux.org/task/69657 Looking at the post in various places, this error message seems to be displayed in quite varied contexts and I suspect it may occur in wide range of causes. Use of word "generic error" may be a hint. In any case - can someone please look at the problem at hand - eg "Screen locker is broken and unlocking is not possible"? @Nate - you are able to reproduce this bug, correct? Thanks, Andrej -- You are receiving this mail because: You are watching all bug changes.
[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 Thanks for the link. That page described how do disable coredups, but it seems it does not state how to enable it? This is what I have ATM in cat /etc/systemd/coredump.conf [Coredump] #Storage=external #Compress=yes #ProcessSizeMax=2G #ExternalSizeMax=2G #JournalSizeMax=767M #MaxUse= #KeepFree= Thanks for your help. -- You are receiving this mail because: You are watching all bug changes.
[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/kscreenlocker_greet > --testing` in a terminal window > 2. enter "run" at the prompt > 3. when it crashes, enter "bt" at the prompt > 4. copy-and-paste the output here gdb --args /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing GNU gdb (Ubuntu 9.2-0ubuntu1~20.04.1) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet... (No debugging symbols found in /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet) (gdb) run Starting program: /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Cannot find user-level thread for LWP 317551: generic error (gdb) bt Selected thread is running. (gdb) quit -- You are receiving this mail because: You are watching all bug changes.
[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 mail because: You are watching all bug changes.
[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 Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: and...@falout.org CC: bhus...@gmail.com Target Milestone: --- SUMMARY "Screen locker is broken and unlocking is not possible" KDE neon User 5.25 fully up to date as of right now. Reported to https://invent.kde.org/plasma/kscreenlocker/-/issues/4 Reproduced by Nate Graham STEPS TO REPRODUCE 1. Run /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing OBSERVED RESULT /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:222: ReferenceError: wallpaper is not defined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:0: ReferenceError: wallpaper is not defined Locked at 1655853372 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:43:9: Unable to assign [undefined] to bool qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Segmentation fault SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.25 -- You are receiving this mail because: You are watching all bug changes.
