[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#946804: marked as done (plugin download fails (broken keyserver, assumes Python 2))

Your message dated Mon, 16 Dec 2019 08:01:34 +0100
with message-id <9860821.W0ZDGQzLXt@odyx.org>
and subject line Re: Bug#946804: plugin download fails (broken keyserver, assumes Python 2)
has caused the Debian Bug report #946804,
regarding plugin download fails (broken keyserver, assumes Python 2)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
946804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946804
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: hplip
Version: 3.18.12+dfsg0-2
Severity: important

Hi,

I upgraded a machine to buster recently, and printing (an HP 1025nw,
with HP's proprietary plugin) just silently broke. Everything looked
OK, but nothing was coming out. Finally I found in /var/log/debug:

  Dec 16 00:07:20 localhost hpcups[9302]: prnt/hpcups/HPCupsFilter.cpp 489: m_Job initialization failed with error = 48

The Internet suggested I needed to run hp-setup again (which needed
X forwarding, but OK...). It failed pretty badly, since it tried to
contact a keyserver that no longer existed, namely pgpkeys.mit.edu.
(Downloading the key manually from a different keyserver didn't help.)
Worse, however, is that the plugin installation just silently failed.

Eventually, I found out which file it was downloading, namely:

  http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-3.18.12-plugin.run

and ran it myself. It turned out that it couldn't find its HPLIP modules;
by that, it seemingly meant the Python CUPS modules. The problem is that
the .run file prefers /usr/bin/python, which is Python 2, but Debian now only
ships CUPS modules for Python 3. (If you don't have /usr/bin/python, it tries
python3.)

After installing the plugin properly and getting a success message, it _still_
claimed I needed a plugin that I didn't have, and offered to run hp-plugin
for me, but now my old printer definition worked again, so I could just abort
the wizard and print. But new installations will probably be broken.

-- System Information:
Debian Release: 10.2
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.11 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message --- 
Version: 3.19.8+dfsg0-2
Control: tags -1 +buster +upstream

Hi Steinar, and thanks for your bugreport,

Le lundi, 16 décembre 2019, 00.50:50 h CET Steinar H. Gunderson a écrit :
> I upgraded a machine to buster recently, and printing (an HP 1025nw,
> with HP's proprietary plugin) just silently broke. Everything looked
> OK, but nothing was coming out. Finally I found in /var/log/debug:
> 
>   Dec 16 00:07:20 localhost hpcups[9302]: prnt/hpcups/HPCupsFilter.cpp 489:
> m_Job initialization failed with error = 48
> 
> The Internet suggested I needed to run hp-setup again (which needed
> X forwarding, but OK...). It failed pretty badly, since it tried to
> contact a keyserver that no longer existed, namely pgpkeys.mit.edu.
> (Downloading the key manually from a different keyserver didn't help.)

That's really unfortunate indeed; and something I fixed in 3.19.8+dfsg0-2 
through installing and using the PGP public key directly in the package.

> Worse, however, is that the plugin installation just silently failed.
> 
> Eventually, I found out which file it was downloading, namely:
> 
> http://www.openprinting.org/download/printdriver/auxfiles/HP/plugins/hplip-> 3.18.12-plugin.run
> 
> and ran it myself. It turned out that it couldn't find its HPLIP modules;
> by that, it seemingly meant the Python CUPS modules. The problem is that
> the .run file prefers /usr/bin/python, which is Python 2, but Debian now
> only ships CUPS modules for Python 3. (If you don't have /usr/bin/python,
> it tries python3.)

That's an upstream-provided "binary artifact"; which should be fixed by them.

> After installing the plugin properly and getting a success message, it
> _still_ claimed I needed a plugin that I didn't have, and offered to run
> hp-plugin for me, but now my old printer definition worked again, so I
> could just abort the wizard and print. But new installations will probably
> be broken.

hplip is a mess; and more so in stable; and I'm sorry for this (on upstream's 
behalf I guess).

That said, I wonder if you could make reasonable use of your HP printer 
through driverless: https://wiki.debian.org/DriverlessPrinting

For "normal" printing, it might very well be that you don't _actually_ need 
hplip.

Cheers,

    OdyX

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: