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

[Alan Fischer e Silva]

Binary package hint: update-notifier-kde

Description: Ubuntu karmic (development branch)
Release: 9.10

update-notifier-kde:
  Installed: 9.10ubuntu2
  Candidate: 9.10ubuntu2
  Version table:
 *** 9.10ubuntu2 0
        500 http://ca.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 222dae1e3f7f9fb033fafa900cd74e97
CheckboxSystem: 78db936e3abcbc195af890c2658b7bc7
Date: Wed Oct 14 01:05:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/update-notifier-kde
InterpreterPath: /usr/bin/python2.6
Package: update-notifier-kde 9.10ubuntu2
PackageArchitecture: all
ProcCmdline: python /usr/bin/update-notifier-kde -session 10144c2e4c2000125545696900000052660010_1255496498_842457
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
PythonArgs: ['/usr/bin/update-notifier-kde', '-session', '10144c2e4c2000125545696900000052660010_1255496498_842457']
SourcePackage: update-notifier-kde
Title: update-notifier-kde crashed with RuntimeError in <module>()
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/update-notifier-kde", line 29, in <module>
     from PyKDE4.kdecore import *
 RuntimeError: the sip module implements API v6.0 but the PyKDE4.kdecore module requires API v5.0
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:2733): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #452757, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.