Bug 549764

Summary: Invalid default theme in /etc/gtk-2.0/gtkrc breaks gtk applications under KDE 4.3.x
Product: [Fedora] Fedora Reporter: Gilboa Davara <gilboad>
Component: fedora-gnome-themeAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mclasen, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 14:43:31 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:
Attachments:
Description Flags
Broken progress bar. none

Description Gilboa Davara 2009-12-22 15:55:45 UTC
Created attachment 379852 [details]
Broken progress bar.

Description of problem:
Fresh F12 install (using a F11 home).
Updated to latest KDE 4.3.4 from kde-redhat.
All gtk applications (X-c-m, pulse controls, etc) no longer honor the KDE colors and certain widgets display artifacts (E.g. progress bars.)

Changing the theme from Clearlooks to Nodoka in /etc/gtk-2.0/gtkrc solves the problem.

Version-Release number of selected component (if applicable):
fedora-gnome-theme-12.3-2.fc12.noarch

How reproducible:
Always

Comment 1 Matthias Clasen 2010-01-25 06:18:01 UTC
Clearlooks in not 'invalid' in any way. It is the default theme in F12.

Comment 2 Gilboa Davara 2010-01-25 07:38:02 UTC
Bad wording on my part.
Never the less, replacing it Nodoka solves the corruption problem under KDE.

- Gilboa

Comment 3 Gilboa Davara 2010-06-05 07:25:23 UTC
Seeing the same under F13.
Had to change /etc/gtk-2.0/gtkrc from Clearlooks to Nodoka on 3 different brand new F13/KDE machines.

Any chance of solving this?

- Gilboa

Comment 4 Bug Zapper 2011-06-02 17:03:31 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Gilboa Davara 2011-06-04 18:25:24 UTC
Seems to work just fine under F15.
Please close.

Comment 6 Bug Zapper 2011-06-27 14:43:31 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.