Bug 450613

Summary:	wayland: wakeup after screenlock does not refresh the screen properly
Product:	[Plasma] kwin	Reporter:	slartibart70
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	REPORTED ---
Severity:	normal	CC:	kde, kqnumwpvwbjohvazjx, lemmyg, nate, vrykolas
Priority:	NOR
Version First Reported In:	5.24.1
Target Milestone:	---
Platform:	Manjaro
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description slartibart70 2022-02-20 14:37:43 UTC

Hi,
using plasma 5.24.1 and wayland, after screenlocking (triggered by timeout and monitor-off) and logging in again by giving the password on the screen-lock screen, only parts of the desktop appear properly.

In my case, i had chromium open (using X), krusader, a terminal shell and systemsettings.
The effect was a blinking screenlocker-picture on the xwayland/chromium window showing the browser content and the screenlocker-picture alternatively, this gave a very annoying blinking effect.
workaround:
switch to another desktop, switch back and the blink effect is gone.

Still annoying, though

Comment 1 galder 2022-02-20 16:45:19 UTC

Hello,
I tried to reproduce this issue.
I worked fine for me. Restoring the whole Wayland desktop once I unlock it.
I have Firefox , systemsetttings and Chromium opened.

Operating System: Kubuntu 21.10
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.13.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

Comment 2 slartibart70 2022-02-20 18:06:23 UTC

well, it happened for me twice.... That's the reason for the bugticket (maybe for testing you should also get sth. to eat and let the computer idle/poweroff the monitor :-D)
Yes, maybe its dependent on other factors as well. 

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.1
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.10-200.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-7500 CPU @ 3.40GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630

Comment 3 galder 2022-02-20 18:18:10 UTC

Hello,
I followed your steps and worked as expected. I'm not sure what could it be.
Lets see if other users reports same issue.
Regards

Comment 4 vrykolas 2022-02-28 06:14:57 UTC

(In reply to galder from comment #3)
> Hello,
> I followed your steps and worked as expected. I'm not sure what could it be.
> Lets see if other users reports same issue.
> Regards

I confirm this issue with wayland 1.20.0-1, using KDE Plasma.
I noticed it within the last ~1 week (maybe after a recent update)?

To test, I switched to X11 compositor (instead of wayland), and the screen unlock did NOT have a problem.
So it seems (to me) the issue is with wayland, while X11 worked fine.

To reproduce:
1) lock screen (meta-L)
2) unlock screen

-wayland didn't show my desktop (only mouse cursor). A workaround is to press CTRL+ESC, and then it opens task manager and the desktop properly.

-X11 was able to unlock fine.

I'm not a developer, and I'd say I'm beginner to medium experience (not advanced, not a developer).
Using T490 on Linux Manjaro, kernel 5.15.21-1-MANJARO x86_64

Comment 5 kqnum 2022-07-27 01:16:30 UTC

I've been experiencing this issue as well on EndeavourOS with AMD 5500XT graphics. It's been happening over multiple kernel and plasma releases. Like the other comments, it only occurs in Wayland.

In my experience, Plasma still accepts global hotkeys in this state. For instance, using Alt + Tab briefly displays the windows. However, when letting go of those keys, the windows become "invisible" again. Open windows still accept keyboard input, even if the window is not being displayed properly.