-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with HP-ENVY-5530-series #48
Comments
found a solution on sid alain@sid:~$ lsb_release -a alain@sid:~$ apt-cache madison ipp-usb sudo aptitude install ipp-usb= 0.9.17-3+b4 sudo apt-mark hold ipp-usb . pour verifier apt-mark showhold sudo dpkg -l ipp-usb pour mettre a jour sudo apt-mark unhold ipp-usb sudo apt install --reinstall ipp-usb pour verifier now the command http://localhost:60000 gives me plain access to the printer interface . |
Hi, I can confirm this issue with a different printer with version 0.9.20. Thorsten [1] https://www.usb.org/sites/default/files/usbprint11a021811.pdf |
I like your post. in order to help dev's, can you explain me how to debug the ipp-usb package and provide useful information for its rewriting or troubleshooting ? I don't know anything about debugging or programming. if you prefer that I leave this to others, tell me. friendly, p.s.: printer is H.P. Envy 5536 (recognized like a 5530 series) Translated with www.DeepL.com/Translator (free version) |
"Proto==4" is IPP interface, if the "Proto==2", means the device doesn't support IPP over USB specification. |
i've just tested ipp-usb with 5.17 kernel . thanks , |
@BELLECalain do all versions of ipp-usb not work with kernel 5.17? Or is it only the new 0.9.20 version? Thanks, @tangyanli USB printing (7/1/x) has currently 4 different protocols: x = 1 is mon-directional streaming, x = 2 is bi-directional streaming, x = 3 is IEEE-1284 packaet format (AFAIK only used by HPLIP currently), x = 4 is IPP-over-USB. IPP-over-USB devices (7/1/4) ALWAYS print and scan driverless. For printing this means at least one of AirPrint, IPP Everywhere, Mopria, or Wi-Fi Direct Print is supported (or at least IPP 2.0 plus understanding at least one page description language of PDF, Apple Raster/URF, PWG Raster, PCLm), for scanning this means to understand at least one of eSCL and WSD/WS Scan. |
Hi @BELLECalain, may I ask you to collect a whole set of log files ( |
Hello @alexpevzner @BELLECalain provided four logs to the Debian bug report at https://lists.debian.org/debian-printing/2022/04/msg00071.html. I have attached the fourth one. |
Hi @debiantriage, nice to hear from you and thanks!
Looks like |
***@***.***:~$ sudo aptitude search ~b
***@***.***:~$ sudo apt-get check
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances... Fait
Lecture des informations d'état... Fait
it seems there is no broken packages
Le 25/04/2022 à 12:29, Alexander Pevzner a écrit :
…
Hi @debiantriage <https://github.com/debiantriage>, nice to hear from
you and thanks!
libusb_bulk_transfer: Operation timed out
Looks like |libusb| is broken on 5.17.x this kernel (or on this
distro). It would be nice to retry wth apparmor/selinux disabled
(depending on a distro).
—
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYTV5L7LLTLOS7TVCWI72DLVGZXXVANCNFSM5S3UXGEQ>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I don't mean the package itself (i.e., files the package consist of) is broken. I mean, the package's functionality is broken. One of possible reasons is the apparmor/selinux settings. It makes sense to temporary disable apparmor/selinux and to retry. If it will help, it will seriously localise the source of the problem. What exactly your Linux use, depends on a distro. Fedora and similar love to use selinix. Ubuntu loves apparmor. I don't know about other distros. |
@BELLECalain A quick way to do as @alexpevzner suggests is to purge apparmor and reboot. It is easily reinstalled. As a separate test, would you try a different USB port? |
uninstalled apparmor and reboot .
system-config-printer do not work better and do not recognize my printer .
with the 0.9.20-1 ipp-usb package , it seems not to work better than
with the stable one
(ok for stable version) .
saw this :
https://wiki.debian.org/AppArmor/HowToUse#Enable_AppArmor
and did this before uninstall :
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
now deleted file .cfg
i am reinstalling apparmor .
do i have to do this : ?
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=1 security=apparmor"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
thanks .
friendly ,
respectfully ;
alain .
Le 25/04/2022 à 15:27, Brian Potkin a écrit :
…
@BELLECalain <https://github.com/BELLECalain> A quick way to do as
@alexpevzner <https://github.com/alexpevzner> suggests is to purge
apparmor and reboot. It is easily reinstalled.
As a separate test, would you try a different USB port?
—
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYTV5L3UFJK4YYOUR5I3UHDVG2MUBANCNFSM5S3UXGEQ>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
i don't know if using another usb port will be useless .
like using the printer with the stable version of ipp-usb (instead of
the sid version) is ok .
Le 25/04/2022 à 15:27, Brian Potkin a écrit :
…
@BELLECalain <https://github.com/BELLECalain> A quick way to do as
@alexpevzner <https://github.com/alexpevzner> suggests is to purge
apparmor and reboot. It is easily reinstalled.
As a separate test, would you try a different USB port?
—
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYTV5L3UFJK4YYOUR5I3UHDVG2MUBANCNFSM5S3UXGEQ>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Le 25/04/2022 à 16:10, alain a écrit :
…
uninstalled apparmor and reboot .
system-config-printer do not work better and do not recognize my
printer .
with the 0.9.20-1 ipp-usb package , it seems not to work better than
with the stable one
(ok for stable version) .
saw this :
https://wiki.debian.org/AppArmor/HowToUse#Enable_AppArmor
and did this before uninstall :
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=0"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
now deleted file .cfg
i am reinstalling apparmor .
do i have to do this : ?
echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT apparmor=1 security=apparmor"' \
| sudo tee /etc/default/grub.d/apparmor.cfg
thanks .
friendly ,
respectfully ;
alain .
Le 25/04/2022 à 15:27, Brian Potkin a écrit :
>
> @BELLECalain <https://github.com/BELLECalain> A quick way to do as
> @alexpevzner <https://github.com/alexpevzner> suggests is to purge
> apparmor and reboot. It is easily reinstalled.
>
> As a separate test, would you try a different USB port?
>
> —
> Reply to this email directly, view it on GitHub
> <#48 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYTV5L3UFJK4YYOUR5I3UHDVG2MUBANCNFSM5S3UXGEQ>.
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Bearing in mind that my understanding of ipp-usb internals is very tenuous, may I inquire whether the following (from #32) is worth
My thoughts have turned to seeing issue like this one and #33 as having firmware bugs involved, although I am still perplexed by @BELLECalain regaining printing and scanning by downgrading ipp-usb. |
Hi All, I've just tested |
Hi! I'm trying to understand the situation with this issue, and I must confess, I'm completely confused. Too many information, sometimes controverting, split into small pieces around entire Internet. Now I'm trying to bring all parts together. First questions:
|
Ping |
hello alexander pevzner and brian potkin . I will try to answer your 4 questions clearly:
once my printer is plugged , system-config-printer do not recognize it . i can not print even a test page . and never see the printer icon .
once i plug in my printer (or power it on) , after a very short delay , system-config-printer recognize it and i can print a test page and my i see the printer icon and it is fully functional .
system-config-printer never recognize it and i can not print even a test apparmor seems to do nothing with the testing/sid version of ipp-usb . I answered your questions as you wanted? friendly, alain. nb: for instance , i am working with the stable version of ipp-usb and all under 5.17 kernel . my system is constantly up-to-date (sid) . in case of , sorry for the flood . |
What is unstable kernel and unstable ipp-usb? |
@alexpevzner On the present Debian unstable ipp-usb is 0.9.20 and @BELLECalain was using kernel version 5.16.0-6-amd64 when the bug was reported. He also reports that downgrading to ipp-usb 0.9.17 brings back printing and scanning. |
Hi, I've reviewed all changes between
There are literally no other changes between None of these changes look suspicious. Only 6) and 7) are visible from the USB side. If somebody has a problematic device ( |
tried ro compile ipp-usb git version . https://github.com/OpenPrinting/ipp-usb if someone can help me . respecrfully , |
tried the ipp-usb/testing,unstable 0.9.20-1+b1 amd64 do not seems to work any more . in case of , could you explain me the procedure to do the tests ? put again the "debian stable" version |
printer is not recognized in system-config-printer and do not work at all . |
Looks that device hangs during probing for fax at first attempt of the Did you unplug the device between these two attempts? Does the device has faxing facilities? Do you still need the building instructions? |
what i did : by default, I left the debian stable version of ipp-usb in place and froze it (apt-mark hold) then, I compiled the git sources. n.b.: when I copied this I did not touch the printer. i don't know if my printer has fax capabilities . i never used it for that . no , i succeded to compile the git sources . |
Hi @BELLECalain, I have a hypothesis, that problems with your device is caused by attempt to probe faxing facilities. If you have successfully compiled a git version of the Please, add the following lines to the
If it helps, please, let me know: I will add this quirk to the distribution. BTW, does your device actually have a fax unit? |
printer powered on , ipp-usb (debian stable version) frozen :
i launch manually the git version :
system-config-printer do not recognize my printer . |
This is wrong, must be true. Probably, I've guessed device name incorrectly. What |
i noticed that uninstalling ipp-usb also remove the quirks . |
Just run |
updated ipp-usb-quirks in the git repository on my pc .
unfreezing ipp-usb and uninstalling it .
running sudo ./ipp-usb
all worked well . what to do now ? to my side ? and to your side ?
don't know what to do ? |
I think, the simplest way for you will be:
Next release of the |
updated ipp-usb-quirks in the git repository on my pc .
unfreezing ipp-usb and uninstalling it .
running sudo ./ipp-usb
all worked well . what to do now ? to my side ? and to your side ?
don't know what to do ? Install latest "official" ipp-usb (done, version 0.9.20-1+b1 installed) what was the problem ? what was the error ? how did you solve it ? Next release of the ipp-usb will include this quirk. I plan to create this release in few days (waiting for #9 in case it will bring one more useful quirk), and then it will take some time to propagate into the distro you use thanks a lot . friendly , |
Your printer reports, via USB device capabilities, that it has fax unit, but sometimes hangs when I have disabled probing for fax, using the quirk, and the problem dissipated (well, I hope. Actually, we have not tested for enough time to be sure). BTW, does your printer actually have a fax unit? Please use this version for few days. If everything still will be OK, I will consider that the problem is finally solved. |
Does my printer have a fax unit? no, not at all. or else, I don't know where it is. I don't have a fax unit. Anyway, thank you for the support and the troubleshooting. Translated with www.DeepL.com/Translator (free version) n.b.: waiting for the next version of the package . |
To determine whether a printer has a fax unit, check the connectors on the device's back. For fax a phone connector is needed, this is an RJ11 socket, it looks similar to an Ethernet socket but is smaller (6 instead of 8 contacts, often only the center 2 of them actually used). Usually there are 2 such sockets so that in countries where the wall socket for the phone only has a single slot, the phone is connected to the second RJ11 of the fax device. Also in the box you find a phone cable, RJ11 on one end and a phone plug specific to your country on the other end. But it is possible that HP (or perhaps alo other manufacturers) implement a kind of fax-over-internet. Then the device's firmware reports viua DNS-SD and IPP that the device supports fax, and also accepts appropriate jobs. Internally it sends these jobs to a fax service on the internet which passes the fax on into the phone network as needed (like VoIP telephony). So also check the front panel menus of your device, the web admin interface, and also the DNS-SD TXT record which the device reports (use |
first , i ran avahi-discover alone without power on the printer .
|
Thanks. Then it has really no fax ... |
Hi Till, it's the second HP device that claims fax support but have problems in attempt to query its parameters. Previous was |
today , scan test : alain@sid:~$ scanimage -L device `escl:http://localhost:60000' is a HP ENVY 5530 series [FE04D6] (USB) platen scanner device `airscan:e0:HP ENVY 5530 series [FE04D6] (USB)' is a eSCL HP ENVY 5530 series [FE04D6] (USB) ip=127.0.0.1 simple-scan works perfectly . xsane gives images in black and white while it is set in color. i thank you a lot for the solution you gave me . |
If your printer does its job for you, why worry?
Printers of this class rarely survive for more that few years. But I don't see any reasons why not to use it until it appeared to be physically broken |
FIXED |
May I thank @alexpevzner for the professional, competent and successful treatment of the issue in this long thread. Kudos to @BELLECalain for hanging in there. Our printing system would be very much the poorer without the support of maintainer and users. |
Thank you very much, Brian, for your warm words! |
I also want to thank you two, @alexpevzner and @BELLECalain for your patience and effort to hunt down this bug and finally find the solving quirk rule. I have observed the long thread and helped a little bit by fixing the formatting of @BELLECalain's messages (please put a line with only three backticks before and after a block of code lines, to prevent the code from being markdown-formatted). This is the way how reporting, investigating, and solving issues should work. |
FYI, it is fixed in commit 3bcc48c |
Thank you, Till! I've tagged the current version as |
Debian unstable is now updated to ipp-usb 0.9.21 and Ubuntu 22.10 Kinetic Kudu will follow in a few hours via auto-syncing. |
Hi @zdohnal, please, push to Fedora/RHEL too... |
Hi @alexpevzner , on my way, I always try to push the newest versions into Fedora. RHEL/CentOS Stream is a different story, but ipp-usb hasn't been there just yet - unfortunately it won't be there until there is a solution for coexisting with queues created with classic drivers (either by quirks in ipp-usb, driver packages and sane-backends or change of ipp-usb design to don't block the USB port the whole time ipp-usb is running - P.S. I haven't forgot our email communication :) ) while classic drivers are still supported, or there is a migration path for devices which are capable of using ipp-usb but they are now installed with classic driver... |
Hi @zdohnal,
I just wanted to notify you that this newest version already exists :-)
Yes, I understand. BTW, does The more I thinking about this problem, the more I come to conclusion that for the existent users switch from legacy to IPP-USB should be explicit, while for the new users, This problem needs to be solved somehow, because otherwise it creates a bad reputation for the driverless printing among Linux users. Note, there are already a mechanism that prevents CUPS from attempt to use legacy drivers with devices already handled by the |
No problem, thanks for the heads-up :) - I have set upstream release monitoring for I wanted to propose a new thread, but then I've found out you'd already created a one :D - so I'll move there. |
@alexpevzner built and submitted updates for F37, F36, F35 and F34. |
Le 25/04/2022 à 12:44, alain a écrit :
…
Hi , Alexander Pevzner and thanks .
don't understood .
could you explain me what to do , in details ?
or i keep the downgraded package if it is simpliest .
friendly ,
respectfully ,
alain .
Le 25/04/2022 à 12:29, Alexander Pevzner a écrit :
>
> Hi @debiantriage <https://github.com/debiantriage>, nice to hear from
> you and thanks!
>
> libusb_bulk_transfer: Operation timed out
>
> Looks like |libusb| is broken on 5.17.x this kernel (or on this
> distro). It would be nice to retry wth apparmor/selinux disabled
> (depending on a distro).
>
> —
> Reply to this email directly, view it on GitHub
> <#48 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AYTV5L7LLTLOS7TVCWI72DLVGZXXVANCNFSM5S3UXGEQ>.
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
don't know what it means .
the debian bug tracker system told me to post here .
i'm lost
it appears on sid
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008997
https://debian-facile.org/viewtopic.php?id=31739
completely lost . don't know how to solve the problem .
alain@sid:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux bookworm/sid
Release: unstable
Codename: sid
alain@sid:~$ uname -a
Linux sid 5.16.0-6-amd64 #1 SMP PREEMPT Debian 5.16.18-1 (2022-03-29) x86_64 GNU/Linux
alain@sid:~$ apt policy cups ipp-usb hplip
cups:
Installé : 2.4.1op1-2
Candidat : 2.4.1op1-2
Table de version :
*** 2.4.1op1-2 500
100 http://deb.debian.org/debian testing/main amd64 Packages
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
2.3.3op2-3+deb11u1 100
100 http://deb.debian.org/debian stable/main amd64 Packages
ipp-usb:
Installé : 0.9.20-1
Candidat : 0.9.20-1
Table de version :
*** 0.9.20-1 500
100 http://deb.debian.org/debian testing/main amd64 Packages
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
0.9.17-3+b4 100
100 http://deb.debian.org/debian stable/main amd64 Packages
hplip:
Installé : (aucun)
Candidat : 3.22.2+dfsg0-1
Table de version :
3.22.2+dfsg0-1 500
500 http://deb.debian.org/debian unstable/main amd64 Packages
100 /var/lib/dpkg/status
3.21.12+dfsg0-1 100
100 http://deb.debian.org/debian testing/main amd64 Packages
3.21.2+dfsg1-2 100
100 http://deb.debian.org/debian stable/main amd64 Packages
alain@sid:~$ lpstat -t (printer unplugged)
scheduler is running
system default destination: envy
matériel pour envy : ipp://localhost:60000/ipp/print
matériel pour HP-ENVY-5530-series : hp:/usb/ENVY_5530_series?serial=CN595530XD06BX
envy accepte des requêtes depuis mer. 06 avril 2022 11:16:16
HP-ENVY-5530-series accepte des requêtes depuis mar. 05 avril 2022 16:05:38
printer envy is idle. enabled since mer. 06 avril 2022 11:16:16
printer HP-ENVY-5530-series disabled since mar. 05 avril 2022 16:05:38 -
File "/usr/lib/cups/filter/hpcups" not available: No such file or directory
alain@sid:~$ scanimage -L (printer plugged and on)
device `hpaio:/usb/ENVY_5530_series?serial=CN595530XD06BX' is a Hewlett-Packard ENVY_5530_series all-in-one
The text was updated successfully, but these errors were encountered: