applet.py crashed with ImportError in <module>()

[Jānis Kangarooo]

Binary package hint: system-config-printer

this crash came after login after crash that made Bug 601353

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: system-config-printer-gnome 1.2.0+20100408-0ubuntu5.2
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Sat Jul 3 15:11:19 2010
ExecutablePath: /usr/share/system-config-printer/applet.py
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Fujitsu Siemens VIA694X/686A
PackageArchitecture: all
Papersize: letter
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-23-generic root=UUID=b807243e-ef5c-4d91-9308-bc0febe12dc3 ro quiet splash
ProcCmdline: python /usr/share/system-config-printer/applet.py
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
PythonArgs: ['/usr/share/system-config-printer/applet.py']
SourcePackage: system-config-printer
Title: applet.py crashed with ImportError in <module>()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 08/03/2000
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 62710
dmi.board.name: 6VX7-4X
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.0
dmi.chassis.asset.tag: 00000000
dmi.chassis.type: 3
dmi.chassis.version: Version 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr62710:bd08/03/2000:svnFujitsuSiemens:pnVIA694X/686A:pvr00000000:rvnGIGABYTE:rn6VX7-4X:rvr1.0:cvn:ct3:cvrVersion1.00:
dmi.product.name: VIA694X/686A
dmi.product.version: 00000000
dmi.sys.vendor: Fujitsu Siemens

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