Created attachment 573671 [details] screenshot Description of problem: After installing F17 beta RC2 KDE live, oxygen-gtk theme is not applied, instead, the default one is applied. Version-Release number of selected component (if applicable): Fedora 17 beta RC2 KDE Live firstboot-17.0-1.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. Install Fedora 17 beta RC2 from KDE Live 2. Boot into firstboot 3. Actual results: GUI theme (oxygen-gtk I guess) is not applied, the default, 'ugly', one appears (see screenshot) Expected results: GUI theme is applied Additional info: Does not happen when installing from DVD with only KDE selected.
Info: oxygen-gtk is installed
Let's go with simplest fix then, if we can't get something better, reverting to manually setting oxygen-gtk as gtk theme for root on kde spin: https://fedorahosted.org/spin-kickstarts/changeset/3bcca4d1c47d8ec22e3e2e4dbaab326eee9b7bc6/fedora-live-kde-base.ks and followup (adding reference to this bug): https://fedorahosted.org/spin-kickstarts/changeset/3bcca4d1c47d8ec22e3e2e4dbaab326eee9b7bc6/fedora-live-kde-base.ks hopefully we can get this in f17 GA.
nominating blocker per http://fedoraproject.org/wiki/Fedora_17_Final_Release_Criteria#Final_Release_Requirements item 19: The proposed final Fedora artwork must be included and enabled by default for the installer, graphical boot, firstboot, graphical login and desktop background. since the result of not including this fix is an ugly/unthemed firstboot on kde spin
OK, got confirmation from dgilmore that spin composes use git, so getting this pkg updated is not necessarily a blocker (but still would be nice).
The kickstart files really shouldn't be changed during freezes unless they are addressing a that bug gets at least a NTH rating, so it still should get raised as a potential blocker.
the intent of that criterion was the 'artwork' delivered by the design team, but I guess there's a strong case for considering this an infringement of it. I'm +1 NTH at least, anyway. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This influences only firstboot, right? If that's the case, I'm +1 NTH, -1 blocker. But if it influences also other GTK applications run inside KDE session, then I'd consider +1 blocker.
in practical terms, yes, this only affects (and helps) firstboot, since it is launched prior to any user session that has an xsettings daemon. Normal user sessions (including root) should already 'just work'.
this should be fixed in TC6, as the spin-kickstarts change landed. Setting ON_QA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This is fixed with TC6 KDE Live i686.
Confirmed.
Two people confirmed, closing bug.