Bug 235011 - qt43: designer says "The template path /usr/lib/qt4/bin/templates could not be created."
qt43: designer says "The template path /usr/lib/qt4/bin/templates could not b...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: qt4 (Show other bugs)
6
All Linux
medium Severity medium
: ---
: ---
Assigned To: Rex Dieter
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-03 05:55 EDT by Laurent Rineau
Modified: 2007-11-30 17:12 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-04-03 07:01:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Laurent Rineau 2007-04-03 05:55:40 EDT
Description of problem:

At the very start of Qt4's designer, a popup dialog says: "The template 
path /usr/lib/qt4/bin/templates could not be created."


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

qqt4-devel-4.3.0-0.2.beta.fc6

How reproducible: always.

Steps to Reproduce:
1.Launch /usr/bin/designer-qt4
2.
3.
  
Actual results: the popup dialog.

Expected results: nothing.

Additional info: I know that the package qt4-devel-4.3.0-0.2.beta.fc6 is not 
in Fedora, but you are the author, Rex, and I am sure that you reuse your 
kde-redhat spec files for future Fedora packages. Actually, maybe the problem 
is already in the current Qt4 version present in Fedora.
Comment 1 Laurent Rineau 2007-04-03 07:01:26 EDT
Actually this bug may be specific to the beta release of Qt-4.3.
I eventually think that my bug is a spam and has nothing to do in Redhat's 
Bugzilla. Sorry. I close it.
Comment 2 Rex Dieter 2007-04-03 11:25:49 EDT
I don't mind...

I'll try to keep an eye out for this, and if the problem persists in later
qt-4.3 (beta/rc) releases, will re-open.

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