jockey-kde crashed with ImportError in <module>()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jockey (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
błąd pojawił się podczas uruchamiania systemu bezpośrednio po zainstalowaniu aktualizacji
ProblemType: Crash
.var.log.
Architecture: i386
Date: Wed Oct 14 19:42:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/jockey-kde
InterpreterPath: /usr/bin/python2.6
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 03f0:3304 Hewlett-Packard DeskJet 990c
Bus 002 Device 003: ID 04d9:1603 Holtek Semiconductor, Inc.
Bus 002 Device 002: ID 046d:c518 Logitech, Inc. MX610 Laser Cordless Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: jockey-kde 0.5.5-0ubuntu1
PackageArchitec
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/python /usr/bin/jockey-kde
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pl_PL.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/
from PyKDE4.kdecore import *
ImportError: No module named kdecore
Uname: Linux 2.6.31-14-generic i686
UserGroups:
dmi.bios.date: 09/11/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N73-CM ACPI BIOS Revision 0114
dmi.board.name: P5N73-CM
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
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.