Description of problem: Version-Release number of selected component (if applicable): hplip-3.19.6-3.fc30.x86_64 How reproducible: Always Steps to Reproduce: (Printer and Scanner detected previously) 1. Update hplip to hplip-3.19.6-3.fc30.x86_64 2. Try "Simple Scan", no scanner found. 3. Running "hp-toolbox" and "Setup Device" does not detect any devices. Actual results: No devices detected or seen in current configuration. Expected results: Devices already detected previously should work, or should be detected. Additional info: Downgrading to hplip-3.18.12-9.fc30 resovled the issue for me.
Somehow forgot to add the printer model: "HP LaserJet 100 color MFP M175nw" on LAN (wired).
Tested hplip-3.19.6-5 -- no change: Aug 12 13:12:01 /hp-setup[6942]: hp-setup[6942]: error: No devices found on bus: net Aug 12 13:12:01 /hp-setup[6942]: hp-setup[6942]: error: HPLIP cannot detect printers in your network. This may be due to existing firewall settings blocking the required ports. When you are in a trusted network environment, you may open the ports for network services like mdns and slp in the firewall. For detailed steps follow the link. http://hplipopensource.com/node/374 "libsane-hpaio" is installed and is matching version.
Hi Stepan, thank you for reporting the issue! Would you mind checking: 1) If the printer is turned on? 2) If you can ping the printer? 3) Is the printer in the same network as PC? 4) can you see the printer in available printers when you list printers by: $ sudo lpinfo -l -v There are several updates which went into Fedora 30 before your reported version: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1fec7afaf https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d2b365378 https://bodhi.fedoraproject.org/updates/FEDORA-2019-db5ea959c9 Would you mind testing them and narrowing the range where the problem appeared?
Hello Zdenek, Thank you for your quick response! The printer/scanner breaks using hplip-3.19.6-1 (not working), working using hplip-3.18.12-13 (last working). 1) If the printer is turned on? Yes. Turned on, plugged-in, rebooted. 2) If you can ping the printer? Yes. Available over SNMP too: $ snmpwalk -Os -c public -v 1 <ip.ad.dre.ss> .1.3.6.1.4.1.11.2.3.9.1.1.7.0 enterprises.11.2.3.9.1.1.7.0 = STRING: "MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,URP,PCL,PDF,POSTSCRIPT;MDL:HP LaserJet 100 colorMFP M175nw;CLS:PRINTER;DES:Hewlett-Packard LaserJet 100 colorMFP M175nw;MEM:MEM=110MB;COMMENT:RES=600x8;LEDMDIS:USB#ff#04#01;" 3) Is the printer in the same network as PC? Yes, the very same network segment. No routers. 4) can you see the printer in available printers when you list printers by: $ sudo lpinfo -l -v Yes, several instances (using hplip 3.19.6-1, broken state): Device: uri = dnssd://HP%20LaserJet%20100%20colorMFP%20M175nw%20(60177E)._ipp._tcp.local/?uuid=<uuid_of_the_printer> class = network info = HP LaserJet 100 colorMFP M175nw (60177E) make-and-model = HP LaserJet 100 colorMFP M175nw device-id = MFG:HP;MDL:LaserJet 100 colorMFP M175nw;CMD:PDF,PS,PCL,URF; location = Device: uri = socket://<ip.ad.dre.ss> class = network info = HP LaserJet 100 colorMFP M175nw make-and-model = HP LaserJet 100 colorMFP M175nw device-id = MFG:Hewlett-Packard;CMD:PJL,PML,PCLXL,URP,PCL,PDF,POSTSCRIPT;MDL:HP LaserJet 100 colorMFP M175nw;CLS:PRINTER;DES:Hewlett-Packard LaserJet 100 colorMFP M175nw;MEM:MEM=110MB;COMMENT:RES=600x8;LEDMDIS:USB#ff#04#01; location = Device: uri = ipp://NPI60177E.local:631/ipp/printer class = network info = HP LaserJet 100 colorMFP M175nw (driverless) make-and-model = HP LaserJet 100 colorMFP M175nw device-id = MFG:HP;MDL:LaserJet 100 colorMFP M175nw;CMD:PDF,PS,PCL,AppleRaster,URF; location = Interesting parts of $ sudo hp-check -t (using 3.19.6-1): ------------------------------ | DISCOVERED SCANNER DEVICES | ------------------------------ device `v4l:/dev/video0' is a Noname Integrated Camera: Integrated C virtual device ... --------------------------------- | INSTALLED CUPS PRINTER QUEUES | --------------------------------- HP_LaserJet_100_colorMFP_M175nw ------------------------------- Type: Printer Device URI: hp:/net/HP_LaserJet_100_colorMFP_M175nw?ip=<ip.ad.dre.ss> PPD: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw.ppd PPD Description: HP LaserJet 100 color MFP M175 Postscript (recommended) Printer status: printer HP_LaserJet_100_colorMFP_M175nw is idle. enabled since Thu Aug 24 12:29:31 2017 error: Unsupported model: HP_LaserJet_100_colorMFP_M175nw error: Communication status: Failed LaserJet-100-colorMFP-M175nw ---------------------------- Type: Unknown Device URI: dnssd://HP%20LaserJet%20100%20colorMFP%20M175nw%20(60177E)._ipp._tcp.local/?uuid=<uuid_of_the_printer> PPD: /etc/cups/ppd/LaserJet-100-colorMFP-M175nw.ppd PPD Description: HP LaserJet 100 color MFP M175 Postscript (recommended) Printer status: printer LaserJet-100-colorMFP-M175nw is idle. enabled since Sun Jul 21 14:16:17 2019 warning: Printer is not HPLIP installed. Printers must use the hp: or hpfax: CUPS backend for HP-Devices. The scanner is detected and printer reported OK using 3.18.12-13.
Ok, there are two other commits which can break things, but they were not in individual updates: Would you mind trying: 1) 3.18.12-15 https://koji.fedoraproject.org/koji/taskinfo?taskID=36958069 2) 3.18.12-16 https://koji.fedoraproject.org/koji/taskinfo?taskID=36958245
Tested 3.18.12-15 and 3.18.12-16, both working fine.
Hi Stepan, Hi Bruce, sorry for the delay, I had other urgent issues to solve and new hplip raised several similar issues. To sum it up: HP upstream removed entry for HP_LaserJet_100_colorMFP_M175nw in hplip-3.19.1 from models.dat, which caused not-detecting the printer. M175nw discovery and installation is based on ppd-name keyword in M175nw section in models.dat - when the section got renamed, the ppd is no longer found. I'll revert the changes and report it upstream.
(In reply to Zdenek Dohnal from comment #7) > Hi Bruce, > Sorry, copying is bad habit :) .
Hi Stepan, would you mind trying these rpms from following link https://koji.fedoraproject.org/koji/taskinfo?taskID=37605780 ? I reverted upstream changes, so the printer should be discovered and work.
Hi Zdenek, I've tested out these rpms and the printer/scanner worked fine (required a plugin update). Device detected without issues, test page printed out and also scanned fine. Thank you! Stepan
FEDORA-2019-1b1ad80551 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1b1ad80551
hplip-3.19.6-9.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1b1ad80551
hplip-3.19.6-9.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.