Bug 511687 - With multiple screens, have to unlock each screen separately
Summary: With multiple screens, have to unlock each screen separately
Status: RESOLVED DUPLICATE of bug 512028
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.5.1
Platform: Bazzite Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen, regression
Depends on:
Blocks:
 
Reported: 2025-11-05 20:04 UTC by owltropicalastronaut
Modified: 2025-12-10 16:06 UTC (History)
7 users (show)

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


Attachments
Screen locking settings (20.18 KB, image/png)
2025-11-17 06:40 UTC, owltropicalastronaut
Details

Note You need to log in before you can comment on or make changes to this bug.
Description owltropicalastronaut 2025-11-05 20:04:29 UTC
I searched frequently report bugs and searched, but only found a similar but closed bug https://bugs.kde.org/show_bug.cgi?id=485520.

SUMMARY
Updating from KDE Plasma 6.4.5 to 6.5.1 within the stable image branch of Bazzite has led to having to press enter twice after entering password to login. A rollback to the image with 6.4.5 resolves this issue.

STEPS TO REPRODUCE
1. Lock the screen or sleep machine, on an account with a password.
2. Wake screen/system. 
3. Type in password. Press enter and password field shows up on second monitor.
4. Press enter again, screen unlocks and enters desktop.

OBSERVED RESULT
After waking screen/system and typing password, pressing enter does not immediately unlock the system. Must press enter again.

EXPECTED RESULT
After waking screen/system and typing password, pressing enter immediately unlocks the system to the desktop environment.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Bazzite 43.20251102
KDE Plasma Version: 6.5.1
KDE Frameworks Version: Unknown
Qt Version: Unknown

ADDITIONAL INFORMATION
Problem happens with two existing users, unable to test if happening with a newly created user due to time constraints and the fact I already rolled back.
Comment 1 owltropicalastronaut 2025-11-14 05:21:01 UTC
I was unable to reproduce this after upgrading back to Bazzite 43.20251102
Comment 2 owltropicalastronaut 2025-11-17 06:40:44 UTC
Created attachment 186875 [details]
Screen locking settings
Comment 3 owltropicalastronaut 2025-11-17 06:44:16 UTC
After 24 hours this reappeared. I sometimes have to lock my system immediately before walking away, by using the Meta+L shortcut. I also have my system configured to lock after waking from sleep, which may be locking the system doubly. 

To Reproduce:
So this occurs when I lock my system manually, then the system goes to sleep. Upon waking, I have to press enter twice after typing password.

This behavior is not ideal, as it should not be possible. My screen locking settings are attached.
Comment 4 Oliver Beard 2025-11-17 13:07:46 UTC
Moved to plasmashell/Screen Locking.
Comment 5 kde.sitter129 2025-12-03 05:52:18 UTC
I have the same issue. On lock screen (not sddm), I have to hit enter twice. Have had the problem since earlier this year and it has persisted through Fedora 42 + KDE 6.x to Fedora 43 + KDE 6.5.

Here are my system details, happy to provide more info if needed:

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.9-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor
Memory: 64 GiB of RAM (62.0 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 4090
Manufacturer: ASUS
Comment 6 Nate Graham 2025-12-08 22:27:32 UTC
Is anyone affected while using only one screen?
Comment 7 kde.sitter129 2025-12-09 15:27:28 UTC
Yes, I am using only one screen.
Comment 8 Nate Graham 2025-12-09 23:01:45 UTC
*** Bug 512576 has been marked as a duplicate of this bug. ***
Comment 9 Nate Graham 2025-12-10 16:06:13 UTC
Probably a different issue, then. Can you open a new bug report for it?

This looks like the same issue as Bug 512028. I'm marking it as a duplicate of that one despite it being newer, as it has a slightly clearer description of the problem.

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