Created attachment 170169 [details] Screenshot shows icons in the wrong place in the KDE Control Panel For starters: Apologies for posting without a category. Really. I looked and there seemed to be nowhere to report something that seems to affect the entire desktop's rendering like this. SUMMARY Went away from my computer for a bathroom break. When I came back I noticed it took a very long time to wake up. But that was the least of my worries, as Plasma seems to now be really bugged out: Two things: Window decorations (like the ones at the top with the buttons to close and such) do not render properly. That's the simple part The other, weirder one, is harder to explain in text so I made a [video](https://youtu.be/dj0IqMkiJ-4) -- The short version is that whenever I mouse over any icon in a panel, be it a tray icon or something on the taskbar thingie -- it seems to jump to the top-right corner of that panel. Though only visually (as in, to interact with it, I still have to click the blank space the icon once occupied) I have also noticed that icons within qt6 windows do not show in the proper place (see attachment) These persisted after reboots. GTK related programs seem to display properly. STEPS TO REPRODUCE 1. Start plasma 2. Mouse over any icon in a panel 3. Watch it happen OBSERVED RESULT Window decorations don't render properly, and icons snap to the top-right corner of panels when mouse hovers over them. EXPECTED RESULT They should, like, not do that? SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSUSE Tumbleweed 20240531 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel: 6.9.3-1-default (64-bit) Graphics platform: X11 ADDITIONAL INFORMATION Extra details about system (idk maybe it helps?): 1. I have an AMD Processor and GPU 2. All the things I have installed are either from the official SUSE Repos or from Flatpak. There's also some appimages and local executables in my user folder. There is 1(one) application I compiled from source and installed system-wide, and that was [Orbiton](https://github.com/xyproto/orbiton), a text editor for terminal. 3. When I update the system I get a notification about how updating glibc-32bit would break Steam. So I marked it as untouchable on YaST. Maybe this broke something else? Idk. Things I have already tried: 1. Updating the system 2. Rebooting 3. Changing theming configurations back to system defaults (hey, you never know) 4. Moving widgets around in panels 5. Disabling fancy effects 6. Disabling and re-enabling my second monitor/changing which monitor is the primary 7. Asking nicely Things I have not tried: 1. Switching to Wayland (I would do so permanently but it breaks Inkscape for me and that's part of my workflow -- Plus I'm new to SUSE, and the last time I switched from X to Wayland was on EndeavourOS, dunno if the process is any different) 2. Crying Not excluding the possibility of this not being a bug -- Maybe I screwed something up. But I wouldn't know what or how to fix it.
ADDENDUM After a suggestion on the [Lemmy Thread](https://lemmy.ml/comment/11465420) I made about this issue, I tried creating a new user profile, and indeed under the fresh user profile, Plasma behaves normally with no issues. So I think it might be something on my user configs that's screwed.
So! Update. Also on the Lemmy thread I previously cited, a user suggested I backed up my configuration files and then copied over the config files from the (functional) new test user account. I did so. And that didn't solve the problem (it just deleted my customisations to theming and shid, but that's fine) -- BUT -- As I was about to complain that it hadn't worked, I noticed an icon in the tray that definitely wasn't there before, warning that Plasma was using Software Rendering. It wasn't supposed to do that. So I changed it to OpenGL -- And after rebooting one more time, NOW it seems to broadly work. I'll give it some 48 hours of usage before I declare that it does. See if anything else breaks and such. Try to reapply my custom theme. Et cetera. It still feels odd that the renderer would have changed Like That of its own volition.
Unfortunately this is a Qt bug: https://bugreports.qt.io/browse/QTBUG-123799
*** This bug has been marked as a duplicate of bug 482669 ***