config_usb_printer.py crashed with ImportError in /usr/share/hplip/base/status.py: No module named hpmudext
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hplip (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
systemd-sysv booted
got that crash on a gnome-shell session after plugging the usb printer
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: hplip-data 3.15.2-0ubuntu2
ProcVersionSign
Uname: Linux 3.19.0-5-generic i686
NonfreeKernelMo
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
BootDmesg: (Nothing has been logged yet.)
CupsErrorLog:
Date: Sat Feb 21 07:59:54 2015
ExecutablePath: /usr/share/
InterpreterPath: /usr/bin/python2.7
Lpstat:
device for Photosmart-
device for Photosmart_C4500: hp:/usb/
Lsusb:
Bus 001 Device 003: ID 03f0:6b11 Hewlett-Packard Photosmart C4500 series
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
PackageArchitec
Papersize: a4
PpdFiles:
Photosmart_C4500: HP Photosmart c4500 Series, hpcups 3.15.2
Photosmart-
ProcCmdline: /usr/bin/python /usr/bin/
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=
PythonArgs: ['/usr/
SourcePackage: hplip
Title: config_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
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 this software better. This particular crash has already been reported and is a duplicate of bug #1419888, 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.