After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636658 - The brasero md5 checksum plugin does not work well.
The brasero md5 checksum plugin does not work well.
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-12-07 01:15 UTC by dE
Modified: 2018-09-21 17:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description dE 2010-12-07 01:15:18 UTC 
All the time it states that the burn process was not successful... some of the hash did not verify.

I did a manual hash check of all the files and it appeared to be all right.
Comment 1 Frank Griffin 2011-07-29 16:56:18 UTC 
I confirm.  For a more detailed bug report, see https://bugs.mageia.org/show_bug.cgi?id=2329

In that case, brasero reports a mismatch in spite of the fact that a "cmp -l xxx.iso /dev/sr0' comparing the raw burned data to the original ISO on the hard drive finds them equal.
Comment 2 Frank Griffin 2011-07-29 16:57:51 UTC 
The version I'm using is the Mageia 3.0.x version.
Comment 3 Frank Griffin 2012-09-20 14:27:39 UTC 
This is a fairly serious bug that is still occurring and has been open for going on two years now.  Google finds several references to the nature of the problem, something about computing the checksum by reading a multiple of 32 blocks back from the burned disk rather than the exact number written.

Is this ever going to be addressed ?
Comment 4 GNOME Infrastructure Team 2018-09-21 17:11:11 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/150.