Bug 512028 - With two monitors, entering a password to one of them fails to unlock on first attempt, and instead focuses password field on other monitor
Summary: With two monitors, entering a password to one of them fails to unlock on firs...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.5.2
Platform: Arch Linux Linux
: HI normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen, regression
: 511687 512576 (view as bug list)
Depends on:
Blocks:
 
Reported: 2025-11-13 10:55 UTC by Sydney
Modified: 2025-12-19 17:12 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sydney 2025-11-13 10:55:47 UTC
SUMMARY
I have two monitors. If my screen locked while my mouse cursor was on a specific monitor, the first time I press enter to submit my password, it instead 'wakes' the password entry field on my other monitor.

STEPS TO REPRODUCE
1. Lock screen manually while my mouse cursor is located on the problematic monitor.
2. Type password.
3. Press enter to submit password.

OBSERVED RESULT
Lock screen wakes the password entry field on my secondary monitor instead of submitting the password I have already typed into the password entry field visible on my primary monitor.

EXPECTED RESULT
Lock screen accepts the initial attempt to submit my password.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.17.7-arch1-1 (64-bit)
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 9.19.0
Qt Version: 6.10.0

ADDITIONAL INFORMATION
pacman reports my version of the systemsettings package as 6.5.2-1, which does not seem to be an option available in the "version first reported in" field. Not sure what to do about that, so my apologies. The version I had last, where I did not experience this issue, was 6.4.5-1.

I've attempted changing which monitor is my "primary" display, but this doesn't change the behaviour of the bug; the problem always occurs for a specific monitor rather than primacy.
In case it matters, the monitor that I experience issue with is connected via displayport and the one that works as normal is connected via hdmi.

When the monitor I'm typing on is going to be problematic, the password entry field doesn't display the usual blue border that indicates it has focus.
Moving my mouse after locking the screen, even entirely within the bounds of the problematic monitor, seems to sidestep the bug and return the blue focus border.
Comment 1 Sydney 2025-11-13 11:02:00 UTC
Ah, that would be why I couldn't find an appropriate version in the dropdown, I was in the wrong 'product' category. Fixed that.
Comment 2 TraceyC 2025-11-14 00:30:23 UTC
I'm not able to reproduce this on Plasma built from git-master, or 6.5.2.

On git-master, the password field always appears on the same display as the cursor
On 6.5.2 - external (right, primary) monitor the password field appears here if the cursor is here
               - laptop (left) display - if the cursor is here, the password field appears on the external monitor, but when I type my password the field then appears on both monitors and the login is successful.

This looks similar to bug 455380, but that one involves activating a screen different from the one the cursor was on

Are you using a fallback theme? If so, this might be related to bug 481026
Comment 3 Sydney 2025-11-14 00:50:24 UTC
Not sure what a 'fallback theme' is, so I assume I'm not using one.
I have the lock screen configured in system settings to use the slideshow wallpaper type that changes every 5 minute, if that's relevant.

I've also just realised that the file upload size limit was not large enough for this video I took and it silently ignored the upload instead of nagging me about that, so I uploaded it to youtube: https://www.youtube.com/watch?v=PoQulbVb31Y
Comment 4 Bug Janitor Service 2025-11-29 03:46:09 UTC Comment hidden (spam)
Comment 5 Sydney 2025-11-29 15:18:04 UTC Comment hidden (spam)
Comment 6 Nate Graham 2025-12-10 16:06:13 UTC
*** Bug 511687 has been marked as a duplicate of this bug. ***
Comment 7 Nate Graham 2025-12-10 16:06:21 UTC
*** Bug 512576 has been marked as a duplicate of this bug. ***
Comment 8 Nate Graham 2025-12-10 19:08:16 UTC
*** Bug 513115 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2025-12-10 23:22:05 UTC
Clearly *something* is happening judging by the duplicate reports, but being unable to reproduce the issue will unfortunately make it impossible to fix.

Can anyone reproduce this on current git master?

Or, if using a stable release, try to find a specific steps to reproduce or pattern behind it?
Comment 10 owltropicalastronaut 2025-12-11 01:45:11 UTC
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Bazzite Linux 6.17.7-ba20.fc43.x86_64
KDE Plasma Version: 6.5.3 KWin (Wayland)
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
This is the behavior I am experiencing which seems most consistent, even if it is inconsistent. If the screen is locked (Meta+L), then put to sleep or automatically slept. Then upon waking the under the profile image it will say "Unlocking failed" even though there was no attempt to put password in. The password goes in as normal after the failed message disappears.

Instead of locking, putting the computer straight to sleep. Then no "Unlocking failed" message appears, and when typing the password in and hitting enter, the password box appears on second monitor. Hitting enter again enters the system.

I have put what could be relevant log entries below.

$ cat /etc/os-release 
NAME="Bazzite"
VERSION="43.20251210.0 (Kinoite)"
RELEASE_TYPE=stable
ID=bazzite
ID_LIKE="fedora"
VERSION_ID=43
VERSION_CODENAME="Kinoite"
PRETTY_NAME="Bazzite"
ANSI_COLOR="0;38;2;138;43;226"
LOGO=bazzite-logo-icon
CPE_NAME="cpe:/o:universal-blue:bazzite:43"
DEFAULT_HOSTNAME="bazzite"
HOME_URL="https://bazzite.gg"
DOCUMENTATION_URL="https://docs.bazzite.gg"
SUPPORT_URL="https://discord.bazzite.gg"
BUG_REPORT_URL="https://github.com/ublue-os/bazzite/issues/"
SUPPORT_END=2026-12-02
VARIANT="Kinoite"
VARIANT_ID=bazzite
OSTREE_VERSION='43.20251210.0'
BUILD_ID="Stable (F43.20251210)"
BOOTLOADER_NAME="Bazzite Stable (F43.20251210)"
IMAGE_ID="bazzite-43.20251210"

journalctl -f
Output at time of unlocking:
```
Dec 10 17:27:17 bazzite kwin_wayland_wrapper[5763]: warning: queue "mesa egl surface queue" 0x56251a953500 destroyed while proxies still attached:
Dec 10 17:27:17 bazzite kwin_wayland_wrapper[5763]:   wp_presentation#39 still attached
Dec 10 17:27:17 bazzite kscreenlocker_greet[5763]: Could not create EGL surface (EGL error 0x3000)
Dec 10 17:27:17 bazzite kwin_wayland_wrapper[5763]: warning: queue "mesa egl surface queue" 0x56251a51f8c0 destroyed while proxies still attached:
Dec 10 17:27:17 bazzite kwin_wayland_wrapper[5763]:   wp_presentation#39 still attached
Dec 10 17:27:17 bazzite kscreenlocker_greet[5763]: Could not create EGL surface (EGL error 0x3000)
Dec 10 17:27:17 bazzite kscreenlocker_greet[5763]: Failed to write to the pipe: Bad file descriptor.
```
Comment 11 Nate Graham 2025-12-12 20:40:27 UTC
There's a chance this will be fixed with the fix for Bug 513151. Can anyone test after their distro backports the fix? Arch and Fedora are usually pretty timely about this.
Comment 12 HORIE Seiichi 2025-12-13 14:13:41 UTC
I have tested with KDE Linux 2025-12-12. The problem still exists. 
- If I place the cursor on the primary monitor, I have to type ENTER twice. 
- If I place the cursor on the secondary monitor, I have to type ENTER only once ( this is expected ). 

KDE Plasma version 6.5.80
KDE Framework version 6.22.0

By the way, Bug #513151 refers to the KWin 6.5.4-3.1. This is very far from my KWin 6.5.80. Is something wrong? 

 ~ qdbus6 org.kde.KWin /KWin supportInformation | grep version
KWin version: 6.5.80
Qt compile version: 6.10.1
XCB compile version: 1.17.0
OpenGL version string: 4.6 (Core Profile) Mesa 25.3.1-arch1.2
OpenGL shading language version string: 4.60
OpenGL version: 4.6
GLSL version: 4.60
Mesa version: 25.3.1
X server version: 1.24.1
Linux kernel version: 6.17.9
Comment 13 Nate Graham 2025-12-19 17:12:56 UTC
This is strange. I cannot reproduce the issue on my multi-monitor setup running KDE Linux.