Description of problem: Can't download and install HP printer plugin. Version-Release number of selected component (if applicable): hplip-3.17.9-1.fc26.x86_64 How reproducible: Always Steps to Reproduce: 1. Run hp-plugin and follow prompts to download and install Actual results: Checking for network connection... Downloading plug-in from: Plugin is not accessible. Trying to download it from fallback location: [http://hplipopensource.com/hplip-web/plugin/hplip-3.17.9-plugin.run] error: /home/uday/.hplip/hplip-3.17.9-plugin.run file does not match its checksum. File may have been corrupted or altered Expected results: Should have downloaded and installed it. Additional info:
Hi, thank you reporting this issue - seems like HP changed web site, but their developers didn't change url in source files. And I cannot find new plugin on their new website, so I could change url in code to new one.
Reported upstream: https://bugs.launchpad.net/hplip/+bug/1727628
> so I could change url in code to new one. Sorry, mistake, I cannot change url in code to new one.
Hm, seems they again uploaded plugins on openprinting.org website - Nineth, hplip-3.17.10, which is in updates-testing, should work. Would you mind updating to 3.17.10 then?
Updated to 3.17.10, but the same problem exists. The URL might still be the old one. Checking for network connection... Downloading plug-in from: Plugin is not accessible. Trying to download it from fallback location: [http://hplipopensource.com/hplip-web/plugin/hplip-3.17.9-plugin.run] error: /home/uday/.hplip/hplip-3.17.9-plugin.run file does not match its checksum. File may have been corrupted or altered Done
Just noticed the following (that hp-plugin from 3.7.10 still reports the old version): rpm -qf `which hp-plugin` hplip-3.17.10-1.fc26.x86_64 [uday@ukr ~/Downloads]₹ hp-plugin HP Linux Imaging and Printing System (ver. 3.17.9) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. HP Linux Imaging and Printing System (ver. 3.17.9) Plugin Download and Install Utility ver. 2.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details.
I uninstalled and reinstalled 3.7.10 (from updates-testing) and it works. (I somehow still was running the old hp-plugin).
That's interesting - did you updated all hplip packages (hplip, hplip-common, hplip-gui, hplip-libs, libsane-hpaio) or only some of them in comment#5? And which packages got uninstalled and installed in comment#7? You can find it out by these commands: $ sudo dnf history list - you gain number of dnf transaction, when packages got installed/uninstalled etc. $ sudo dnf history undo NUMBER - dnf will try to revert selected transaction, then we will know which packages were in transaction, you can cancel the action after that.
hplip-3.17.10-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-da1e383f18
(In reply to Zdenek Dohnal from comment #8) > That's interesting - did you updated all hplip packages (hplip, > hplip-common, hplip-gui, hplip-libs, libsane-hpaio) or only some of them in > comment#5? I had only updated hplip (since I saw that hp-plugin came from that). I notice this was the cause (as the actual driver behind hp-plugin wasn't updated). > And which packages got uninstalled and installed in comment#7? hplip, hplip-common, hplip-libs This makes it clearer, thanks.
So you went to koji and installed hplip package by sending link to dnf? Because when I use after enabling updates-testing repository: $ sudo dnf -y update hplip dnf updates all hplip subpackages.
(In reply to Zdenek Dohnal from comment #12) > So you went to koji and installed hplip package by sending link to dnf? Right. I should've mentioned that. I actually had installed it from the hplip's sourceforge (via run file). And so dnf update didn't update everything. > Because when I use after enabling updates-testing repository: > > $ sudo dnf -y update hplip > > dnf updates all hplip subpackages.
(In reply to Nineth from comment #13) > (In reply to Zdenek Dohnal from comment #12) > > So you went to koji and installed hplip package by sending link to dnf? > > Right. I should've mentioned that. I actually had installed it from the > hplip's sourceforge (via run file). And so dnf update didn't update And the reason I did that was because I wanted to check if the upstream was free of that issue (since this leads to a non-working printer and an immediate fix was needed).
I understand. If I can give a advice, always use dnf and packages in repos (you can even check bodhi.fedoraproject.org, if there is any pending update for package, which you seek), because of (at least) 2 reasons: 1. installing software by .run files or my any other means (like ./configure, make, make install) creates files, which aren't tracked by any means and they aren't replace/removed by any dnf action - it only leaves garbage in your OS and creates unexpected behavior (like you experienced) 2. Fedora maintainers aren't responsible for fixing errors, when user installed packages from other source than official Fedora repos. So when you install package/software from other sources, you're on your own.
(In reply to Zdenek Dohnal from comment #15) > I understand. If I can give a advice, always use dnf and packages in repos > (you can even check bodhi.fedoraproject.org, if there is any pending update > for package, which you seek), because of (at least) 2 reasons: > > 1. installing software by .run files or my any other means (like > ./configure, make, make install) creates files, which aren't tracked by any > means and they aren't replace/removed by any dnf action - it only leaves > garbage in your OS and creates unexpected behavior (like you experienced) > > 2. Fedora maintainers aren't responsible for fixing errors, when user > installed packages from other source than official Fedora repos. So when you > install package/software from other sources, you're on your own. I understand. But as I mentioned, the only reasoned I installed that was because the one in Fedora's repo was broken. This was critical enough for me to not wait till it was resolved.
hplip-3.17.10-1.fc26 has been pushed to the Fedora 26 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-2017-da1e383f18
I understand. Then if you have fully updated system, you can check bodhi.fedoraproject.org (everything, which is in 'testing' phase on that page, is accessible from updates-testing repository) next time, if there aren't any updates for component which you seek. Or you can check even koji.fedoraproject.org, where you can find all package builds - you can install them by dnf and using link to each rpm. There you can find packages, which aren't even in updates-testing repository, if you really want to try, if the newest build solves it.
(In reply to Zdenek Dohnal from comment #18) > I understand. Then if you have fully updated system, you can check > bodhi.fedoraproject.org (everything, which is in 'testing' phase on that > page, is accessible from updates-testing repository) next time, if there > aren't any updates for component which you seek. > Or you can check even koji.fedoraproject.org, where you can find all package > builds - you can install them by dnf and using link to each rpm. There you > can find packages, which aren't even in updates-testing repository, if you > really want to try, if the newest build solves it. Thanks - this is useful to know!
add external tracker information mentioned in mailing list post
hplip-3.17.10-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.