pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: hplip-data 3.15.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CrashCounter: 1
CupsErrorLog:
Date: Wed Mar 18 09:13:49 2015
ExecutablePath: /usr/share/
InstallationDate: Installed on 2013-12-22 (451 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221)
InterpreterPath: /usr/bin/python3.4
Lpstat:
device for Canon: dnssd:/
device for HP-Büro-2.0: socket:
device for HP_LaserJet_
device for Kyocera-Büro2.0: socket:
MachineType: LENOVO 429149G
PackageArchitec
Papersize: a4
PpdFiles:
Canon: Canon MX920 series - CUPS+Gutenprint v5.2.10
Kyocera-Büro2.0: Kyocera FS-C5100DN (KPDL)
HP_LaserJet_
HP-Büro-2.0: HP LaserJet M1522n MFP Foomatic/pxlmono (recommended)
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: hplip
SystemImageInfo:
current build number: 0
device name:
channel: daily
last update: Unknown
Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bluetooth
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 429149G
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1422004, 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.