DVD created "successfully", but files unusable

[Scott Cowles Jacobs]

Binary package hint: brasero

I have twice tried to back up some files/folders with Brasero (Brasero 2.32.0). Once by bringing Brasero up from the Menu, and once by selecting "Open with CD/DVD Creator" from the pop-up window created when the disk was inserted.
Both times it seemed to work.
However, when I checked the files (for instance, double clicking on a photo to bring up the Image Viewer (thumbnails were all the generic JPG symbol instead of miniature pictures (a bad initial sign...)), a word processor file to bring up OpenOffice 3.2, or a .pdf. file to bring up the Document Viewer), the action was unsuccessful - either the program said that something was wrong with the file and it could not load it, or the file seemed to be gibberish.
I have no idea what the problem is, and Brasero seems not to know anything is wrong. Does it not compare the original files with the burned final product to see if it was correctly done?
On the off chance that my disk burner was at fault, I installed a different burner (GnomeBaker (GnomeBaker 0.6.4)), and had success - all checked files were fine.
The disks are unlikely to be at fault - they are Taiyo-Yuden/JVC disks.

scott@scott-Dimension-8200:~$ uname -a
Linux scott-Dimension-8200 2.6.35-28-generic #49-Ubuntu SMP Tue Mar 1 14:40:58 UTC 2011 i686 GNU/Linux
scott@scott-Dimension-8200:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10

The following seems obvious, but...

3) What you expected to happen
Files on created disk that identically matched the original files.

4) What happened instead
Files on created disk were unusable.

I have a Dell computer (model as seen above in the uname command) with 2GB, 1.7 Ghz, with a replaced DVD-burner from 3+years past. I had specified Maximum or 8x burn, but the burns (with Brasero and with GnomeBaker) seemed to hover around 4x, so that may be the drive max (NO - it's an 8x max - the disks are 16x DVD-R's)

[Scott Cowles Jacobs (scott092707)]

I was not thinking as clearly as I might have yesterday.

It has since occurred to me (why not earlier?) that perhaps it would be useful for you to actually SEE some sample files that were created on the disk, so that you could actually SEE what was produced, and thereby determine what is actually WRONG with them. (i.e.: "DUH!")

So, I will attempt to attach a representative file from each of the types of files that I was attempting to back up.

(If I remember this process correctly, after the fact one can only attach a single file per attempt, so I may have to do this multiple times... I will not likely add a comment for each one...)

[Scott Cowles Jacobs (scott092707)]

I might have thought that by now, someone would have said something.
After all, if a program that is normally used to back up data, is doing so
incorrectly (sometimes?), such that the data "backed-up" is unusable, one would think
that there exists a rather serious bug in it...

One concludes:

1) for some reason, this bug report is not reaching anyone.
2) it has already been fixed, so does not need to be fixed (and no one is bothering to say so).
3) Brasero will not be continued as a project (?), for some reason, and so if it has a bug, no one cares.
4) ?

Anyone?

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Pedro Villavicencio (pedro)]

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!