Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 229073 - gtk2-2.4.13-22.i386.rpm problem with /etc/gtk-2.0/
Summary: gtk2-2.4.13-22.i386.rpm problem with /etc/gtk-2.0/
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gtk2
Version: 4.4
Hardware: i386
OS: Linux
Target Milestone: ---
: ---
Assignee: Cosimo Cecchi
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2007-02-16 19:59 UTC by Johnny Hughes
Modified: 2013-04-30 22:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-20 16:05:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Johnny Hughes 2007-02-16 19:59:46 UTC
In gtk2-2.4.13-22.i386.rpm inside the /etc/gtk-2.0/ directory, the directory has
shifted from:




This causes problems with many apps.  Doing this will fix it temporarily:

cd /etc/grk-2.0/
ln -s i686-redhat-linux-gnu i386-redhat-linux-gnu

This can be fixed by rebuilding the gtk2 and defining the following on the
command line:

--define "_build i386-redhat-linux-gnu" --define "_host i386-redhat-linux-gnu"

This issue is also in the CentOS Bug tracker at:

The following packages also need to be built with "_build" and "_host" defined
as i386 and not i686 (at least in the current RHEL4 codebase):

pango, emacs, librsvg2

Comment 1 Jiri Pallich 2012-06-20 16:05:05 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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