Created attachment 146248 [details] illegible buttons in the gnome-abrt GTK application with Breeze GTK theme SUMMARY In Fedora 35 KDE Spin, the buttons in the title bars of some GTK apps and dialogs are illegible, appearing dark on dark. STEPS TO REPRODUCE 1. My Application Style > GNOME/GTK Application Style > GTK theme: is set to Breeze, as is Global Theme and Window Decorations > Theme. 2a. In Firefox under Wayland, choose File > Open 2b. Run a GTK app with buttons in its title bar, e.g. gtk-abrt OBSERVED RESULT See attached screenshot. For me, the buttons and controls in these title bars with what I think are "CSD (client-side decoration) buttons" are black on black, thus illegible. Normally the title bar of the active window in Breeze turns blue, but these remain black. Some buttons have a thin outline. If I mouse over the top right, I see a dim red (X) icon; if I right-click and hold in the right location in the title bar, the button will draw, dimly. EXPECTED RESULT Legible buttons and window controls in the title bar. Maybe it should be blue when active like other Windows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Wayland ADDITIONAL INFORMATION Some people comment that removing files in ~/.config/gtk-3.0 fixes rendering issues, e.g. bug 428120. I have never messed with my theming or touched this directory, but I have upgraded Fedora and KDE for years on this laptop, so maybe I have old cruft in it.
What system color scheme are you using? Note that the color scheme is separate from the Global Theme.
(In reply to Nate Graham from comment #1) > What system color scheme are you using? Note that the color scheme is > separate from the Global Theme. Breeze Light, plus Use accent color "From current color scheme". What's strange is my windows don't look like the preview for Breeze Light: the title bar of my active KDE window or "CSD-less" GTK window is white text on blue, not the black on gray in the Breeze Light preview. If I click Breeze Light > Edit Color Scheme... > Colors, that also shows Active Titlebar/Titlebar Text as black text on gray; meanwhile the color scheme shows Inactive Titlebar/Titlebar Text as medium gray text on slightly lighter gray; but in fact my inactive KDE windows are gray text on black. I tried switching to Colors > Breeze, and this bug goes away -- GTK titlebars with CSD buttons look the same as other Breeze windows, white on darkish gray. Then I switched back to Colors > Breeze Light, and all titlebars now match the Breeze Light preview (no more active blue and inactive black) and the bug has stayed fixed 🎉. So if anyone else has this bug, the workaround is probably "If some titlebars look wrong, try choosing a different Colors scheme, [Apply], switch back, [Apply]." I'm fairly confident I never tweaked any Application Style/Color stuff, and none of these system settings dialogs showed an active [Defaults] or [Reset] button. However I've updated this laptop from 2016's Fedora 24 through various betas, and I think at some point I was using Oxygen not Breeze. So most likely some upgrade didn't cleanly update some setting. I kinda liked the white text on blue active titlebars I had, but I trust the Plasma theme designers. Thanks for all you do! 👍
> the title bar of my active KDE window or "CSD-less" GTK window is white text on blue That generally means you're using a color scheme that doesn't exist, and was a bug that affected Fedora releases prior to 34. If you installed your system with Fedora 33 or earlier, that could explain it. This bug that was fixed to never be able to happen in Plasma 5.24. In the meantime, you can switch your color scheme to something else and then back to "Breeze Light" again. Does that improve things?
(In reply to Nate Graham from comment #3) > you can switch your color scheme to something else and then back to > "Breeze Light" again. Does that improve things? Yes, as I said switching color scheme fixed it and it's gone for good along with my odd titlebar colors. I resolved fixed, thanks!
In that case, this is a known issue that was fixed in Plasma 5.24! :)