Bug 689070

Summary:	Firstboot doesn't use gtk-oxygen theme after kde spin install
Product:	[Fedora] Fedora	Reporter:	Trever Fischer <tdfischer>
Component:	firstboot	Assignee:	Martin Gracik <mgracik>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	bcl, dmach, kevin, mgracik, rdieter
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-22 15:25:17 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	669355

Description Trever Fischer 2011-03-19 02:48:50 UTC

Description of problem:
Inside the rawhide kde live cd, the anaconda installer has the oxygen theme like the rest of the desktop. After installation however, firstboot has the ugly boxy GTK theme straight out of the 90s.

Version-Release number of selected component (if applicable):
Rawhide


How reproducible:
Every time

Steps to Reproduce:
1. Install rawhide kde spin
2. Reboot
3. Run through firstboot
  
Actual results:
Ugly GTK theme


Expected results:
gtk-oxygen, or at least Nodoka.


Additional info:
None. But Anaconda with the GTK theme looks drop dead sexy.

Comment 1 Martin Gracik 2011-03-21 15:11:13 UTC

I believe this is related to bug#683855

Comment 2 Trever Fischer 2011-03-21 16:47:05 UTC

It is indeed related, but not the solution. The solution should be to use the oxygen GTK theme which is installed as part of the KDE spin.

Comment 3 Rex Dieter 2011-03-21 18:22:45 UTC

This seems, imo, ultimately a gtk issue, I mean there's no way I know of to set a global/default gtk theme, short of installing a /etc/gtk-2.0/gtkrc or /etc/gtk-3.0/settings.ini , and I'm pretty sure that the users' settings daemon isn't consulted when running apps with a different uid either.

We've hacked around this on the kde spin creating a /root/.gtkrc-2.0 (part of bug#683855).

any better suggestions?

Comment 4 Kevin Kofler 2011-03-22 10:03:04 UTC

I think what happens here is that the /root/.gtkrc-2.0 created on the live image does not end up installed, so things are screwed up again after installation.

Comment 5 Rex Dieter 2011-03-22 12:16:53 UTC

Kevin's right, modified files on the live images are for the live image only (sorry if that wasn't obvious).

Comment 6 Martin Gracik 2011-03-22 12:25:47 UTC

I believe, that we don't want to put that hack into anaconda.

Comment 7 Kevin Kofler 2011-03-22 13:29:23 UTC

What if we put those lines:
# hack around https://bugzilla.redhat.com/683855
cat > /root/.gtkrc-2.0 << GTKRC_EOF
include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc"
include "/etc/gtk-2.0/gtkrc"
gtk-theme-name="oxygen-gtk"
GTKRC_EOF
below the /etc/rc.d/init.d/livesys EOF, i.e. write directly to the live image's /root instead of the livesys initscript?

Comment 8 Kevin Kofler 2011-03-22 15:25:17 UTC

Should be fixed by:
http://git.fedorahosted.org/git/?p=spin-kickstarts.git;a=commitdiff;h=9a222daf121e1265a859850e2b064b61a929ca44