Bug 1389006

Summary: hplip-3.16.9-plugin.run file does not match its checksum
Product: [Fedora] Fedora Reporter: Edouard Duliège <edouard>
Component: hplipAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: edouard, jpopelka, mmc, twaugh, udayreddy, zdohnal
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 13:10:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Edouard Duliège 2016-10-26 16:20:32 UTC 
Description of problem:
I run hp-setup or hp-plugin. I get the following error message when the machine want to download a plugin: .hplip/hplip-3.16.9-plugin.run file does not match its checksum


Version:
3.16.9

How reproducible:
everytime

Steps to Reproduce:
1. run hp-plugin
2. get this error message

Actual results:
hp-plugin crashes

Expected results:
hp-plugin downloads the plugin

Additional info:
rolling back to 3.16.5 is a workaround.
Comment 1 Zdenek Dohnal 2016-11-02 12:25:47 UTC 
*** Bug 1390917 has been marked as a duplicate of this bug. ***
Comment 2 Zdenek Dohnal 2016-11-02 12:28:39 UTC 
Hi Edouard,

thank you for contacting us. Would you mind upgrading to the newest hplip version, if issue will disappear?
Comment 3 Zdenek Dohnal 2016-11-02 12:37:21 UTC 
Upstream launchpad case, which I think is relevant:

https://bugs.launchpad.net/hplip/+bug/1624950
Comment 4 Edouard Duliège 2016-11-02 21:04:25 UTC 
Hi Zdenek,

The issue has disappeard after upgrading to  hplip 3.16.10-1, thank you very much!
Comment 5 Zdenek Dohnal 2016-11-04 13:10:09 UTC 
No problem, Edouard.
Comment 6 udayb 2016-11-05 12:34:50 UTC 
hplip 3.16.9-1 was the latest version available when I reported the bug (a duplicate of this). I works now with 3.16.10-1.