applet.py crashed with ImportError in /usr/lib/python2.7/dist-packages/cupshelpers/cupshelpers.py: No module named packagekit.client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Always happens a few seconds after logging in, was in Gnome-Shell but I think it happens in unity as well.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-
ProcVersionSign
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Sun Jul 31 19:54:58 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110715)
InterpreterPath: /usr/bin/python2.7
Lpstat: device for EPSON-Stylus-
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7360
PackageArchitec
Papersize: a4
PpdFiles: EPSON-Stylus-
ProcCmdline: /usr/bin/python /usr/share/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: system-
Title: applet.py crashed with ImportError in /usr/lib/
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/11/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.2
dmi.board.
dmi.board.name: MS-7360
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7360
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
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 #819203, 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.