Bug 160810 - x86_64 version of qtrc refers to 32 bit directories
x86_64 version of qtrc refers to 32 bit directories
Product: Fedora
Classification: Fedora
Component: redhat-artwork (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Depends On:
  Show dependency treegraph
Reported: 2005-06-17 09:45 EDT by Sjoerd Mullender
Modified: 2013-03-05 22:43 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-06 17:07:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sjoerd Mullender 2005-06-17 09:45:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The file /usr/lib64/qt-3.3/etc/settings/qtrc (i.e. the 64 bit version) refers to /usr/lib/qt-3.3 and /usr/lib/kde3 (the 32 bit versions), but that should be /usr/lib64/qt-3.3 and /usr/lib64/kde3 (both path names occur twice).

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

How reproducible:

Steps to Reproduce:
1. not applicable

Additional info:
Comment 1 Christian Iseli 2007-01-19 19:19:13 EST
This report targets the FC3 or FC4 products, which have now been EOL'd.

Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?

Comment 2 Sjoerd Mullender 2007-01-24 11:30:41 EST
The file mentioned still exists in FC6 in the package redhat-artwork-5.0.8-1.fc6
and still refers to /usr/lib/qt-3.3 and /usr/lib/kde3 which don't exist, instead
of to /usr/lib64/qt-3.3 and /usr/lib64/kde3 which do exist.
Comment 3 Sjoerd Mullender 2007-09-06 17:07:52 EDT
The file does not seem to exist anymore in F7, so even though the problem still
persists in FC6 I'll close the report.  I can't remember anymore why this was a
problem anyway.

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