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 603605 - .checksum.md5 ("file integrity check" plugin) broken when using "Increase compatibility with Windows"
.checksum.md5 ("file integrity check" plugin) broken when using "Increase com...
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
2.28.x
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-12-02 14:20 UTC by Pedro Villavicencio
Modified: 2009-12-04 19:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-12-02 14:20:29 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/486438

"
I burn MP3-files. To use the CD/DVD also with MS-Windows I use the option "Increase compatibility with Windows". Brasero cuts the length of every filename to 64 characters correctly.
Addionally I use the plugin "file integrity check" and brasero creates the hidden file .checksum.md5 on the CD/DVD. But the integrity check stops with an error because Brasero ist not able to find the some files.
What I saw is that Brasero saves the original long (!) filenames (> 64 char.) in the .checksum.md5-file but on the CD/DVD there are of course only the short filenames (< 64 char.) available.
To work fine Brasero should save the short (!) filenames (< 64 char.) in .checksum.md5. In other words: For a working "file integrity check" the filenames on the CD/DVD must be the same as in the .checksum.md5-file."

"I tested a little bit and found out:

1) When you only burn one single file, the "file integrity check" always works fine (even if you use the option "Increase compatibility with Windows" and Brasero cuts the filename to less than 64 characters).

2) When you burn two ore more files and - using the option "Increase compatibility with Windows" - brasero cuts the filename of one or more files to less than 64 characters, the "file integrity check" always stops with an error as described in the Bug Description above.

Here is an example:

I burn these two files with the option "Increase compatibility with Windows". The original filenames are:
01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3
02_-_This_is_a_test_file.mp3

On the CD/DVD the filenames are:
01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check.mp3
02_-_This_is_a_test_file.mp3

As you can see, Brasero cuts the filename of the first file correctly after 64 characters.

The entries in the .checksum.md5 are:
51a31a66cc5eb5110f5bdf41aab0dd87 02_-_This_is_a_test_file.mp3
51a31a66cc5eb5110f5bdf41aab0dd87 01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3

The last rows in the log file say:
BraseroChecksumFiles Getting file /02_-_This_is_a_test_file.mp3
BraseroChecksumFiles comparing checksums for file /02_-_This_is_a_test_file.mp3 : 51a31a66cc5eb5110f5bdf41aab0dd87 (from md5 file) / 51a31a66cc5eb5110f5bdf41aab0dd87 (current)
BraseroChecksumFiles Getting file /01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3
BraseroChecksumFiles Ended with an error
BraseroChecksumFiles called brasero_job_error
BraseroChecksumFiles finished with an error
BraseroChecksumFiles asked to stop because of an error
 error = 1
 message = "Datei »/01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3« kann nicht geöffnet werden"
BraseroChecksumFiles stopping
Session error : Datei »/01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3« kann nicht geöffnet werden (brasero_burn_record brasero-burn.c:2808)

As you can see, the "file integrity check" is searching the file 01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3 but doesn't find it because the filename on the CD/DVD is only 01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check.mp3.

I also made a screenshot of the error-message but it's in german (see attachment). I try to translate:
"The file integrity check can not be carried out. File "01_-_This_is_a_test_file_to_look_if_brasero_is_able_to_check_the_file_integrity_of_filenames_with_less_than_64_characters.mp3" can not be opend".

I hope this example will help to find the bug."
Comment 1 Philippe Rouquier 2009-12-04 19:38:42 UTC
Thanks for the report. The diagnosis was excellent. I fixed it in master and will backport it to 2.28 branch soon. Thanks again for researching the origin of the bug.