Bug 496150

Summary: On a multi-screen setup, typing the password before all monitors are awake causes the focus to shift to another screen
Product: [Plasma] plasmashell Reporter: kiwifruit
Component: Session ManagementAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: kiwifruit, natalie_clarius, nate
Priority: NOR    
Version: master   
Target Milestone: 1.0   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: video of the bug

Description kiwifruit 2024-11-11 21:44:53 UTC
SUMMARY
On a multiscreen setup, starting to type the password before all windows are awake causes the focus to shift to another screen's password input. This leads to half the password being present on one screen's password input, and the other half being on another screen.

STEPS TO REPRODUCE
1. Lock your screen (Meta + L)
2. Press ESC to force your monitors to go to sleep
3. Wait for your monitors to go into "power saving mode"
4. Once the monitors are all asleep, start typing the password without waiting for monitors to be awake.

OBSERVED RESULT
As each monitor returns from sleep, the focus shifts to that monitor's password input.

EXPECTED RESULT
The password input in focus should always be the one on the main monitor, unless the user clicks on another monitor's password input.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20241105
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.6-2-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 31.0 GiB of RAM
Graphics Processor: AMD Radeon RX 7900 XT

ADDITIONAL INFORMATION
I personally don't see the need of having a password prompt on *every* monitor, but that's not the main issue. What really bugs me is the focus shifting around.

I've added a video of the bug in action [WARNING: some flashing lights].
Comment 1 kiwifruit 2024-11-11 21:46:02 UTC
Created attachment 175740 [details]
video of the bug
Comment 2 Nate Graham 2024-11-13 18:18:16 UTC
Ultimately, will be fixed by fixing Bug 433563.

*** This bug has been marked as a duplicate of bug 433563 ***