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 149473 - Please add "verify image after burn" option
Please add "verify image after burn" option
Status: RESOLVED DUPLICATE of bug 125470
Product: nautilus-cd-burner
Classification: Deprecated
Component: cd-burner
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus CD Burner Maintainers
Nautilus CD Burner Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-06 08:00 UTC by Gregory Kovriga
Modified: 2007-11-05 13:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6


Description Gregory Kovriga 2004-08-06 08:00:30 UTC 
Some speeds / media can eventually produce a damaged CD image.
Having an option to verify the image after burning would be very helpful.
Comment 1 André Dahlqvist 2004-08-07 19:17:54 UTC 
This is a duplicate of bug 125470.
Comment 2 Bastien Nocera 2004-08-21 18:12:37 UTC 

*** This bug has been marked as a duplicate of 125470 ***
Comment 3 Johan Walles 2007-11-05 13:11:31 UTC 
This bug is not a duplicate of bug 125470 (which is about adding MD5 files to the disk and some other things).

Somebody authorized, please remove the bogus DUPLICATE designation.
Comment 4 Johan Walles 2007-11-05 13:16:32 UTC 
BTW, as somebody suggested in one of the dups of this one, verifying the write should be the default behavior.

With fast writers (8x) and even faster readers, verification doesn't take that long.
Comment 5 Johan Walles 2007-11-05 13:49:26 UTC 
Also, I question the "enhancement" severity of this bug.

Since not verifying the disks makes people write broken CDs / DVDs without any warning, we currently have a problem with data loss.

According to "http://bugzilla.gnome.org/page.cgi?id=bug-status.html#bug_severity" this implies severity Critical: "Crashes, causes loss of data, or is a severe memory leak."

Somebody authorized, please modify the priority accordingly.