Description of problem: When burning a DVD image, k3b claimed the written data would differ. This is very irritating for users (adding more confusion to the unreliable CD and DVD burning process). The written data does not differ, but K3B seems to write in 32KB blocks; when the ISO image is not on a 32KB boundary it is filled up with NULLs. Technicalls the Image is different, but K3B should take this into account and not complain. How reproducible: always Steps to Reproduce: Write a dvd image, as one from - http://10.65.7.1/sysreports/495233/1798266/SUN_Ultra24_Supplemental_1.1_Bios_1.10_tools_and_drivers.iso $ ls -sk SUN_Ultra24_Supplemental_1.1_Bios_1.10_tools_and_drivers.iso 1168952 SUN_Ultra24_Supplemental_1.1_Bios_1.10_tools_and_drivers.iso Actual results: k3b complains that md5sum has failed Expected results: md5sum is correct, as shown in RHEL5. Additional info: probably upstream bug - http://bugs.kde.org/show_bug.cgi?id=98385 suspected fixes - http://websvn.kde.org/branches/k3b/0.11/kdeextragear-1/k3b/src/tools/k3bmd5job.cpp?diff_format=l&view=log#rev380065 SEG Notes: This appears to be a bug that occurs on x86_64 systems. I couldn't reproduce the bug on x86 and since I haven't got a DVD burner on my x86_64 box I haven't got any way of checking to see if the patch has introduced any regressions. It doesn't seem to have any impact on my x86 system so I'll pass the patch up to engineering.
Created attachment 312146 [details] md5sum.patch
Created attachment 312147 [details] sysreport-root.evebe625_21jan2008.tar.bz2
Patch reviewed and works.
*** Bug 412031 has been marked as a duplicate of this bug. ***
*** Bug 469084 has been marked as a duplicate of this bug. ***
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0958.html