Bug 808062 - firstboot: GUI theme settings not applied after installation from KDE Live
Summary: firstboot: GUI theme settings not applied after installation from KDE Live
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: spin-kickstarts
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jeroen van Meeuwen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: F17Blocker, F17FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-03-29 13:15 UTC by Martin Krizek
Modified: 2012-05-16 19:35 UTC (History)
16 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2012-05-16 19:35:23 UTC


Attachments (Terms of Use)
screenshot (123.33 KB, image/png)
2012-03-29 13:15 UTC, Martin Krizek
no flags Details

Description Martin Krizek 2012-03-29 13:15:22 UTC
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.

Comment 1 Martin Krizek 2012-03-29 13:22:10 UTC
Info: oxygen-gtk is installed

Comment 2 Rex Dieter 2012-05-14 20:39:24 UTC
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.

Comment 3 Rex Dieter 2012-05-14 20:43:43 UTC
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

Comment 4 Rex Dieter 2012-05-14 20:48:39 UTC
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).

Comment 5 Bruno Wolff III 2012-05-14 21:14:46 UTC
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.

Comment 6 Adam Williamson 2012-05-14 21:45:11 UTC
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

Comment 7 Kamil Páral 2012-05-15 12:25:02 UTC
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.

Comment 8 Rex Dieter 2012-05-15 12:37:48 UTC
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'.

Comment 9 Adam Williamson 2012-05-16 05:53:27 UTC
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

Comment 10 Kamil Páral 2012-05-16 09:17:31 UTC
This is fixed with TC6 KDE Live i686.

Comment 11 Jaroslav Reznik 2012-05-16 13:20:56 UTC
Confirmed.

Comment 12 Kamil Páral 2012-05-16 19:35:23 UTC
Two people confirmed, closing bug.


Note You need to log in before you can comment on or make changes to this bug.