update-notifier-kde crashed with ImportError in <module>()

[CB]

Binary package hint: update-notifier-kde

Ubuntu karmic (development branch) Release: 9.10

update-notifier-kde: Installed: 9.10ubuntu1

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 63d9fe0b7b738a2ae165f7b69e96d158
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
Date: Sat Oct 3 17:22:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-notifier-kde
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-kde 9.10ubuntu1
PackageArchitecture: all
ProcCmdline: python /usr/bin/update-notifier-kde
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
PythonArgs: ['/usr/bin/update-notifier-kde']
SourcePackage: update-notifier-kde
Title: update-notifier-kde crashed with ImportError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/update-notifier-kde", line 34, in <module>
     import dbus.mainloop.qt
 ImportError: No module named qt
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev scanner video
XsessionErrors:
 (gnome-settings-daemon:1678): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1678): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1781): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:1775): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:1774): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.1/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Jonathan Thomas (echidnaman)]

Does this crash go away if you install the python-qt4-dbus package?

[Mikael Bergqvist (mikaelb)]

Just upgraded to Kubuntu 9.10 and this bug happened.

[Harald Sitter (apachelogger)]

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!