config_usb_printer.py crashed with ImportError in /usr/share/hplip/base/status.py: No module named hpmudext

[Gerald Teschl]

???

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: hplip-data 3.15.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Mon Mar 2 09:59:58 2015
ExecutablePath: /usr/share/hplip/config_usb_printer.py
InstallationDate: Installed on 2012-03-27 (1069 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1)
InterpreterPath: /usr/bin/python2.7
MachineType: Hewlett-Packard HP EliteBook 850 G1
PackageArchitecture: all
Papersize: a4
ProcCmdline: /usr/bin/python /usr/bin/hp-config_usb_printer 001:005
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=e68c551a-87a9-4584-a12e-07c23e27c37c ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/hp-config_usb_printer', '001:005']
SourcePackage: hplip
Title: config_usb_printer.py crashed with ImportError in /usr/share/hplip/base/status.py: No module named hpmudext
UpgradeStatus: Upgraded to vivid on 2015-02-24 (5 days ago)
UserGroups:

dmi.bios.date: 02/09/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L71 Ver. 01.07
dmi.board.name: 198F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 15.52
dmi.chassis.asset.tag: CNU4139T12
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.07:bd02/09/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.52:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 850 G1
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

[Apport retracing service (apport)]

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.