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

Please run the commands

dpkg -l | grep hplip
dpkg -l | grep hpmudext

in a terminal window. Post the output here.

ii hplip 3.15.2-0ubuntu2
                           amd64 HP Linux Printing and Imaging
System (HPLIP)
ii hplip-data 3.15.2-0ubuntu2
                           all HP Linux Printing and Imaging -
data files

Am 26.02.2015 um 18:26 schrieb Till Kamppeter:
> Please run the commands
>
> dpkg -l | grep hplip
> dpkg -l | grep hpmudext
>
> in a terminal window. Post the output here.
>
>
> ** Changed in: hplip (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: hplip
> Status: New => Incomplete
>

I got this bug on my box (Utopic, but with the Vivid packages of HPLIP) and checked what I have exactly installed and all HPLIP packages including the hpmudext packages are of version 3.15.2-0ubuntu2, so there is no version mismatch. In addition, I have installed all binary packages which get built from the hplip source package, so I must have installed all files of the upstream "make install" and so no file should be missing.

I tried also running "python3" and then on the Python command line "import hpmudext" which works whereas running "python" (=Python 2.x) and "import hpmudext" fails, giving the impression that something runs accidentally under Python2.

For me it looks like that something went with the Python3 transition by upstream, so to the HPLIP developers at HP, please check.

Note also that during the package build I modify the shebangs of .py files from /usr/bin/python to /usr/bin/python3 to assure that everything is running under Python3, and config_usb_printer.py has a Python3 shebang in the Ubuntu package.

It is actually caused by accidentally running under Python2, as the apport info in the initial description contains:

InterpreterPath: /usr/bin/python2.7

The only strange thing is how this can happen with the Python3 shebang in config_usb_printer.py.

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.

Changed the "master bug" of this series of duplicate bugs from bug 1419888 to this bug, so that my comments get more visible.

In my case I think this is happenes because I have hplip set to be off at boot.It is trying to start anyway and then crashes.

my results:

elhoir@elhoir-desktop:~$ dpkg -l | grep hplip
ii hplip 3.15.2-0ubuntu2 amd64 HP Linux Printing and Imaging System (HPLIP)
ii hplip-data 3.15.2-0ubuntu2 all HP Linux Printing and Imaging - data files
elhoir@elhoir-desktop:~$ dpkg -l | grep hpmudext
elhoir@elhoir-desktop:~$

> The only strange thing is how this can happen with the Python3 shebang in config_usb_printer.py.

Because it's not being invoked directly but by calling
    python config_usb_printer.py
And python is always python2, the question here is who is doing the invokation.

Ok, found the culprit,

     /lib/udev/rules.d/56-hpmud.rules

has

ENV{hp_test}=="yes", PROGRAM="/bin/sh -c 'logger -p user.info loading HP Device $env{BUSNUM} $env{DEVNUM}'", RUN+="/bin/sh -c 'if [ -f /usr/bin/systemctl ]; then /usr/bin/systemctl --no-block start hplip-printer@$env{BUSNUM}:$env{DEVNUM}.service; else /usr/bin/nohup /usr/bin/python /usr/bin/hp-config_usb_printer $env{BUSNUM}:$env{DEVNUM} ; fi &'"

given that /usr/bin/hp-config_usb_printer is executable by itself the

/usr/bin/python

should just be dropped.

To the HPLIP developers at HP:

Please go through the whole HPLIP and take care that a script is always called directly:

<path>/<script> <command line parameters>

and never by explicitly calling the interpreter like

<interpreter> <path>/<script> <command line parameters>

This way we can simply control by the shebang in the script which interpreter version or flavor is used. So the same interpreter gets used both when the user explicitly calls the script from the command line and when another script or program calls the script.

This bug was fixed in the package hplip - 3.15.2-0ubuntu4

---------------
hplip (3.15.2-0ubuntu4) vivid; urgency=low

  * debian/rules: Remove explicit call of /usr/bin/python when calling the
    /usr/bin/hp-config_usb_printer script so that the shebang does not get
    overridden (LP: #1425812).
 -- Till Kamppeter <email address hidden> Tue, 17 Mar 2015 16:04:00 +0100

I've updated to 3.15.7 and this issue still occurs. There is no file /lib/udev/rules.d/*hpmud.rules that I can edit.

Dennis, the file /lib/udev/rules.d/56-hpmud.rules is part of the "hplip" package. Make sure the "hplip" package is installed. If it is already installed, run

sudo apt-get install --reinstall hplip

to refresh its installation.