https://bugs.kde.org/show_bug.cgi?id=520324
--- Comment #1 from Petr N. <[email protected]> --- Maybe running: gsettings set org.gnome.desktop.interface gtk-theme 'Breeze-Dark' or gsettings set org.gnome.desktop.interface gtk-theme 'Adwaita' or adding a minutely cronjob (to set breeze/breeze-dark theme): * * * * * S=$(kreadconfig6 --group General --key ColorScheme); [[ "$S" == *"Dark"* ]] && T=Breeze-Dark || T=Breeze; gsettings set org.gnome.desktop.interface gtk-theme "$T" # gtk apps text to background issues fix attempt may help refresh the GTK windows content, but not always. AI: - "wxGTK 3.2 has no portal client, and adding one would be an upstream wxWidgets change" - "kde-config-gtk-style enumeration bug on Plasma 6" AI https://lumo.proton.me: " The reason gsettings isn't running automatically is that KDE Plasma 6 does not natively emit a D-Bus signal to GNOME/GTK settings when the system theme switches between Light and Dark. Plasma manages its own "Global Theme" and "Color Scheme" internally. While it can change the Qt/KDE apps instantly, it doesn't automatically translate that change into the org.gnome.desktop.interface namespace that GTK apps listen to. The breeze-gtk engine is supposed to bridge this, but as you discovered, the missing index.theme file breaks that bridge. Solution lies in KDE's built-in automation tool: "D-Bus Methods" or "System Monitor" triggers. The breeze-gtk engine fails to listen to Plasma's ColorSchemeChanged D-Bus signal and update org.gnome.desktop.interface gtk-theme. " -- You are receiving this mail because: You are watching all bug changes.
