SUMMARY Sometimes (trigger is unknown) gtk configs are not updated and stay in some weird, incorrect state. This has two effects: 1. When setting a new GTK theme, all seems to work fine. 2. After session relog, we get some bizarre, broken window buttons on apps with client side decoration, like Pamac. There are no steps to reproduce because I can't trigger it at will, but it happened to me twice since the last Plasma 5.20 update, which forced me to delete: ~/.config/gtk-3.0/ I also noticed, that there were at least 4 or five similar issue topics on Manjaro forums, so this is happening all the time on various systems. Because it is only visible when messing with GTK themes and aurorae themes and on client side decorations, it's easy to miss this issue. EXPECTED RESULT Window buttons drawn from currently set GTK theme. Operating System: Manjaro Linux KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.11-3-MANJARO OS Type: 64-bit Processors: 8 × Intel® Core™ i7-6700HQ CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 530 ADDITIONAL INFORMATION I'm sending packed corrupted configs, plus the default one on which it works fine. - > Wait, Ark is not working for me at the moment, no loaded library... Not sure what happened. I upload the packed configs when I fix the package issue. In meanwhile, see the threads on the Manjaro forum, where you have screenshots of the ill effects of that bug. https://forum.manjaro.org/t/incorrect-window-buttons-on-client-side-decorations-on-gtk-apps-like-pamac/41046 https://forum.manjaro.org/t/how-to-restore-default-style-of-windows-buttons-in-gnome-shell/34414 This seems to be a known bug that is causing a lot of confusion and frustration for the users.
Created attachment 133844 [details] gtk-3.0 configs I'm adding earlier mentioned configs. The current, working one is simply gtk-3.0. The others, corrupted ones are as a .bak folders.
This should be fixed in 5.20.5. Please rereport, if it won't be fixed in PLasma 5.20.5. *** This bug has been marked as a duplicate of bug 428842 ***