Claim that hash of incoming file is wrong
Submitted by Guillaume Desmottes
Link to original bug (#663150)
Description
I received a 6.2M file and Empathy claims that its hash were wrong:
hash_job_done: Hash mismatch when checking incoming handler: received bb864735b969ca991ffcf995c9d2dfe3, calculated 48b55e389bd5cd8d3b89024ea413246f
but manually hashing the file gives us the right hash: $ md5sum /tmp/vg.out bb864735b969ca991ffcf995c9d2dfe3 /tmp/vg.out
So I guess there is a bug somewhere in our hashing code.
Version: 2.33.x