Bug 428706 - Cannot unlock session after external screen switches off in Wayland
Summary: Cannot unlock session after external screen switches off in Wayland
Status: RESOLVED DUPLICATE of bug 435941
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: HI major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2020-11-05 00:18 UTC by Ongun Kanat
Modified: 2021-05-11 12:58 UTC (History)
9 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The output of journalctl --boot 0 --priority warning (259.33 KB, text/plain)
2020-11-05 00:18 UTC, Ongun Kanat
Details
The output of journalctl --boot 0 --priority warning shorter (194.78 KB, text/plain)
2020-11-08 23:28 UTC, Ongun Kanat
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ongun Kanat 2020-11-05 00:18:35 UTC
Created attachment 133034 [details]
The output of journalctl --boot 0 --priority warning

SUMMARY
I decided to try Wayland session out since I have a new Hi-DPI monitor. However I cannot unlock if the session goes into power saving mode and switches the display off. I can see and move the mouse but the greeter screen does not show up. I can reproduce the bug reliably. I can unlock the session using loginctl unlock-session. There are a couple of crashes in journalctl.

STEPS TO REPRODUCE
1. Lock the screen or wait until plasma locks it down
2. Wait until screen switches off


OBSERVED RESULT
Cannot login. Entering the password "in the dark" does not unlock the session. I have to switch into a TTY to unlock it with loginctl.

EXPECTED RESULT
The screen locker should be displayed and I should be able to unlock.

SOFTWARE/OS VERSIONS 
Operating System: Arch Linux
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.3-arch1-1
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD RENOIR


ADDITIONAL INFORMATION
The output of journalctl --boot 0 --priority warning is attached.
Comment 1 Nate Graham 2020-11-05 14:27:16 UTC
eek.
Comment 2 Nate Graham 2020-11-05 21:28:09 UTC
Works for me with my laptop's internal 4k screen.
Comment 3 Ongun Kanat 2020-11-08 23:28:27 UTC
Created attachment 133159 [details]
The output of journalctl --boot 0 --priority warning shorter

I replaced the journalctl log with a shorter one. I have just logged in and locked my screen and waited until it goes into power saving.
Comment 4 Dan Johansen 2021-03-25 06:42:05 UTC
I have the same issue on my desktop.

OS: Manjaro Linux
Plasma version: 5.21.3
Display server: Wayland
Kernel: 5.11.6

1. Put system in suspend mode, which locks the screen.
2. Turn off screen
3. Wake system again.
4. Screenlocker crashed.

But if I turn on the screen, before I wake the system (between point 2 and 3), there is no issues. Which would explain why laptop lid open action works, since that powers on the screen before waking plasma.
Comment 5 Winford 2021-04-03 19:30:52 UTC
I am also suffering from the same problem. If the monitor is powered off kscreenlocker can no longer unlock the session. I am given a screen that directs me to switch to another tty and use loginctl unlock-session. The same thing will happen if a TV is used over HDMI. If the tv switches input to another HDMI or cable input, before or during a locked session, kscreenlocker cannot unlock the session after returning the input to the desktop's HDMI.

SOFTWARE/OS VERSIONS 
Operating System: Arch Linux
KDE Plasma Version: 5.21.3
Plasma Framework Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.10-arch1-1
systemd Version: 247.4
OS Type: 64-bit
Processor: AMD Ryzen 5 1400 Quad-Core
Graphics:  AMD Radeon R5 340
Comment 6 Michael Harden 2021-05-01 13:27:46 UTC
same issue, keyboard does not respond, I can get it to ask for the password, but nothing I do on the keyboard responds on the system.  I have multiple users, so I was able to use switch user and get it to log back into the sesson.  on x11 lock screen, unlike before I have to press a button on the keyboard and wait, after the screen wakes up and the lock screen comes up I can start typing in my password.  I plan to attempt same work around under wayland to see if this allows keyboard access to log in, if im able to get a work around for this, I will post the information here.
Comment 7 Michael Harden 2021-05-01 13:29:27 UTC
(In reply to Nate Graham from comment #2)
> Works for me with my laptop's internal 4k screen.

Same on my laptop, been using wayland on my laptop its not a 4k screen just a regular screen, but im able to get in with no issues, this issue seems to just be with desktop sessions as far as I can tell so far.
Comment 8 Alex 2021-05-11 12:40:09 UTC
Marking this as confirmed given the number of people who report running into this.
Comment 9 Vlad Zahorodnii 2021-05-11 12:49:37 UTC
This looks like a dup of https://bugs.kde.org/show_bug.cgi?id=435941 (It affects machines with amd gpus)
Comment 10 Nate Graham 2021-05-11 12:58:50 UTC

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