applet.py crashed with ImportError in <module>()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
system-config-printer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: system-
maverick updated
got multiple crashes immediatly after opening the session, this one is one of them
might be related to bug 603919
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: system-
ProcVersionSign
Uname: Linux 2.6.35-
NonfreeKernelMo
Architecture: i386
CupsErrorLog:
Date: Thu Jul 15 07:16:38 2010
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.6
Lpstat: device for Photosmart-
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
PackageArchitec
Papersize: a4
PpdFiles: Photosmart-
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: python /usr/share/
ProcEnviron:
LANG=fr_FR.utf8
SHELL=/bin/bash
PythonArgs: ['/usr/
SourcePackage: system-
Title: applet.py crashed with ImportError in <module>()
Traceback:
Traceback (most recent call last):
File "/usr/lib/
from ._gi import _API
ImportError: libgirepository
UserGroups: adm admin audio avahi-autoipd cdrom clamav couchdb dialout dip fax floppy fuse gdm haldaemon lpadmin netdev plugdev polkituser proxy pulse pulse-access root rtkit sambashare ssh tape users video www-data
dmi.bios.date: 10/22/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3001
dmi.board.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5W DH Deluxe
dmi.product.
dmi.sys.vendor: ASUSTEK COMPUTER 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 #129222, 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.