[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 kdebugsquas...@catradora.org changed: What|Removed |Added CC|kdebugsquas...@catradora.or | |g | -- You are receiving this mail because: You are watching all bug changes.
[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 #85 from Nate Graham --- This is a somewhat old bug report and the code has changed a lot since it was reported. There's a very good chance the issue you're experiencing is caused by something else, even if the outward symptoms look and feel the same. Can you please submit a new bug report? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[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 #84 from Bernd Steinhauser --- Despite being marked as resolved, this still occurs to me sometimes on Plasma 6.0. -- You are receiving this mail because: You are watching all bug changes.
[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 #83 from Nate Graham --- *** Bug 455712 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[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 Nate Graham changed: What|Removed |Added Version Fixed In|5.26.4 |5.27.5 -- You are receiving this mail because: You are watching all bug changes.
[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 Harald Sitter changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kscreenlocker/commit/a92 |ma/kscreenlocker/commit/161 |73c87e8582be7aa1e3de14d92b8 |f9d4c5151e4f3871e670531883b |0ec92c4f44 |cb6a198d1f --- Comment #82 from Harald Sitter --- Git commit 161f9d4c5151e4f3871e670531883bcb6a198d1f by Harald Sitter. Committed on 26/04/2023 at 11:31. Pushed by sitter into branch 'Plasma/5.27'. greeter: track various properties persistently There is a fundamental race condition between PamAuthenticator and the greeter views. PA is a singleton that emits signals that result in stateful changes to the views (e.g. showing the prompt message). Meanwhile views are added when they get connected. This leads to circumstances where pam may have sent a prompt before a view was created, meaning the view is in an incorrect state. To mitigate the problem we'll force-emit a number of stateful signals whenever they are connected to. Thus ensuring that greeter views definitely receive the most recent states. The more long-term solution should likely be to move to property bindings instead, so these stateful signals are now also exposed as stateful properties. (cherry picked from commit a9273c87e8582be7aa1e3de14d92b80ec92c4f44) M +77 -4greeter/pamauthenticator.cpp M +21 -0greeter/pamauthenticator.h https://invent.kde.org/plasma/kscreenlocker/commit/161f9d4c5151e4f3871e670531883bcb6a198d1f -- You are receiving this mail because: You are watching all bug changes.
[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 Harald Sitter changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/kscreenlocker/commit/a92 |t/20c51d95798e953acd3299354 |73c87e8582be7aa1e3de14d92b8 |a5b37a1216b6343 |0ec92c4f44 --- Comment #81 from Harald Sitter --- Git commit a9273c87e8582be7aa1e3de14d92b80ec92c4f44 by Harald Sitter. Committed on 26/04/2023 at 11:29. Pushed by sitter into branch 'master'. greeter: track various properties persistently There is a fundamental race condition between PamAuthenticator and the greeter views. PA is a singleton that emits signals that result in stateful changes to the views (e.g. showing the prompt message). Meanwhile views are added when they get connected. This leads to circumstances where pam may have sent a prompt before a view was created, meaning the view is in an incorrect state. To mitigate the problem we'll force-emit a number of stateful signals whenever they are connected to. Thus ensuring that greeter views definitely receive the most recent states. The more long-term solution should likely be to move to property bindings instead, so these stateful signals are now also exposed as stateful properties. M +77 -4greeter/pamauthenticator.cpp M +21 -0greeter/pamauthenticator.h https://invent.kde.org/plasma/kscreenlocker/commit/a9273c87e8582be7aa1e3de14d92b80ec92c4f44 -- You are receiving this mail because: You are watching all bug changes.
[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 #80 from Lewis L. Foster --- (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. I know that the issue isnt directly related to fingerprint readers, etc. Its just when using fingerprint, etc it always displays the unlock button that doesnt work. Not too sure on the behaviour if you are using a password, does it happen randomly? -- You are receiving this mail because: You are watching all bug changes.
[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 #79 from Stephane Travostino --- (In reply to Andrej Falout from comment #77) > Do you have dual/multi monitor setup by chance? I do. The problem indeed happens with multi monitor setups, fingerprint sensors have nothing to do with this. -- You are receiving this mail because: You are watching all bug changes.
[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 Miren Radia changed: What|Removed |Added CC|miren_ra...@yahoo.co.uk | -- You are receiving this mail because: You are watching all bug changes.
[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 #78 from sparkie --- (In reply to Andrej Falout from comment #77) > (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? Not Stephane, but I do. -- You are receiving this mail because: You are watching all bug changes.
[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] Under certain circumstances when using multiple monitors, "unlock" button is clickable but does nothing
https://bugs.kde.org/show_bug.cgi?id=456210 --- Comment #76 from Stephane Travostino --- 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. -- You are receiving this mail because: You are watching all bug changes.
[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 #75 from Lewis L. Foster --- (In reply to Stephane Travostino from comment #74) > Same story on Fedora Kinoite. AMD 6800 XT, with two 4K screens of similar, > but not same model. > > It is extremely aggravating to the point that it's the single thing that > stops me from using KDE, as I can't take a coffee break without being locked > out from my desktop and the thing I was working on. For me, its ALWAYS happening because i have fingerprint auth enabled. As a workaround, i switch over to TTY1 where GDM is running and i can unlock from there, luckily. Still super annoying -- You are receiving this mail because: You are watching all bug changes.
[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 Stephane Travostino changed: What|Removed |Added CC||s...@combo.cc --- Comment #74 from Stephane Travostino --- Same story on Fedora Kinoite. AMD 6800 XT, with two 4K screens of similar, but not same model. It is extremely aggravating to the point that it's the single thing that stops me from using KDE, as I can't take a coffee break without being locked out from my desktop and the thing I was working on. -- You are receiving this mail because: You are watching all bug changes.
[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 kdebugsquas...@catradora.org changed: What|Removed |Added CC||kdebugsquas...@catradora.or ||g -- You are receiving this mail because: You are watching all bug changes.
[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 sparkie changed: What|Removed |Added CC||lg_ninj...@yahoo.com --- Comment #73 from sparkie --- I'm having this issue as well. I can enter my password, then it goes to a screen with an "Unlock" button, but clicking the button does nothing. I'm on Wayland, plasma 5.27.3, Fedora 37, Qt 5.15.8, and I have three identical monitors connected to an AMD 6700XT GPU. Two via displayport-->hdmi adapters and one normal HDMI. -- You are receiving this mail because: You are watching all bug changes.
[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 stellarpo...@googlemail.com changed: What|Removed |Added CC||stellarpo...@googlemail.com --- Comment #72 from stellarpo...@googlemail.com --- I am also on Ubuntu 22.04 and Plasma 5.25.5 (wayland). I have not had any lock-screen issues so far (I'm not using it at all) but when I see Plasma crashes I have lines in the log in common with what is mentioned here. https://bugs.kde.org/show_bug.cgi?id=458469 I am seeing behaviour similar to in this bug and have added comments there; and someone else who was able to get 5.26 also saw that fix it. Am commenting in case there might be something in common between these issues, and something that has been resolved as of 5.26, but not in the 5.25 branch (which is the latest available for all Ubuntu LTS users, so a reasonably large number may encounter further problems) I see these lines in common (and searching for them has brought me here): - Creating a fake screen in order for Qt not to crash - requesting unexisting screen -1 - qt.qpa.wayland: Wayland does not support QWindow::requestActivate() - QMetaProperty::read: Unable to handle unregistered datatype 'KWin::SessionState' for property 'KWin::EffectsHandlerImpl::sessionState' - QML Connections: Detected function "onConfigurationChanged" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. This is unrelated to the screenlocking, and often occurs when I power my display back on after being away form the PC for some time (fully on, not suspended); but I also experience this at times when there is a change in my desktop - e.g. opening a new application. - Cannot read property 'wallpaper' of null -- You are receiving this mail because: You are watching all bug changes.
[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 Lewis L. Foster changed: What|Removed |Added CC||le...@sniff122.tech --- Comment #71 from Lewis L. Foster --- I am also experiencing this bug on the framework laptop and the fingerprint reader on 5.25.5 on ubuntu 22.04. I have the fingerprint setup with libfprint and i have it configured in `/etc/pam.d/common-auth`. With just the internal display, I can move my mouse or press a key on the keyboard and it will ask me to place my finger on the reader and it will show the unlock button which works. With multiple displays connected, the unlock button appears to do nothing and i have to run a loginctl unlock-session from another tty to be able to unlock. I have also tried entering my password before placing my finger on the reader with the same effect. I have a similar setup with my work machine (a HP probook 440 G8) so i'll test that and see how it works Ubuntu 22.04 Plasma 5.25.5 Wayland -- You are receiving this mail because: You are watching all bug changes.
[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 superation...@gmail.com changed: What|Removed |Added CC||superation...@gmail.com --- Comment #70 from superation...@gmail.com --- So with Rocky 8.6 kernel version 4.18.0-372.26.1 I tried several things and I was still having this issue. I check the journalctl and my issue was a file. The file /etc/authselect/system-auth only had read permissions. I changed it to 755 and the unlock function worked. I realize this isn't a full fix for the bug but it turned out to be a good workaround for my situation. -- You are receiving this mail because: You are watching all bug changes.
[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 Bernd Steinhauser changed: What|Removed |Added CC||li...@bernd-steinhauser.de -- You are receiving this mail because: You are watching all bug changes.
[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 Nate Graham changed: What|Removed |Added Summary|Cannot unlock screen when |Under certain circumstances |using multiple monitors |when using multiple ||monitors, "unlock" button ||is clickable but does ||nothing See Also||https://bugs.kde.org/show_b ||ug.cgi?id=409226 -- You are receiving this mail because: You are watching all bug changes.
