Bug 424011 - Visual desktop corruption after display is turned back on
Summary: Visual desktop corruption after display is turned back on
Status: RESOLVED DOWNSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.18.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-08 21:29 UTC by kde
Modified: 2020-07-22 17:57 UTC (History)
1 user (show)

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


Attachments
journalctl output (207.91 KB, text/plain)
2020-07-08 21:29 UTC, kde
Details
system info (4.05 KB, text/plain)
2020-07-08 21:30 UTC, kde
Details
example of visual corruption in kickoff (148.63 KB, image/jpeg)
2020-07-08 21:30 UTC, kde
Details
example of visual corruption in kate (149.18 KB, image/jpeg)
2020-07-08 21:31 UTC, kde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2020-07-08 21:29:08 UTC
Created attachment 129986 [details]
journalctl output

SUMMARY

I have an interesting (read maddening and not obviously fixable) problem with a single machine that I want to run KDE on.  The computer is hooked up to an audio video receiver (AVR) which is hooked up to a TV.  Once the AVR and TV are shutoff for several minutes, turning them back on results in a visually corrupted desktop with horizontal line artifacts everywhere (icons, panels, applications, kickoff, etc.).

The only thing that fixes the desktop is logging out and back in (or obviously restarting).  kwin_x11 --replace or kquitapp5 plasmashell && kstart5plasmashell don't get rid of the corruption.

It's an Intel based machine with discrete AMD graphics.  While I'm submitting this issue based on a clean install of OpenSUSE Leap 15.2/Plasma 5.18.5, the same behavior exists on this machine using Tumbleweed, Kubuntu, and Neon.

I fully suspect that the root cause is some weird power/link management issue in the AVR or TV, but I'm hoping there is some workaround I haven't tried, or that if it is a bug it can be fixed.  GNOME works fine on this machine (either vanilla or with dash-to-dock), but I *strongly* prefer Plasma and I need any computers hooked up to TVs to have consistent DEs so my family can use them easily without me.

STEPS TO REPRODUCE
1. This computer running and logged into a KDE Plasma session
2. Turn off TV (Sharp Aquos LC80LE642) and AVR (Onkyo TX-NR809) for ~10+ minutes
3. Turn TV and AVR back on

OBSERVED RESULT

Plasma desktop is visually corrupted.

EXPECTED RESULT

Plasma desktop is not visually corrupted.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSUSE Leap 15.2
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.71.0
Qt Version: 5.12.7

ADDITIONAL INFORMATION

Also occurs in the latest 5.19.x releases on Tumbleweed or Neon.  Attaching inxi system info, journalctl output, and some pictures of the visual corruption.  The system was booted at 14:15 in the journalctl output, the TV/AVR were shut off, and then I turned the TV/AVR back on and logged back in 30 minutes later 14:45.
Comment 1 kde 2020-07-08 21:30:11 UTC
Created attachment 129987 [details]
system info
Comment 2 kde 2020-07-08 21:30:48 UTC
Created attachment 129988 [details]
example of visual corruption in kickoff
Comment 3 kde 2020-07-08 21:31:33 UTC
Created attachment 129989 [details]
example of visual corruption in kate
Comment 4 David Edmundson 2020-07-08 21:54:36 UTC
So even after restarting kwin and plasmashell you still see corruption in plasmashell?

And it affects newly launched apps too?
Comment 5 kde 2020-07-08 22:38:08 UTC
Correct on both accounts.  I've tried...

kwin_x11 --replace
plasmashell --replace
kquitapp5 plasmashell && kstart5plasmashell (which is probably same as above)

And none of these fix the visual corruption.  Any newly launched apps continue to suffer the same visual corruption.  A full logout and log back in is the only thing that clears it short of a reboot.

I'm happy to run debug versions of components or enable extra logging etc. if we get to that point.
Comment 6 Christoph Feck 2020-07-22 17:57:18 UTC
Bug is either in the graphics/OpenGL drivers, or even lower in the stack (ModeSettings/DRM/DRI drivers). I suggest to look for help in a Mesa graphics forum or bug tracker.