applet.py crashed with ImportError in /usr/lib/python2.7/dist-packages/cupshelpers/cupshelpers.py: No module named packagekit.client

[Wobbo]

dunno

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: system-config-printer-gnome 1.3.5+20110731-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic i686
Architecture: i386
Date: Sun Jul 31 20:54:29 2011
ExecutablePath: /usr/share/system-config-printer/applet.py
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110727)
InterpreterPath: /usr/bin/python2.7
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
MachineType: innotek GmbH VirtualBox
PackageArchitecture: all
Papersize: a4
ProcCmdline: /usr/bin/python /usr/share/system-config-printer/applet.py
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic root=UUID=2eb16cbe-631f-4beb-8e73-da97495bf35e ro quiet splash vt.handoff=7
PythonArgs: ['/usr/share/system-config-printer/applet.py']
SourcePackage: system-config-printer
Title: applet.py crashed with ImportError in /usr/lib/python2.7/dist-packages/cupshelpers/cupshelpers.py: No module named packagekit.client
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[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 #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.