By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2030

Summary: python-qt3-3.18.1-1.el6.rpm is broken
Product: TDE Reporter: welnicki
Component: rhelAssignee: Timothy Pearson <kb9vqf>
Status: RESOLVED DUPLICATE    
Severity: normal CC: albator78, bugwatch, michele.calgaro
Priority: P5    
Version: 3.5.13.2 [Trinity]   
Hardware: i386   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:
Bug Depends on:    
Bug Blocks: 2575    

Description welnicki 2014-04-15 19:05:00 CDT
I'm on centos 6.5.

I found the following messages in ~/.xsession-errors:

Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/trinity-tde-guidance/guidance-power-manager.py", line 40, in <module>
    from qt import *
ImportError: No module named qt

It seems that python-qt3-3.18.1-1.el6 (from trinity-3.5.13 repo) is broken.
This RPM installs the qt module in /usr/lib/python2.6/site-packages/python-qt3/qt.so, where python can't find it (note the extra /python-qt3/).

I worked around the problem by running:
# echo python-qt3 > /usr/lib/python2.6/site-packages/qt.pth

But the problem is really elsewhere.

I seem to have hit the bug because I didn't have EPEL enabled while I installed trinity-tde-guidance-powermanager.0.8.0svn20080103-7.el6.opt.
The trinity-tde-guidance-powermanager has "python-qt3" as a dependency,
but this dependency is normally satisfied by PyQt-3.18.1-12.el6 from EPEL.
The EPEL version works fine, because it installs to /usr/lib/python2.6/site-packages/qt.so.

I think there's no point in providing the non-working python-qt3-3.18.1-1.el6.rpm.
It isn't normally installed anyway, and just causes unobvious breakage if EPEL is not enabled.
Comment 1 Michele Calgaro 2016-10-14 07:27:01 CDT
This is the same problem reported on bug 2693, which has now been resolved.

*** This bug has been marked as a duplicate of bug 2693 ***