jockey-kde crashed with ImportError in <module>()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: jockey-kde
~$ jockey-kde
Traceback (most recent call last):
File "/usr/bin/
import jockey.
ImportError: No module named ManagerWindowKDE4
$ lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04
$ apt-cache policy jockey-kde
jockey-kde:
Installed: 0.5.8-0ubuntu2
Candidate: 0.5.8-0ubuntu2
Version table:
*** 0.5.8-0ubuntu2 0
500 http://
100 /var/lib/
This happens upon launch of jockey-kde, nearly immediately. I expect it to bring up the list of available drivers, but it just crashes instead.
ProblemType: Crash
Architecture: amd64
Date: Tue Mar 23 22:05:53 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/jockey-kde
InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
InterpreterPath: /usr/bin/python2.6
MachineType: Dell Inc. Inspiron 1501
NonfreeKernelMo
Package: jockey-kde 0.5.8-0ubuntu2
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde --check 60
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
PythonArgs: ['/usr/
SourcePackage: jockey
Title: jockey-kde crashed with ImportError in <module>()
Traceback:
Traceback (most recent call last):
File "/usr/bin/
import jockey.
ImportError: No module named ManagerWindowKDE4
Uname: Linux 2.6.32-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/07/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.3
dmi.board.name: 0UW744??????
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1501
dmi.product.
dmi.sys.vendor: Dell Inc.
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 #451105, 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.