Thank you for the report.
Having said that after installing the printer via CCM (MCC) the test page printed OK, did the printer work subsequently? If you ignore HPLIP, does the printer function correctly? In other words, is the problem of not being able to access the printer just related to HPLIP?

CC: (none) => lewyssmith

Hi
The printer works when not using hplip-toolbox :
I tried it with Kwrite : created a file and printed it from Kwrite

The problem seems to be that hplip-toolbox can't communicate with it
"error : channel write error"  even if it knows it is here (it appears as installed printer)

Thanks for this extra info.
If you install a system from the Live Plasma ISO, does the problem show equally in the installed system?
Asking this to see whether it relates just to the Live session, or is more permanent.

Hi Lewis
I can't install a Beta Live ISO on my computer...

But you are certainly reaching the problem for the Live Iso used as Live Iso
hp-toolbox seems needing to write somewhere which channel to use to communicate with the printer... if the path leads to the Live iso which is "readonly" that can't work

Hope that someone else with an hp printer install the Live ISO and confirm your diagnostic is right

Thanks for the extra comments. For the moment, the problem looks like HPLIP does not function in a Live session; this to pursue.

CC'ing TJ. Can you comment on this, perhaps ask other Live ISO testers? We need to pin down the problem before passing it on.

CC: (none) => andrewsfarm

I tested using the Mageia-9-beta1-Live-Plasma-x86_64 ISO with my elderly HP Photosmart C4180 All-in-One.

When configuring the printer in MCC, it offers two connection choices, HPLIP and USB. When choosing HPLIP, the printer is shown as available in the HP Device Manager and I can print a test page from there (the ink cartridges have long since dried up, but it goes through the motions :-) ).

If I choose the USB connection then HP Device Manager tells me "No installed HP devices found", which is the expected behaviour - you have to configure the printer to use the HPLIP connection for it to be available in HP Device Manager.

So this looks like a printer-specific bug in the hplip package.

CC: (none) => mageia

I've never tried installing a printer in Live mode, at least as far as I can remember, but this reminds me of behavior of HP printers I've seen in installed Mageia 9. It appears to be an hplip problem.

I see that this printer is capable of wireless operation. Is it installed as a network printer, or via usb? (The HP Toolbox seems to handle them differently.)

If usb, the messages you are getting seem to be show up when a printer goes into "power-saving" mode - or whatever HP is calling it these days. 

My three printers all have different amounts of time in "idle" before they go into "power-save," with the newest being the shortest. When in Power-save, the HP Toolbox seems to be unable to wake them up again, though some other apps are able to. But, if you switch off power to the printer, wait maybe 20-30 seconds, and switch it back on again, it might be able to communicate again.

Alternatively, you can install your printer as a network printer. That's what I have done with my HP Envy Photo 7858 all-in-one, and it hasn't shown this behavior since doing  that.

Hi Thomas and Martin

NB this printer works well in Mageia8 and can be used with the HP Device Manager (to print a test page, to launch the scanner, to align or clean cartridges and to verify if the cartridges are filled)

With the Live iso

I tried several installation of this hp 8100 serie all-in-one printer (with the CCM, with CUPS and with HP Device Manager)

Everytime I get a communication problem with the HP Device Manager (unable to print a test page, to use the scanner)  
but I can print a text directly with Kwrite without using HP Device Manager

I tried to add live to lp group
I tried to change the owner of the ppd file...

I always get two kind of messages
Communication error 5002
Or the printer is busy or powered off or disconnected



I launched hp-check -t from the console
here is an extract as an attachment :

Created attachment 13733 [details]
extract from the result of hp-check -t

extract from the result of hp-check -t

showing some dependencies missing

(perhaps hplip needs to be rebuilt with some last versions of BuildRrequires, or some dependencies are missing in the Live DVD ?)

(In reply to Thomas Andrews from comment #8)
> 
> 
> I see that this printer is capable of wireless operation. Is it installed as
> a network printer, or via usb? (The HP Toolbox seems to handle them
> differently.)

To use wifi you need to connect the printer first with USB
> 
> If usb, the messages you are getting seem to be show up when a printer goes
> into "power-saving" mode - or whatever HP is calling it these days. 
> 
> My three printers all have different amounts of time in "idle" before they
> go into "power-save," with the newest being the shortest. When in
> Power-save, the HP Toolbox seems to be unable to wake them up again, though
> some other apps are able to. But, if you switch off power to the printer,
> wait maybe 20-30 seconds, and switch it back on again, it might be able to
> communicate again.
> 
The printer is connected by USB... and I verified that it was not in power-save
I tried to unplug and plug again, power off and power on => no change

NB In Mageia 8 this printer can be waken up by the Device Manager when it was in power-save mode

> Alternatively, you can install your printer as a network printer. That's
> what I have done with my HP Envy Photo 7858 all-in-one, and it hasn't shown
> this behavior since doing  that.

"NB In Mageia 8 this printer can be waken up by the Device Manager when it was in power-save mode"

Yes, my usb printers are the same way, though each of them is a bit different from the other in how it behaves in Mageia 9. 

Mageia 8 uses hplip 3.22.6, while Mageia 9 is currently using hplip 3.22.10. That seems to be making the difference. 

I am in no sense of the word a developer, so there is unfortunately nothing I can do except wait for a solution, too. I don't know if our developers can fix it, or if we have to wait for an upstream solution.

You might try booting with the printer powered down, only powering up after the boot is complete. That seems to help with my non-Live installs of Cauldron. I have no idea how it would work for a Live system.

(In reply to Philippe Didier from comment #11)
> (In reply to Thomas Andrews from comment #8)
> > 
> > 
> > I see that this printer is capable of wireless operation. Is it installed as
> > a network printer, or via usb? (The HP Toolbox seems to handle them
> > differently.)
> 
> To use wifi you need to connect the printer first with USB
> > 
Well, yes and no. You need the usb connection when you first add the printer to your network, but you don't need usb after that.

If you were to connect your printer to your network router using Mageia 8, then you can use the same IP address to connect it as a network printer with the Mageia 9 beta1 Live isos.

In MCC, you go to set up the printer, add a new printer, and drop down the Network printer menu. Click on Find a network printer, and put the printer's IP address in the search box. It sould find it right away, and you can go from there.

I just did it with mine.

Thank you everybody for all the hard work looking into this.
HPLIP is giving us more & more grief. I have flagged it for ERRATA9.

ns80 is the most evident packager for HPLIP, so assigning this to you.
As already noted, we can just hope for the best from HPLIP updates.
Note especially comment 9, comment 10.

Keywords: (none) => FOR_ERRATA9
Assignee: bugsquad => nicolas.salguero
CC: lewyssmith => (none)

Created attachment 13734 [details]
extract from the result of hp-check -t in Mageia8

extract from the result of hp-check -t in Mageia8

Hi Martin 
Hi Lewis

I tested my Mageia8 Plasma Live ISO final release (that I had kept since I created it)


There's no problem for Mageia8 with HP Device Manager whatever the way I use to install the printer (with CCM or with HP Device Manager itself) :
HP Device Manager has access to it to print a test page or to use the scanner 

I launched hp-check -t and I attached the summary :

There's a little difference between the two files :
1) two missing dependencies in Mageia9  that didn't missed in Mageia8
-error: 'glibc-i18ndata' package is missing/incompatible
-error: 'glibc_lsb' package is missing/incompatible
2) two missing optional dependencies that didn't missed in Mageia8
-error: 'policykit' package is missing/incompatible
-error: 'policykit-gnome' package is missing/incompatible


NB glibc-2.36-34-6 has been updated some times in Cauldron since hplip-3.22.10 has been built with glibc-2.35-25-6
polkit-kde-agent has been updated too since december

Perhaps hplip needs to be rebuilt with the last versions of glibc and polkit-kde-agent to be compatible with them

just saw that hplip has just been pushed in the BS to be rebuilt with new glibc and polkit
Thanks to the reactive packager ns80 ;-)

I  wait until it is in the repo and will test again the Live ISO and update hplip to see if it solves the problem

Sorry for my stupid idea :
If I use a Live DVD, I can indeed update hplip and dbus and glibc and polkit
but the same problem remains
the reason is not in the updates :

I need to launch again the computer for glibc !!!! I didn't ! so glibc is not the one used to build hplip
but if I do launch again this all is lost   :-(

It's an aporia
No way to test with this Live DVD beta1 


need to wait the next beta2 which will include the last versions of glibc binutils libtool dbus polkit and hplip to test again

(In reply to Philippe Didier from comment #17)

> but if I do launch again this all is lost   :-(
> 

I thought there was a way to make a live install persistent?

CC: (none) => zen25000

Hi Barry

You are right for a Live install 
But I test the "Live DVD" as a Live DVD and don't install it, which allows nevertheless to update or add some rpms if the computer memory is wide enough
and if the updated rpms doesn't need a reboot to be taken in account (which is unfortunately the case for glibc which needs a reboot !!!)

I consider the "Live DVD" as a Demo or as something to use to verify if the components of a computer are compatible and if the programs are bugless before installing a new version of Mageia

I already did this for Mageia8 Live ISO and updated some rpms or add some others (such as guayadeque or opencpn for instance) to test them before installing Mageia.
Lots of updates appears after the final release of the LiveDVD and InstallDVD...  

The first feedbacks I wrote in Bugzilla  were after testing the LiveDVD and allowed to correct some problems (induced by wxgtk 3.1 for instance !)

I always wait for some time before I install a new version of Mageia with an "install DVD" and update it (before this I remain with the previous version on the computer I use everyday)

Installing a "Live DVD" fills the computer with lots of useless rpm (unneeded languages for instance) and doesn't allow to really test a beta "LiveDVD" as a Live DVD and find a way to improve it

So wait and see for the beta2 :)

(In reply to Philippe Didier from comment #19)
> Hi Barry
> 
> You are right for a Live install 
> But I test the "Live DVD" as a Live DVD and don't install it, which allows
> nevertheless to update or add some rpms if the computer memory is wide enough
> and if the updated rpms doesn't need a reboot to be taken in account (which
> is unfortunately the case for glibc which needs a reboot !!!)
> 
If, rather than putting it on a DVD, you use our Isodumper to "burn" the iso to a usb stick that is bigger than the iso(say 8GB or higher), the app can create a "persistence" partition on the stick. This will save changes you make, like installing a printer, updating things that require a reboot, and others. When you reboot, the changes will still be there. A side effect of this is that a reboot won't make you go through all the preliminary setup questions again.

> I consider the "Live DVD" as a Demo or as something to use to verify if the
> components of a computer are compatible and if the programs are bugless
> before installing a new version of Mageia
> 
> I already did this for Mageia8 Live ISO and updated some rpms or add some
> others (such as guayadeque or opencpn for instance) to test them before
> installing Mageia.
> Lots of updates appears after the final release of the LiveDVD and
> InstallDVD...  
> 
Yes, there has been a big update of Plasma, for example. I will have to admit that my experience with a LiveUSB with persistance is limited, and I don't know from personal use if it can handle that many updates.

> The first feedbacks I wrote in Bugzilla  were after testing the LiveDVD and
> allowed to correct some problems (induced by wxgtk 3.1 for instance !)
> 
> I always wait for some time before I install a new version of Mageia with an
> "install DVD" and update it (before this I remain with the previous version
> on the computer I use everyday)
> 
> Installing a "Live DVD" fills the computer with lots of useless rpm
> (unneeded languages for instance) and doesn't allow to really test a beta
> "LiveDVD" as a Live DVD and find a way to improve it
> 
Installing from the Live iso should be giving you the option to remove/not install languages and unneeded hardware support packages. If choosing to do that results in something being removed that shouldn't have been, we need to know about it as soon as possible so it can be corrected.

> So wait and see for the beta2 :)

Created attachment 13736 [details]
result of hp-chec -t in Mageia8

Created attachment 13737 [details]
result of hp-check -t in Mageia9

Hi Martin Thomas Barry Lewis

I changed the way to use a Live Iso thanks for Barry's and Thomas'  advices

Created a LiveUSB with persistence and updated it (991 rpmms to download and install 2 reboots => that took one hour...)

So the problem remains for hp-tools (HP Device Manager) in Mageia9

I tried several way to install the all in one printer
- with the CCM
- with CUPS web interface 
in both case the printer is working (printing a text file from Kwrite) 
it is present in HP Device Manager but HP Device Manager can't communicate with it in spite of the fact it is the default printer (device busy or powered down or unplugged)
I tried to unplug and replug, power off and power on : No change

Then I uninstalled the printer and I tried to install it with the HP Device Manager
(two way to do this 
- using "setup device" from HP Device manager button 
- using "CUPS" button)
After that, the printer doesn't appear at all in HP Device Manager although it was present in the list of detected printers to install

I added to attachments to the bug report :
result of hp-chec -t in Mageia8  (sorry for the typo a k is missing)
result of hp-check -t in Mageia9
You may compare them

It's an aporia ! no explanation

Comparing the two log files we can see that there's a problem 
with 2 required dependencies :
cups 
and dbus
and with an optional dependency :
polkit

compatibility problem ?

3 hypothesis :
the add-mga-support.patch is outdated (it allows to support mga 5 6 and 7 but neither 8 or 9)

the hplip-udev-rules.patch has been modified 

some patches have not been rediffed

Still struggling with this bug :

I used my Mageia8 system to build HPLIP 3.22.6 rpms inside mock for Cauldron and copied them on the LiveUSB (changing their owner to be able to use them)

I launched Mageia9 with the liveUSB 
uninstalled the whole HPLIP 3.22.10 stuff 
replaced it with the built HPLIP 3.22.6 stuff (being asked to add python3-sip)

Several tests :
install the printer with CCM (print a test page OK) then uninstall it
install the printer with CUPS (print a test page OK) then uninstall it
install the printer with HP Device Manager (unable to print a test page with it) 

In the three cases the printer appears with a red cross in the left part of the window of the HP Device Manager but there's always a communication error (device busy or unplugged or powered off)

NB when I print a test page from CUPS or the CCM the status tab of the HP Device Manager indicates that the printer is printing after that it indicates again that the printer is busy or unplugged or powered off

I  used hp-plugin in a console to update the firmware => no change

I switched the USB port to connect the printer => it appeared briefly as idle in the left part of the window of the HP Device Manager as available (3 seconds) but quickly was marked with a red cross

It definitely seems to be a problem with dbus (or precisely with python-qt5-bus)

Googling a little I found this 

https://developers.hp.com/hp-linux-imaging-and-printing/KnowledgeBase/InstallHPLIPwithqt5.html?language=es-un

apparently with Qt5 (which is used in Cauldron) 
there's something to add to the spec file : 2 new BR : PyQt5 and python-qt5-bus
and something to modify in configure to enable qt5 and disable qt4 if it's not done automatically

perhaps a new patch is needed ? but I'm not skille for this

I finally found the cause of the problem !!!!

It is not a hplip problem 
it is not a dbus problem
it is not a cups problem
it is not a polkit problem


ALL this is caused by a new rpm installed by Mageia9 that didn't exist in Mageia8

The culprit is ipp-usb !
It prevents communication between HP Device Manager and my USB connected HP printer

If I uninstall it everything is OK !!! I can use HP Device Manager 
to verify the level of ink cartridges
to launch the scanner
to print a test page

That may be added to Errata 9

Good detective work Philippe! With that information I find it's a known problem:

https://docs.fedoraproject.org/en-US/quick-docs/cups-known-issues/#_golang_github_openprinting_ipp_usb

I wonder why it didn't affect my HP printer. Maybe it's using a different communication protocol. I'll try to check that.

I just changed the name of the srpm (in fact ipp-usb rpm is built by golang-github-openprinting-ipp-usb srpm)

There's a conflict between ipp-usb and the use of the proprietary drivers...
They can't be used side by side

If ipp-usb is present the CCM uses it to install and use a printer or a scanner and they work driverless (if the printer and scanner are Air-print compatible)
Then the printer is occupied by this use and HP-Device-Manager (for instance) can't communicate with the printer

The installation of ipp-usb should not coexist with hpip (asked by task-printing) 

At the beginning of an installation the user must have the choice between ipp-usb (allowing to use a recent scanner or printer without driver) or task printing (if the printer is not in the list of hardwares compatible with ipp-usb)

It maybe confusing for a Mageia user to see HP-Device-Manager no more working  without any explanation (no more access to the level of ink in the cartridges, no way to launch a scanner from it)

(In reply to Martin Whitaker from comment #29)
> Good detective work Philippe! With that information I find it's a known
> problem:
> 
> https://docs.fedoraproject.org/en-US/quick-docs/cups-known-issues/
> #_golang_github_openprinting_ipp_usb
> 
> I wonder why it didn't affect my HP printer. Maybe it's using a different
> communication protocol. I'll try to check that.

Maybe your printer is too old to work with ipp-usb (not Air-print compatible ?) and hplip is necessary for it

ipp-usb creates confusion too if used beside a classical installation of the printer
or scanner : two printers and two scanners exist side by side inside CUPS and CCM

Then you don't know which one to use and the classical won't work with sane-backend


Beside this some scanners and printers need to have their firmware upgraded  to work well with ipp-usb ...

Ipp-usb is a good idea but doesn't fit every situation and may create problems

Maybe it's too soon to integrate it systematically in the Live ISO ?

(In reply to Philippe Didier from comment #32)
> Ipp-usb is a good idea but doesn't fit every situation and may create
> problems
> 
> Maybe it's too soon to integrate it systematically in the Live ISO ?

It's not specific to the Live ISO, ipp-usb is recommended by the cups package so will be pulled in automatically when the cups package is installed. It won't be included if you are installing from the classical installer ISO (and haven't added on-line media) because the ipp-usb package is not included on that ISO.

From the reading I've done, it seems ipp-usb may be necessary to support other printers, so I don't know that we can simply exclude it.

Hi Martin

ipp-usb brings some progress (better quality of printing for some printers, no need for driver) but sometimes some problems too (printers needing a firmware update not so easy to do for some users)

Since Cups uses this and gets a kind of priority for the usage of the printer
 the conflict in access to the USB port used by the printer makes the classical tools unusable without an easy to find explanation 
(I spent some time to find it and to solve the problem by uninstalling the ipp-usb rpm)

Users (particularly newbies testing the LiveISO) need to be informed of this conflict and of the way to solve it if necessary

User upgrading from Mageia8 to Mageia9 may be surprised and think there is bug

There something to write in Errata or in Release Note 
unless it is possible to inform the user an other way when ipp-usb is installed
(a kind of warning particularly in the CCM...)

This must be what's going on with Bug 31222. That was with a hard drive install of Mageia 9, not from one of the Lives, so I thought perhaps this was different. It also was with an install from much earlier in Cauldron development, so much has changed in the meantime.

I wasn't seeing the problem with the printer, but then I don't use that as a printer much at all - the ink carts dry up too much between uses. Since that time it became more convenient for me to use that MFP as a wireless device, which avoided the whole situation. 

See Bug 31222 comment 16. If I booted with the printer powered up I saw the problem, but if I booted with it powered down and just powered it up when I wanted to use it, it worked as expected. I was also seeing the "device communication error" with all HP usb-connected printers, not just those with wireless capability.

That was why I brought that up as a possible workaround earlier, but it seems that different printers act differently in this situation. Differences in individual printer firmwares, perhaps? 

I think maybe. Phillipe says he has to connect with usb in order to connect with wifi to his network. But while my printer can work that way, it can also do that from the front panel with no usb connection at all. Individual differences.

But now, after Phillipe's work, I'm wondering if my two usb-only printers would no longer show the "device communication error" if I were to remove the ipp-usb rpm...

(In reply to Thomas Andrews from comment #35)
> 
> 
Hi Thomas
> 
> I think maybe. Phillipe says he has to connect with usb in order to connect
> with wifi to his network. But while my printer can work that way, it can
> also do that from the front panel with no usb connection at all. Individual
> differences.
> 
>
What I said about wifi is that in Mageia8 if you want to use wifi with an HP printer you need to plug it first to USB, so that HP-Device-Manager can create the configuration by fetching info from the printer... In a second time you can unplug it

I didn't try to use wifi printing with Mageia9 for now since HP-Device-Manager couldn't communicate with the printer because of ipp-usb


I didn't try to configure the printer to work with wifi since ipp-usb has priority : I don't know if there's a way to do this without using HP-Device-Manager and didn't find any explanation in the Mageia Wiki

I even tried to uninstall the whole hplip stuff to see what happens : I was asked to uninstall lots of things such as task-printing and lots of other rpms => a real mess !!!

I didn't verify in /usr/lib/udev/rules.d/ if the rule of ipp-usb-rule conflicts with printers-rule

(In reply to Philippe Didier from comment #36)
> I didn't try to configure the printer to work with wifi since ipp-usb has
> priority : I don't know if there's a way to do this without using
> HP-Device-Manager and didn't find any explanation in the Mageia Wiki

My understanding is that it is possible to do this over WiFi, but only if your firewall is configured to allow it. Check the "Network services autodiscovery" and "Network printer/scanner autodiscovery" settings in drakfirewall.

From reading https://wiki.debian.org/CUPSDriverlessPrinting, when using a USB connection, if you have ipp-usb installed *and* enable the cups-browsed service, the printer should be automatically discovered and configured by CUPS and listed as a network printer. Neither of my printers supports IPP, so I can't test this myself.

(In reply to Philippe Didier from comment #36)
> >
> What I said about wifi is that in Mageia8 if you want to use wifi with an HP
> printer you need to plug it first to USB, so that HP-Device-Manager can
> create the configuration by fetching info from the printer... In a second
> time you can unplug it
> 
As I tried to explain in comment 13, you do need the printer connected via usb IF the printer hasn't yet received a static IP address from that network. This would be if it's a new printer, or if the router has been changed, or if the printer is moved to a different network. But if the printer DOES have a static IP on the network, it won't change when you install a new OS. The trick to installing the printer without a usb connection is that you have to know that IP.

There are two ways that I have used to install my HP printer as a wireless printer. Quoting from 
https://doc.mageia.org/mcc/8/en/content/mcc-hardware.html#system-config-printer :

"You can add your network printer by choosing the protocol it uses to talk to your computer over the network. If you don't know which protocol to choose, you can try the Network Printer - Find Network Printer option in the Devices menu and give the IP address of the printer in the box on the right, where it says "host". 
If the tool recognises your printer or printserver, it will propose a protocol and a queue..." That is the way I usually use. So far, it has always worked.

Alternatively, you can, as root, run "hp-setup <printer's IP address>" and it will go through the process. I don't usually use hp-setup because one of my printers, a Color Laserjet CP1215, works better with the foo2hp driver that MCC sets it up to use than with the hplip driver that hp-setup will force it to use. It worked OK for my HP wireless printer during a test of a Mageia 8 hplip update, but I still prefer MCC.

Hi again

I tested Mageia9 Live Plasma Beta2 with a USB stick (persistent)
The problem remains the same
There's an incompatibility for HP-tools if ipp-usb has been installed (default install...)

To install correctly my HP all-in-one printer, so that I can use it from the HPLIP tray icon, I need to remove ipp-usb...
Then the HPLIP tray icon and the HP-tools work perfectly

Something for Erratas ?
This looks complicated to modify the printer install exclusively for HP printers

Feels like suitable for errata.

Is this limited to Live?

@Nicholas (packager) have you had time to look into this?

CC: (none) => fri

Martin said in comment 33 that ipp-usb is not included on the CIs. 

I just checked the beta2 isos, and that's still true. It is on all the Lives, but not the CIs.

And I also see

$ urpmq --whatrequires ipp-usb
ipp-usb

So when does it get installed?

Oh, that is too explained in same comment...:

When installing cups with on-line repos enabled, because it is recommended by cups.

(a --whatrecommends option to urpmq would have been useful :) )

(In reply to Morgan Leijström from comment #43)
> Oh, that is too explained in same comment...:
> 
> When installing cups with on-line repos enabled, because it is recommended
> by cups.
> 
> (a --whatrecommends option to urpmq would have been useful :) )

Sounds like an excellent enhancement request for a new bug report to me...

In my opinion, the fix has to come from HPlip. 

We can't simply not install ipp-usb, because there are a number of printers of other brands that would not work as well without it. And we can't specify not installing it if hplip is being used, because it's perfectly possible that a user could have an HP printer AND another brand, both of which he'd like to work.

So for now, it looks to me like a note in Errata is the best we can do.

Bug 32053 - Suggestion: add option --whatrecommends to urpmq

---

https://wiki.mageia.org/en/Mageia_9_Errata#Printing

Keywords: FOR_ERRATA9 => IN_ERRATA9

(In reply to Philippe Didier from comment #27)
> I finally found the cause of the problem !!!!
> 
> It is not a hplip problem 
> it is not a dbus problem
> it is not a cups problem
> it is not a polkit problem
> 
> 
> ALL this is caused by a new rpm installed by Mageia9 that didn't exist in
> Mageia8
> 
> The culprit is ipp-usb !
> It prevents communication between HP Device Manager and my USB connected HP
> printer
> 
> If I uninstall it everything is OK !!! I can use HP Device Manager 
> to verify the level of ink cartridges
> to launch the scanner
> to print a test page


Wow, I spent so much time trying to debug this problem! I uninstalled and reinstalled my HP printer many times without success and I was almost ready to throw my printer against the wall! And I suddenly found this bug report. I uninstalled ipp-usb and everything now works like a charm.

Thank you very much Philippe for having found the culprit! :)


@To packagers: Mageia 9 has ipp-usb 0.9.19, which was released on May 2021. The most recent release currently is 0.9.23 which has been released on November 2022. Wouldn't it make sense to update this RPM to see if this fixes the problem? With all the trouble 0.9.19 is currently causing to several of us, it wouldn't harm to update it.

CC: (none) => LpSolit

Hi Frédéric

Unfortunately changing the version won't bring any improvement

The problem is that lots of printers air-print compatible work well or even better with ipp-usb... than when using an other driver
and that's why it is installed by default

Worst : we can't ask to uninstall ipp-usb if hplip has been installed because if other printers non HP are installed they will miss ipp-usb
(see : https://bugs.mageia.org/show_bug.cgi?id=31623#c45)

The only way to resolve this problem is a warning in Errata
Or perhaps a warning appearing when the hplip rpm is installed, like for some other rpms which display an information when they are installed or updated...
(For this kind of warning a README.urpmi file is added to the Sources used to build the rpm)

(In reply to Philippe Didier from comment #48)
>  a warning in Errata

Errata 9 say currently : 

" mga#31623 - hp-toolbox can't use the installed HP printer if the ipp-usb package is installed. Problem: some printers need ipp-usb. Workaround: Choose if you want ipp-usb or not installed for your printer. Fresh installs from Classic installer do not have this package installed unless on-line repositories have been used during installation. Live media have ipp-usb installed. "

(In reply to Morgan Leijström from comment #49)
> (In reply to Philippe Didier from comment #48)
> >  a warning in Errata
> 
> Errata 9 say currently : 

I think a warning in the errata is not enough. I didn't type "hp-toolbox" in a shell before reading this bug report. I simply went to MCC > Hardware > Printers or I clicked on "HP Device Manager" in the Tools submenu found in the apps menu. You are asking users to know that "HP Device Manager" *is* hp-toolbox (or vice versa). At the minimum, the errata should mention "HP Device Manager" besides "hp-toolbox".

What is even more confusing is that the item right before this one in the errata mentions that "Booting up with usb-connected printer powered up may show "device communication error" in the HP Device Manager if package ipp-usb was removed". So here, the errata suggests that you should not remove the ipp-usb package. Confusing to non-expert users.


> Or perhaps a warning appearing when the hplip rpm is installed, like for
> some other rpms which display an information when they are installed or
> updated...
> (For this kind of warning a README.urpmi file is added to the Sources used
> to build the rpm)

I think that's a better workaround.

Summary: in Mageia9 beta1 Plasma Live DVD hp-toolbox can't use the installed HP printer if the ipp-usb rpm is installed.... idem for Beta2 ! => In Mageia9, hp-toolbox (HP Device Manager) cannot use the installed HP printer if the ipp-usb RPM is installed

Hi guys!

Dilemma. We either print or scan. The two will not work interchangeably. After an upgrade from Mageia 8 to 9, my friend contacted me saying that the printer does not work, but the scanner does. Searching on the net, I also found the Mageia 9 errata and finally removed a printer from the printers and then the ipp-usb package as well. I added the printer to MCC again and chose USB connection. Now the printer works, but you can't scan. scanimage -L sees the scanner, but there is an I/O error.

HP DeskJet 2700 All-in-One

CC: (none) => csablak

You mean that when you last installed the printer in MCC, you chose "USB" rather than "HPLIP?" That's probably the culprit. Unlike hplip, the generic USB driver doesn't include the driver for the scanner.

Try removing the printer once more, then re-install using the hplip option. Make sure usb-ipp isn't installed.

There seems to be an upstream bug that only affects usb-connected printers, where if you boot with the printer powered up, hplip may have problems communicating with it. The workaround is to power the printer down, wait a few seconds, then power it back up again. Or, boot with the printer powered down, and wait for the boot process to complete before powering it up.

Alternatively, if you can connect this printer to a network, the communication error doesn't seem to happen. At least, not with my HP Envy Photo 7858.