Bug 442699

Summary:	With Intel GPU, laptop display remains black with only a cursor after resuming from sleep
Product:	[Plasma] kwin	Reporter:	Arjen Hiemstra <ahiemstra>
Component:	wayland-generic	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	cirlo_ca, jpeterse77, kalzwayed, nate, postix
Priority:	NOR
Version:	5.22.90
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
See Also:	https://bugs.kde.org/show_bug.cgi?id=455297 https://bugs.kde.org/show_bug.cgi?id=416501
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Arjen Hiemstra 2021-09-19 14:16:23 UTC

SUMMARY
When resuming my laptop from sleep, the display will remain black and only a cursor is shown. 

If I connect a secondary display, the secondary display renders fine. However, I need to restart KWin for the laptop display to be restored.

STEPS TO REPRODUCE
1. Put laptop to sleep.
2. Wake it up.

OBSERVED RESULT
Laptop display remains black, only a cursor is shown. 

EXPECTED RESULT
Laptop display shows lock screen and everything else correctly.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86
Qt Version: 5.15

ADDITONAL INFORMATION
The only thing I can see in the log output of KWin that might be relevant is:
kwin_core: Provided presentation timestamp is invalid: 19096252 (current: 68962192)

Comment 1 Nate Graham 2021-09-21 21:40:33 UTC

Bug 391531 maybe?

Comment 2 Arjen Hiemstra 2021-09-22 11:03:40 UTC

That one is on X11 and in Plasma, this one is on Wayland and I'm reasonably sure it's KWin, since also no windows show up.

Comment 3 Jan Petersen 2021-10-27 15:46:24 UTC

I think I've run into the same issue.
On a Dell XPS13 laptop. No external monitors.

After sleep, the screen does not appear to wake up. The power light is still on, and if I leave the laptop running unplugged, it will run down the battery to 0% and die.

I'm on the latest anniversary release of Neon, from a few days ago.

Comment 4 postix 2023-11-20 20:11:48 UTC

*** Bug 456723 has been marked as a duplicate of this bug. ***

Comment 5 Nate Graham 2023-11-29 17:05:31 UTC

Arjen, can you still reproduce this on Plasma 6? If so, is an NVIDIA GPU involved anywhere?

Comment 6 Arjen Hiemstra 2023-11-30 13:00:51 UTC

I haven't seen this for a pretty long time at this point, so we can consider this fixed.

And no, I don't have any NVidia GPUs.