Burn with different MD5 checksum

Bug #783767 reported by Cristiano Fraga G. Nunes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: brasero

When burn an image to DVD, and check this DVD checksum, the value has different.
Example: I trying burn ubuntu-11.04-desktop-i386.iso with MD5: 8b1085bed498b82ef1485ef19074c281

After read the iso of DVD, the MD5 is: 86c79bdf953b4795f57e3571d85a39ff

I'm have tested many times with various medias, and has same issue.

Revision history for this message
Cristiano Fraga G. Nunes (cfgnunes) wrote :

 The burners burn in blocks of 32kB each.
When iso's are not exact multiples of 32kB they pad the iso's with 0's when they write them.
The burning software calculates the MD5 checksum on the original, unpadded iso image
The MD5 sum calculated after burning includes the padded zeros and will not match the original MD5 sum calculated on the iso if the size of the original iso was not a multiple of 32kB.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Are you getting the same with k3b ? brasero is just using a helper that createst the md5 filesum

Changed in brasero (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.