I have 2 systems, both are AMD GPU based and both are running Arch and are plugged into the same 2 monitors. However, one is using the HDMI ports and the other the DP ports. The issue is only happening on the DP ports system. When the monitors are coming out of sleep / wake up (CPU is not set to sleep or hibernate) the primary desktop will have lost the background, right click menu no longer works, etc... However, the background it had usually has has moved to the other monitor. Sometimes the other monitor just has one of the Arch package (or KDE) default backgrounds vs. one of the ones I've set. The taskbar and virtual deskops, konsole apps, etc...all stay were they are and you can still work in everything. There just isn't a "desktop" anymore on the primary monitor. Killing the plasmashell process and re-starting it brings back both backgrounds, right click menu, etc.... However, the background that had moved to the 2nd monitor goes back to the first and the original background on the 2nd monitor shows up again. This feels like someone is counting starting with 0 and someone else with 1 in an array or something when coming out of sleep or while it's asleep processes are doing something, but are off by 1. Operating System: Arch Linux KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-8700 CPU @ 3.20GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 550 / 550 Series similar to: https://bugs.kde.org/show_bug.cgi?id=362058 , but I've only started seeing this issue in the last 6 months or so. Same hardware and setup, although I'm on a clean install of Arch now vs. an Arch install that had been around for awhile.
I need to amend this. I hadn't finished my coffee. It's the system plugged into the HDMI ports that lose their background, etc.... The DP port system is actually fine.
I can attach gdb to the plasmashell process, but it's not "crashing" per se so don't know how helpful it will be.
*** This bug has been marked as a duplicate of bug 353975 ***