Bug 30065 - Update request: update hplip to latest 3.21.12 to add support for several new printers
Summary: Update request: update hplip to latest 3.21.12 to add support for several new...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks: 10072 30059 30069
  Show dependency treegraph
 
Reported: 2022-02-17 22:29 CET by Thomas Andrews
Modified: 2022-03-12 04:08 CET (History)
8 users (show)

See Also:
Source RPM: hplip-3.21.2-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Thomas Andrews 2022-02-17 22:29:03 CET
Description of problem:
Our hplip is version 3.21.2. 

The latest release is 3.21.12, which according to https://developers.hp.com/hp-linux-imaging-and-printing/release_notes adds support for several new printers.
Comment 1 Lewis Smith 2022-02-18 11:49:14 CET
Thank you for the hint, TJ.
Like its companion bug 30059, assigning this request globally.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30059
Source RPM: (none) => hplip-3.21.2-1.mga8.src.rpm
Assignee: bugsquad => pkg-bugs

Morgan Leijström 2022-02-20 13:00:27 CET

Blocks: (none) => 30069

Comment 2 Nikolay Sabelnikov 2022-02-20 13:06:42 CET
Morgan, there is a catch in the update, I have already encountered this in other distrs. New hplip update they are adding new printers and cutting out the old ones, although the functionality of my printer is still on top. So before you update, let me know so I can check.

CC: (none) => 79625490833

Comment 3 sturmvogel 2022-02-20 14:08:11 CET
It's clearly described which printers are supported:
https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/index


And alsos clearly described which printers are unsupported (most of them belongs into a museum):
https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/unsupported
Comment 4 Nikolay Sabelnikov 2022-02-20 14:21:46 CET
(In reply to sturmvogel from comment #3)
> It's clearly described which printers are supported:
> https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/
> index
> 
> 
> And alsos clearly described which printers are unsupported (most of them
> belongs into a museum):
> https://developers.hp.com/hp-linux-imaging-and-printing/supported_devices/
> unsupported

I have an hp LaserJet cp1025nw printer and there are a lot of problems with the new drivers, previously there were much fewer such problems. Which, unfortunately, they will not solve, so the warranty on the printer has long been out.

Therefore, I strongly ask you, before releasing updates to the public, to send them to me for a test in order to check the correctness of the work.
Comment 5 sturmvogel 2022-02-20 14:24:45 CET
So that means we need to test all atm supported 3138 printers before releasing the update. Sounds valid.
Comment 6 sturmvogel 2022-02-20 14:26:35 CET
(In reply to Nikolay Sabelnikov from comment #4)
> Therefore, I strongly ask you, before releasing updates to the public, to
> send them to me for a test in order to check the correctness of the work.

You should get familiar with the testing procedures and how the testing repositorys work under Mageia. Nobody gets "send" the packages to test them. You have to use the testing repositorys yourself.
Comment 7 sturmvogel 2022-02-20 14:30:17 CET
And you can start right away with testing because hplip-3.21.2-1.mga8 is already in cauldron.
Comment 8 sturmvogel 2022-02-20 14:32:06 CET
hplip-3.21.12-2.mga9 is in cauldron
Comment 9 Morgan Leijström 2022-02-20 14:37:44 CET
I believe the benefit of shipping this as update weighs more than keeping our last version supporting very old printers.

If some user must use elder version, user can downgrade and add it to skip list.

Of course every Mageia user is invited to do testing, this is a community distro and how I ended up here...

@sturmvogel: Please no sarcasm - language translations are hard enough without.

CC: (none) => fri

Comment 10 Morgan Leijström 2022-02-20 14:45:55 CET
Related: udev rule, Bug 10072

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=10072

Comment 11 Nikolay Sabelnikov 2022-02-20 16:07:32 CET
(In reply to Morgan Leijström from comment #9)
> I believe the benefit of shipping this as update weighs more than keeping
> our last version supporting very old printers.
> 
> If some user must use elder version, user can downgrade and add it to skip
> list.
> 
> Of course every Mageia user is invited to do testing, this is a community
> distro and how I ended up here...
> 
> @sturmvogel: Please no sarcasm - language translations are hard enough
> without.

you're right, I see that an update is needed and I understand it, reading the bug, I'll test it in cauldron tomorrow and if it doesn't work, then I don't know what to do anymore. I'm definitely breaking my head with this, solving this problem. This is if the saddest scenario I'm assuming.
Comment 12 Nikolay Sabelnikov 2022-02-20 16:09:06 CET
(In reply to sturmvogel from comment #5)
> So that means we need to test all atm supported 3138 printers before
> releasing the update. Sounds valid.

and I ask you not to be sarcastic, if you took my side, then you definitely would not be joking.
Comment 13 Thomas Andrews 2022-02-20 17:21:40 CET
(In reply to Nikolay Sabelnikov from comment #2)
> Morgan, there is a catch in the update, I have already encountered this in
> other distrs. New hplip update they are adding new printers and cutting out
> the old ones, although the functionality of my printer is still on top. So
> before you update, let me know so I can check.

https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/Different%20Support%20Level.html indicates that HP's goal is to add new printers as they come out, but NOT to drop old ones. However, because of the sheer size of the list of supported printers, as of 2009 many of them, while not dropped, will not receive any new fixes, and some may even not wok correctly with new releases of hplip.

I have already run into this. My newest printer, an HP Envy Photo 7800 series all-in-one that came out just five years ago has been "supported" since hplip 3.17.2, but that support is listed as "Full(End of Support)." And there is a problem that the printer will not print in duplex on US Letter-sized paper. (Bug 30059) A simple change to the .ppd will fix it, but because HP has put it on End of Support it won't be coming from them. And I don't expect that to change with this update, even though I requested it. If I want it changed, I have to do it myself.

At the same time I have another printer, a Deskjet 5650, that, according to the copyright of the manual, is 19 years old. It has the same level of support as the Envy 7800, since hplip 0.95.0. And it still works. I used it just yesterday.

I also have a Color Laserjet CP1215, 15 years old. Curiously, that one is listed as having had "Full" support (no qualifier) since hplip 3.9.2. So that one MAY get new fixes, and it may not. But even if its designation changes to End of Support, I don't expect HP will drop it from the list entirely.
Comment 14 Nikolay Sabelnikov 2022-02-20 17:34:08 CET
(In reply to Thomas Andrews from comment #13)
> (In reply to Nikolay Sabelnikov from comment #2)
> > Morgan, there is a catch in the update, I have already encountered this in
> > other distrs. New hplip update they are adding new printers and cutting out
> > the old ones, although the functionality of my printer is still on top. So
> > before you update, let me know so I can check.
> 
> https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/
> Different%20Support%20Level.html indicates that HP's goal is to add new
> printers as they come out, but NOT to drop old ones. However, because of the
> sheer size of the list of supported printers, as of 2009 many of them, while
> not dropped, will not receive any new fixes, and some may even not wok
> correctly with new releases of hplip.
> 
> I have already run into this. My newest printer, an HP Envy Photo 7800
> series all-in-one that came out just five years ago has been "supported"
> since hplip 3.17.2, but that support is listed as "Full(End of Support)."
> And there is a problem that the printer will not print in duplex on US
> Letter-sized paper. (Bug 30059) A simple change to the .ppd will fix it, but
> because HP has put it on End of Support it won't be coming from them. And I
> don't expect that to change with this update, even though I requested it. If
> I want it changed, I have to do it myself.
> 
> At the same time I have another printer, a Deskjet 5650, that, according to
> the copyright of the manual, is 19 years old. It has the same level of
> support as the Envy 7800, since hplip 0.95.0. And it still works. I used it
> just yesterday.
> 
> I also have a Color Laserjet CP1215, 15 years old. Curiously, that one is
> listed as having had "Full" support (no qualifier) since hplip 3.9.2. So
> that one MAY get new fixes, and it may not. But even if its designation
> changes to End of Support, I don't expect HP will drop it from the list
> entirely.

this is true, but in my case the driver behaves incorrectly, you can look at this bug. 
https://bugzilla.rosalinux.ru/show_bug.cgi?id=11570
Comment 15 Morgan Leijström 2022-02-20 17:48:59 CET
If I read that correctly in translation, workaround is simply to use the old ppd?
(or old hplip)

Please no need to cite a lot of text, en not from just previous post.
Try keep total size of issue down for easier read.
Comment 16 Nikolay Sabelnikov 2022-02-20 18:26:22 CET
unfortunately, but it is. I have already written several times to hp, but with no result.
Comment 17 Thomas Andrews 2022-02-20 18:28:40 CET
I read a Google-translated site, too, where I see that the printer works in the current Mageia 8 version, but not in the newer hplip in Cauldron.

Please be aware that while checking things in Cauldron is a valuable exercise, and can help identify potential problems, something NOT working there doesn't necessarily mean that it won't work in Mageia 8. 

Cauldron is in development, and therefore issues are to be expected. When the developers believe they have the update for Mageia 8 ready for testing, it will be assigned to QA here for that testing before it is released to the public. 

You are more than welcome to help us do that testing.
Comment 18 Nikolay Sabelnikov 2022-02-20 18:53:05 CET
I will be happy to test in a stable branch, but for now I'm testing in cauldron via virtualbox.
Comment 19 Nikolay Sabelnikov 2022-02-20 19:21:14 CET
I checked in cauldron, printing is going fine. However, foo2zjs is used. I tried printing through hplip, but the quality between foo2zjs and hplip is incomparably much better for foo2zjs.
Comment 20 Nicolas Salguero 2022-02-21 13:23:55 CET
Suggested advisory:
========================

The updated packages:
  - add support for several new printers;
  - fix the ppd for HP Envy Photo 7800 series to allow US Letter size duplex printing;
  - fix uploading printer firmware automatically.

References:
https://bugs.mageia.org/show_bug.cgi?id=10072
https://bugs.mageia.org/show_bug.cgi?id=30059
https://bugs.mageia.org/show_bug.cgi?id=30065
https://bugs.mageia.org/show_bug.cgi?id=30069
========================

Updated packages in core/updates_testing:
========================
hplip-3.21.12-2.mga8
hplip-doc-3.21.12-2.mga8
hplip-gui-3.21.12-2.mga8
hplip-hpijs-3.21.12-2.mga8
hplip-hpijs-ppds-3.21.12-2.mga8
hplip-model-data-3.21.12-2.mga8
lib(64)hpip0-3.21.12-2.mga8
lib(64)hpip0-devel-3.21.12-2.mga8
lib(64)sane-hpaio1-3.21.12-2.mga8

from SRPM:
hplip-3.21.12-2.mga8.src.rpm

Status: NEW => ASSIGNED
Blocks: (none) => 30059, 10072
CC: (none) => nicolas.salguero

Nicolas Salguero 2022-02-21 13:24:08 CET

Assignee: pkg-bugs => qa-bugs

Comment 21 Nikolay Sabelnikov 2022-02-21 13:43:26 CET
how do I enable test reps?
Comment 22 Nicolas Salguero 2022-02-21 13:52:22 CET
Hi,

I found this link in Mageia Wiki: https://wiki.mageia.org/en/Enabling_the_Testing_media.

Best regards,

Nico.
Comment 23 Thomas Andrews 2022-02-21 14:33:21 CET
(In reply to Nikolay Sabelnikov from comment #21)
> how do I enable test reps?

If you'd rather, you can also use qarepo. https://wiki.mageia.org/en/QA_Repo

That's what I will be doing, once I'm on the computer where my printers are.
Comment 24 Thomas Andrews 2022-02-21 17:56:37 CET
I have these HP printers:

Deskjet 5650  (Deskjet 5600 series driver)
Color Laserjet CP1215
Envy Photo 7858 (Envy Photo 7800 series driver)

All printers seem to be working OK, except that the UI still objects to printing in duplex with Letter-sized paper on the Envy Photo 7858. The printer WILL print in duplex, after you have told it to do so despite the unnecessary warnings.

The Envy's scanner is working as expected.
Comment 25 PC LX 2022-02-22 10:26:31 CET
Installed and tested without issues.

Printer: HP Officejet 4658

System: Mageia 8, x86_64, Plasma DE, LXQt DE, Intel CPU, nVidia GPU using nvidia-current proprietary driver.

Tests included:
- Running HP GUI.
- Checking information shown by HP GUI (e.g. status, ink level).
- Scanning with xsane using the printer's plate and automatic feeder.
- Printing test page from HP GUI.
- Printing gray and color pages from Okular and LibreOffice.

Installed/updated packages:
- hplip-3.21.12-2.mga8.x86_64
- hplip-gui-3.21.12-2.mga8.x86_64
- hplip-hpijs-3.21.12-2.mga8.x86_64
- hplip-hpijs-ppds-3.21.12-2.mga8.x86_64
- hplip-model-data-3.21.12-2.mga8.x86_64
- lib64hpip0-3.21.12-2.mga8.x86_64
- lib64sane-hpaio1-3.21.12-2.mga8.x86_64

$ uname -a
Linux marte 5.15.23-desktop-1.mga8 #1 SMP Fri Feb 11 09:56:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
$ rpm -qa | egrep '(hplip|hpip|hpaio)' | sort
hplip-3.21.12-2.mga8
hplip-gui-3.21.12-2.mga8
hplip-hpijs-3.21.12-2.mga8
hplip-hpijs-ppds-3.21.12-2.mga8
hplip-model-data-3.21.12-2.mga8
lib64hpip0-3.21.12-2.mga8
lib64sane-hpaio1-3.21.12-2.mga8

CC: (none) => mageia

Comment 26 Nicolas Salguero 2022-02-22 10:35:35 CET
Putting on hold while trying to fix bug 30059.

Keywords: (none) => feedback

Comment 27 Nicolas Salguero 2022-02-22 10:52:00 CET
Suggested advisory:
========================

The updated packages:
  - add support for several new printers;
  - fix the ppd for HP Envy Photo 7800 series to allow US Letter size duplex printing;
  - fix uploading printer firmware automatically.

References:
https://bugs.mageia.org/show_bug.cgi?id=10072
https://bugs.mageia.org/show_bug.cgi?id=30059
https://bugs.mageia.org/show_bug.cgi?id=30065
https://bugs.mageia.org/show_bug.cgi?id=30069
========================

Updated packages in core/updates_testing:
========================
hplip-3.21.12-3.mga8
hplip-doc-3.21.12-3.mga8
hplip-gui-3.21.12-3.mga8
hplip-hpijs-3.21.12-3.mga8
hplip-hpijs-ppds-3.21.12-3.mga8
hplip-model-data-3.21.12-3.mga8
lib(64)hpip0-3.21.12-3.mga8
lib(64)hpip0-devel-3.21.12-3.mga8
lib(64)sane-hpaio1-3.21.12-3.mga8

from SRPM:
hplip-3.21.12-3.mga8.src.rpm

Keywords: feedback => (none)

Comment 28 Herman Viaene 2022-02-22 15:18:59 CET
MGA8-64 Plasma on Lenovo B50 in Dutch
Had already an HP-Envy 6022 Aall-in-one installed, so removed it before installation.
No installation issues.
Configured printer and scanner seemingly correct in MCC, scanner was recognized.
But when I tried to access the scanner in xsane, I got the error "device hpaio ......could not be accessed beause of missing ....".This came from the HP Device Manager". It proposed to download driver from HP site, and once this was executed with success, the scanner worked OK.

CC: (none) => herman.viaene

Comment 29 Len Lawrence 2022-02-22 19:55:01 CET
mga8, x64
Tried xsane on an HP Photosmart after updating the 9 packages.  It was all straightforward.  Saved a 300 dpi scan to a PNG image which displayed fine.

CC: (none) => tarazed25

Comment 30 Thomas Andrews 2022-02-22 23:07:40 CET
No installation issues.

On the HP Envy Photo 7858, the UI still objected to printing in duplex on Letter size paper, until after I had used MCC to remove the printer, and after a reboot, installed it again. Then the duplex/Letter combination worked as it should. 

The scanner also still worked after the re-install. Actually, since I never saw anything about the scanner during the removal or re-installation of the printer, I have my doubts that the scanner part was ever removed.
Comment 31 Thomas Andrews 2022-02-23 17:41:46 CET
(In reply to Nikolay Sabelnikov from comment #4)
> 
> I have an hp LaserJet cp1025nw printer and there are a lot of problems with
> the new drivers, previously there were much fewer such problems. Which,
> unfortunately, they will not solve, so the warranty on the printer has long
> been out.

Nikolay, I see from https://developers.hp.com/hp-linux-imaging-and-printing/binary_plugin.html that your printer needs the hp plugin for "printing support." I wonder... Is it possible that you are a victim of our Bug 10072? (HPLIP doesn't upload printer firmware automatically)

This morning I have been wondering the same about the printer in Bug 30069. That one also requires the plugin/firmware. The coincidence is thought-provoking.


Unfortunately, I don't have a clue about how to test to see if that's what's happening.
Comment 32 Thomas Andrews 2022-03-01 00:35:40 CET
In Comment 19, Nicolay stated that his CP1025nw printer was working for him in Cauldron with hplip 3.21.12, but that it is using the foo2zjs driver, rather than hplip.

This is similar to what I have learned about my Laserjet CP1215 printer. When I install it with MCC, the test page indicates it is using the foo2hp driver, which seems at least adequate. If I attempt to install it with the hp-setup gui, it fails at the step where the hp-required plugin is downloaded, and refuses to go further.

Since these two printers are both working with this update, if maybe not at "full" function, I don't believe they should hold this update back.

So that leaves bug 30069 and bug 10072. The latter is a firmware (plugin) issue, and from what I've been able to discover, the former bug may be a plugin  issue, as well. 

Is there anything we can do about this? If not, perhaps we should mark them as upstream bugs, and move on.
Comment 33 Len Lawrence 2022-03-11 18:57:12 CET
mga8, x64

Sidetracked here.  Spent the whole day trying to reestablish a portable HP Officejet100 as a bluetooth printer.  It has worked in the past and seemed to be OK on the bluetooth side but CUPS would not communicate with it this time.  It masquerades as a RF serial port under bluetooth.  The modules rfcomm, bluetooth and hci_usb are loaded but no sign of l2cap (not on the system - don't know how to install it).  So it is not clear whether this is a regression or a problem in cups or a missing module.

Abandoned that approach and switched to a direct USB connection and that worked without any problems.  HPLIP found a driver for it without user intervention and an A5 testpage printed out in seconds.

Looks like HPLIP is doing its job OK even if CUPS has forgotten how to deal with bluetooth.
Comment 34 Thomas Andrews 2022-03-12 00:27:02 CET
I  installed this on another system, with no installation issues. Then I used hp-setup as root to install my HP Envy Photo 7858 as a wireless network printer. This took a surprising amount of time, long enough at one point that I wondered if it was "stuck," but eventually was successful.

I'm going to label this as OK, and validate. I believe the remaining two blocks are both related to the need to download and install the proprietary HP plugin, but there seems to be an upstream issue that makes this process unreliable. 

Someone more knowledgeable than me needs to decide what, if anything we can do about those two bugs.

Advisory in Comment 27.

CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update
Whiteboard: (none) => MGA8-64-OK

Dave Hodgins 2022-03-12 00:36:57 CET

CC: (none) => davidwhodgins
Keywords: (none) => advisory

Comment 35 Mageia Robot 2022-03-12 04:08:37 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2022-0034.html

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.