Bug 442736 - wayland system hangs on lock session
Summary: wayland system hangs on lock session
Status: RESOLVED WORKSFORME
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords: wayland
Depends on:
Blocks:
 
Reported: 2021-09-20 13:15 UTC by Alexander Fieroch
Modified: 2023-11-26 03:45 UTC (History)
7 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 Alexander Fieroch 2021-09-20 13:15:36 UTC
Each time I lock my KDE session 
- manually using the lock widget
- using the command line "loginctl lock-session"
- using xscreensaver which locks the screen after some minutes

the system hangs. Parts of my screen turn black but I can see the rest of the screen. There is no login dialog or lock screen background. I also cannot unlock my session by typing blind my credentials.
However, it does not kill the desktop session. I can switch to a terminal CTRL+ALT+F1, login, and enter "loginctrl unlock-sessions". After switching back to KDE Wayland session I can use it again.

I have an AMD graphic card using 3 screens by 3 display port output.

$ inxi -G
Graphics:  Device-1: AMD Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] driver: amdgpu v: kernel 
           Display: wayland server: X.Org 1.21.1.1 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 1: 1200x1920~60Hz 2: 1920x1200~60Hz 3: 1920x1200~60Hz 
           OpenGL: renderer: Radeon RX550/550 Series (POLARIS12 DRM 3.40.0 5.11.0-34-generic LLVM 12.0.0) 
           v: 4.6 Mesa 21.0.3 

----

Kubuntu 21.04
ii  plasma-workspace 4:5.22.4-0ubuntu1~ubuntu21.04~ppa1 amd64        Plasma Workspace for KF5
ii  libkscreenlocker5:amd64                                     5.22.4-0ubuntu1~ubuntu21.04~ppa1
Comment 1 Nate Graham 2021-09-21 21:59:39 UTC
Do you see a message saying that the lock screen is broken? If so, this is probably the same issue as Bug 439096.
Comment 2 Alexander Fieroch 2021-09-22 05:02:17 UTC
There is no message, it just hangs immediately after locking. Sorry.
Comment 3 Nate Graham 2021-09-22 11:24:54 UTC
OK, thanks.
Comment 4 Alexander Fieroch 2022-03-02 09:08:50 UTC
After switching to an Nvidia graphic card, the locking works as expected. There must be a problem in combination with the AMD driver...
Comment 5 Alexandre Cavalheiro 2022-03-22 17:10:14 UTC
(In reply to Alexander Fieroch from comment #4)
> After switching to an Nvidia graphic card, the locking works as expected.
> There must be a problem in combination with the AMD driver...

It must be, because I personally have this issue and I am running an AMD GPU, I also have problems on the lock screen through the default key-bind when I am using wayland, the screen just jitters and takes a while to receive any input.
Comment 6 Nate Graham 2022-11-04 21:24:27 UTC
Do you have multiple screens connected when this happens?
Comment 7 Alexander Fieroch 2022-11-07 11:20:38 UTC
Yes, I had 3 monitors connected by displayport with resolution 1920x1200 each. Now I have a different multi-montior setup with new different problems I needed to open a new ticket:
https://bugs.kde.org/show_bug.cgi?id=461544
Comment 8 Nate Graham 2022-11-07 19:03:54 UTC

*** This bug has been marked as a duplicate of bug 374890 ***
Comment 9 Nate Graham 2023-10-27 20:52:09 UTC
Sorry, I think I mis-triaged this as a duplicate of bug 374890, which was not correct.
Comment 10 Nate Graham 2023-10-27 20:52:20 UTC
Regardless, if it's only broken when using an AMD GPU, that's a useful data point. Perhaps it was a driver issue that's since been fixed? Can you let me know if you still experience the issue in Plasma 5.27 and the latest Mesa drivers?
Comment 11 Bug Janitor Service 2023-11-11 03:45:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2023-11-26 03:45:41 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!