Bug 649682
Summary: | post-install process error when updating gtk2 on ia64 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Tomas Pelka <tpelka> |
Component: | gtk2 | Assignee: | Benjamin Otte <otte> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.5.z | CC: | atodorov, bgollahe, lmiksik, mclasen, otte, ovasik, pmachata, pvine, sforsber, tlavigne, vbenes |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | gtk2-2.10.4-30.el5 | Doc Type: | Bug Fix |
Doc Text: |
* Previously, a post-installation process error occurred when updating GTK2 on systems using Itanium processors due to an incorrect usage of hard coded paths that were not translated correctly on the Itanium architecture. This update corrects the errors in the hard coded paths, and it is now possible to update GTK2 on Itanium processors.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-01 00:44:59 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: |
Description
Tomas Pelka
2010-11-04 09:46:26 UTC
Hmm, I can't see what is going wrong here. The i386 package definitively contains /usr/bin/gdk-pixbuf-query-loaders-32 The problem here might be that update-gdk-pixbuf-loaders asks for gdk-pixbuf-query-loaders-32 using explicit path, /usr/bin/gdk-pixbuf-query-loaders-32. On ia64, i386 packages are installed to /emul/ia32-linux. I think it might need to ask for /emul/ia32-linux/usr/bin/gdk-pixbuf-query-loaders-32 I have no idea what the right way to fix this is. One option that comes to mind is asking for ./gdk-pixbuf-query-loaders-32, or perhaps extracting current dir from $0 and looking for the binary there. I'll look into it some more, but these are the first thoughts. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1366.html |