Bug 402873 - Can't login after suspend
Summary: Can't login after suspend
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: Power management & brightness (other bugs)
Version First Reported In: 5.18.5
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: multiscreen
Depends on:
Blocks:
 
Reported: 2019-01-04 23:27 UTC by ksthiele
Modified: 2025-06-17 20:16 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ksthiele 2019-01-04 23:27:32 UTC
SUMMARY
I have two monitors and when the system suspends after not using it for a longer time. When waking it up, only (and always even after switching hdmi cables) the right monitor gets the kscreenlock. 

STEPS TO REPRODUCE
1. Wait for system to go into power save mode
2. Move mouse to wake up system
3. Kscreenlocker appears and I can't enter a password


OBSERVED RESULT
I can't login, only when I unplug the monitor and kscreenlocker switches to the first monitor. 
The keyboard IS recognized I can enter press Caps Lock and it warns me about it.


EXPECTED RESULT
That I can enter a password and enter desktop again


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE neon 5.14
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 64bit

ADDITIONAL INFORMATION

I have an AMD graphics card with latest stable Mesa (now at 18.2.2 on Xorg) from a PPA

I also have two monitors: On the left one old "DELL UHD2410" (set as Primary Display) and on the right a newer "LG Ultrawide", as mentioned it always starts on the right monitor (the LG one). I kinda suspect that the Dell needs a bit longer to "start" and KDE ignores it and gives the LG the kscreenlocker.

I also observed that I can enter characters while kscreenlocker appears after waking the system up (very short timeframe) but then it locks up

most of the time I have Chromium up, maybe it also messes with kscreenlocker?
Comment 1 Nate Graham 2025-06-17 20:16:27 UTC
Thanks for the bug report, and I'm sorry we weren't able to get to it yet. A lot has changed since it was reported; can I ask you to re-test with Plasma 6.3.5 or later in a Wayland session? Thanks a lot!