SUMMARY GTK theme isn't set to Breeze after fresh install. STEPS TO REPRODUCE 1. Install latest User/Testing/Unstable Neon in a VM 2. Open System Settings after installation 3. Navigate to Colors & Themes > Application Style > Configure GNOME/GTK Application Style... OBSERVED RESULT The GTK Theme combo box contains an invalid empty theme that that appears to look like Adwaita and must be manually changed to Breeze in order to make apps such as Firefox fit into the rest of the desktop. EXPECTED RESULT The GTK Theme combo box already contains the default Breeze theme. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Same happens on the User (and although I haven't checked there, probably also Testing) Edition. Not sure if this is exactly Neon specific, I can't test on other systems right now, but if it can be reproduced elsewhere, maybe this bug should be moved.
Bug in kde-gtk-config. This is meant to be handled by the gtkconfig.upd kconf_update script in kde-gtk-config, but it currently does not run in fresh installs because it has Version=5 and is thus only handled by kded5.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/113
Git commit 5b8327530ee62a257f9f12d8b419b445beec345b by Fabian Vogt. Committed on 13/03/2024 at 15:42. Pushed by fvogt into branch 'master'. gtkconfig.upd: Set Version=6 Make sure it's actually run by kded6. M +1 -1 kconf_update/gtkconfig.upd https://invent.kde.org/plasma/kde-gtk-config/-/commit/5b8327530ee62a257f9f12d8b419b445beec345b
Git commit 0760b1fd5f16a19475a25084be6e935a9ce7cbb5 by Fabian Vogt. Committed on 13/03/2024 at 15:48. Pushed by fvogt into branch 'Plasma/6.0'. gtkconfig.upd: Set Version=6 Make sure it's actually run by kded6. (cherry picked from commit 5b8327530ee62a257f9f12d8b419b445beec345b) M +1 -1 kconf_update/gtkconfig.upd https://invent.kde.org/plasma/kde-gtk-config/-/commit/0760b1fd5f16a19475a25084be6e935a9ce7cbb5
*** Bug 483445 has been marked as a duplicate of this bug. ***