ImportError: No module named qt

Bug #335811 reported by Andreas Blochberger
230
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kdebindings (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kdebluetooth

After a sudo apt-get dist-upgrade to Jaunty Alpha 5 this error popped up. Maybe this is a similar problem as in Bug #135893

ProblemType: Crash
Architecture: amd64
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/bin/kblueplugd
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: kdebluetooth 1:0.3-0ubuntu2
ProcCmdline: /usr/bin/python /usr/bin/kblueplugd
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/kblueplugd']
SourcePackage: kdebluetooth
Title: kblueplugd crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/kblueplugd", line 15, in <module>
     import dbus.mainloop.qt
 ImportError: No module named qt
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse-rt sambashare

Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :
Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

This has something to do with Python 2.6, i've reported two other bugs with the same cause:

Traceback:
 Traceback (most recent call last):
   File "/usr/bin/kblueplugd", line 15, in <module>
     import dbus.mainloop.qt
 ImportError: No module named qt

Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

This error makes KDE 4.2 unusable. Plasma hangs as soon as i start any application. I don't know if this is related to this, though

Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #135893. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

This should be fixed with the latest updates. KDE made some rather... invasive changes to the python bindings this time around.

Changed in python-kde4:
status: New → Fix Released
Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

As this bug returned, it seems not to be fixed. Bug #340088 proves that this problem still is here

Changed in kdebindings:
status: Fix Released → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Are you sure you're up to date? It works for me.

Changed in kdebindings:
status: New → Incomplete
Revision history for this message
Ilja Pavkovic (ipavkovic) wrote :

Works for me too, no bug anymore

Changed in kdebindings:
status: Incomplete → Fix Released
Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

I am sure i'm up to date. I do software updates twice a day, and this last crash just happened yesterday. Currently KDE doesn't work at all, so i'm trying it out after every update. Usually i only see that it does not work (i can't start any application in KDE and i see a lot of zombies in my process list), but yesterday apport reported this crash, when i returned in gnome.

Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

What information do you need, to track this issue?

Revision history for this message
Michael "notriddle" Howell (mhowell123-deactivatedaccount) wrote :

Same output from update-notifier-kde

michael@clu:~$ update-notifier-kde
Traceback (most recent call last):
  File "/usr/bin/update-notifier-kde", line 34, in <module>
    import dbus.mainloop.qt
ImportError: No module named qt

Revision history for this message
Andreas Blochberger (andreas-blochberger) wrote :

This probably is the same cause as in Bug #341568, so i'm going to mark it as duplicate of this. The re-installation of python-qt4-dbus made the error message go away, but it looks like the symptoms are still there.

Revision history for this message
SRElysian (srelysian) wrote :

strangely enough, i didnt notice my bluetooth icon was missing until I reinstalled dbus. I was originally trying to fix the update notifier problem, and on reboot... my bluetooth icon showed up. Hah, I still haven't seen the update notifier icon come up with anything new though.. usually (on 8.10) if i did a manual update it'd show up, but nothing now.

Revision history for this message
mrvanes (mrvanes) wrote :

update-notifier-kde was bumped to 0.15 yesterday and it now shows available updates correctly.
The last wrinkle now is that clicking on the notifier icon doesn't launch the update manager.

Revision history for this message
Giordano Battilana (jordan83) wrote :

I've upgraded to Kubuntu 9.04 beta about a week ago and notifications about software upgrades were not working. The Kdebluetooth icon also disappeared.
I investigated and found out that the command "update-notifier-kde" was failing with

$ update-notifier-kde
Traceback (most recent call last):
  File "/usr/bin/update-notifier-kde", line 34, in <module>
    import dbus.mainloop.qt
ImportError: No module named qt

I then found this bug page and (apparently) solved the issue by reinstalling the package python-qt4-dbus as suggested by Andreas.

Perhaps you should force the re-installation of such package because other users may be experiencing the same problem.

Cheers

Giordano

Revision history for this message
Matej Kenda (matejken) wrote :

This issue happened in Kubuntu Karmic Alpha 6.

Revision history for this message
Paulino Ascenção (paulino.a) wrote :

This is hapenning again in Kubuntu 9.04. When I try to upgrade to 9.10 with update-notifier.

paulino@kubuntup:~$ update-notifier-kde -d
Traceback (most recent call last):
  File "/usr/bin/update-notifier-kde", line 34, in <module>
    import dbus.mainloop.qt
ImportError: No module named qt

And solved after reinstalling package python-qt4-dbus

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.