Created attachment 158806 [details] Screenshot showing panel that hadn't visually refreshed SUMMARY *** At some point while playing a full-screen game, at least several parts of the panel stopped refreshing. They are all still interactive - at least the ones that are appropriately still showing - for example, clicking on my open browser window minimizes it, clicking on the Notifications bell in the tray opens it, etc. However, new task manager buttons aren't appearing, closed windows aren't disappearing, and the visual contents of items aren't updating (e.g. the browser button shows the window title as of when it froze, the weather/memory/clock on the right are stuck. *** STEPS TO REPRODUCE 1. Run a full-screen game 2. Tab in and out of it 3. View panel OBSERVED RESULT Task manager buttons and panel icons/labels stop updating at a certain point EXPECTED RESULT Task manager buttons and panel icons/labels should continue updating, since the underlying apps that feed them are still running and functional SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: HP Product Name: HP Pavilion Gaming Laptop 15-ec2xxx ADDITIONAL INFORMATION This sounds like this bug reoccurring again, so this may be an Nvidia issue, however I'm on a hybrid laptop so theoretically the panel isn't rendering using Nvidia but rather the integrated AMD graphics? (But maybe because the full-screen game was using Nvidia, that threw it off somehow?) Sorry if this is not an appropriate way to file this, please let me know what I can do better! I'm attaching a screenshot (with the top part of my Firefox window cropped out just due to having a bunch of tabs open there), but it was about 2:55 PM my local time when I took that screenshot, and the game in the Task Manager (Hades) had already been closed.
*** This bug has been marked as a duplicate of bug 469016 ***