Hello, It seems that configuring an HP printer using hplip when this printer need the proprietary plugin not working due to a failling download of the hplip-3.20-11-plugin.run (wrong checksum). error message is "hplip-3.20.11-plugin.run file does not match its checksum" It seems that the issue comes from the fact that hp-plugin tool try to download the hplip-3.20-11-plugin.run from the openprinting site but failed because the checksum of the downloaded file is different from the one in the http://hplip.sf.net/plugin.conf. When trying to install the 3.21.2 which is present in the cauldron repository, i can't see this kind of error message. Note: i can't test as i don't have an HP printer ( and not one that need the installation of the plugin).
CC: (none) => doktor5000
(In reply to Nicolas Nicolas from comment #0) > Hello, > > Note: i can't test as i don't have an HP printer (and not one that need the > installation of the plugin). Why reporting then? ;) Joke aside, > It seems that configuring an HP printer using hplip when this printer need > the proprietary plugin not working due to a failing download of the > hplip-3.20-11-plugin.run (wrong checksum). > > error message is "hplip-3.20.11-plugin.run file does not match its checksum" > > It seems that the issue comes from the fact that hp-plugin tool try to > download the hplip-3.20-11-plugin.run from the openprinting site but failed > because the checksum of the downloaded file is different from the one in the > http://hplip.sf.net/plugin.conf. > > When trying to install the 3.21.2 which is present in the cauldron > repository, i can't see this kind of error message. This is an update request for hplip package. Cauldron package seems not affected by this kind of complains. Assigning globally as no registered maintainer. CC'd David G who did lastly the excellent job.
Summary: Configuring HP printer which need proprietary plugin using hplip is failling => Update request for hplip that will help installing upstream proprietary plugins for some HP printersCC: (none) => geiger.david68210, ouaurelienSource RPM: hplip-3.20.11-1.mga8.x86_64 => hplip-3.20.11-1.mga8.src.rpmAssignee: bugsquad => pkg-bugsStatus comment: (none) => hplip-3.21.3 from Cauldron seems not affected.
Please test hplip-3.21.2-1.mga8 in Core/Updates_testing repo!
Hello, The two reported cases on the mlo forum seems to have been solved after applying the testing package. https://www.mageialinux-online.org/forum/topic-28564+imprimante-et-scanner-hp.php https://www.mageialinux-online.org/forum/topic-28553-1+probleme-hplip-plugin.php As i can't test, probably the issue is fixed by this package.
Assigning to QA now, Advisory: ======================== Our current hplip package has some issue with proprietary plugins for some HP printers. It can't download and install the appropriate plugin.run file due to a wrong checksum, we can see an error message: "hplip-3.20.11-plugin.run file does not match its checksum" So this update fixes this issue. ======================== Packages in 8/core/updates_testing: ======================== hplip-model-data-3.21.2-1.mga8.i586.rpm hplip-doc-3.21.2-1.mga8.i586.rpm libhpip0-3.21.2-1.mga8.i586.rpm hplip-hpijs-3.21.2-1.mga8.i586.rpm libhpip0-devel-3.21.2-1.mga8.i586.rpm libsane-hpaio1-3.21.2-1.mga8.i586.rpm hplip-gui-3.21.2-1.mga8.i586.rpm hplip-3.21.2-1.mga8.i586.rpm hplip-hpijs-ppds-3.21.2-1.mga8.i586.rpm hplip-model-data-3.21.2-1.mga8.x86_64.rpm hplip-doc-3.21.2-1.mga8.x86_64.rpm lib64hpip0-3.21.2-1.mga8.x86_64.rpm hplip-hpijs-3.21.2-1.mga8.x86_64.rpm lib64hpip0-devel-3.21.2-1.mga8.x86_64.rpm lib64sane-hpaio1-3.21.2-1.mga8.x86_64.rpm hplip-gui-3.21.2-1.mga8.x86_64.rpm hplip-3.21.2-1.mga8.x86_64.rpm hplip-hpijs-ppds-3.21.2-1.mga8.x86_64.rpm Source RPM: ======================== hplip-3.21.2-1.mga8.src.rpm
Assignee: pkg-bugs => qa-bugsStatus comment: hplip-3.21.3 from Cauldron seems not affected. => hplip-3.21.2 from Cauldron seems not affected.
I have one of the printers that requires the plugin - a Color Laserjet CP1215. However, it is functioning just fine with Mageia 8. This system was an upgrade install from an MGA7 Plasma system. The printer had originally been installed through system-config-printer over a year ago. It has been through an hplip update or two under MGA7, and of course the upgrade to MGA8, with no error messages coming to my attention. I can only assume that since the system working it is somehow currently using an old plugin. Please advise how I can determine which version of the plugin I currently have. Also please advise on the best procedure to use for testing this update. Will a simple update do the job? Do I need to remove the printer, install the update, then re-install the printer? Do I need to use hp-setup to re-install the printer, or system-config-printer?
CC: (none) => andrewsfarmKeywords: (none) => feedback
Never mind. I have reasoned this out for myself.
Keywords: feedback => (none)
Ran hp-plugin manually from the command line, which resulted in the checksum error. (I must assume that my printer was working because system-config-printer/hp-setup found an existing local version of the plugin and used that.) The following 8 packages are going to be installed: - hplip-3.21.2-1.mga8.x86_64 - hplip-doc-3.21.2-1.mga8.x86_64 - hplip-gui-3.21.2-1.mga8.x86_64 - hplip-hpijs-3.21.2-1.mga8.x86_64 - hplip-hpijs-ppds-3.21.2-1.mga8.x86_64 - hplip-model-data-3.21.2-1.mga8.x86_64 - lib64hpip0-3.21.2-1.mga8.x86_64 - lib64sane-hpaio1-3.21.2-1.mga8.x86_64 No installation issues. Ran hp-plugin again, this time with a successful download and install of the latest plugin. Tried printing a monochrome text file from kwrite and a color photo from Gwenview, with no issues. It surprises me that an update of hplip doesn't automatically download and install the latest plugin for any installed printer that may need it, but apparently that is expected behavior. I shall have to remember that for the future. Validating. Advisory in Comment 4.
Whiteboard: (none) => MGA8-64-OKKeywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0043.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED