Missing "verify data after burning" functionality.

Bug #72217 reported by David Planella
4
Affects Status Importance Assigned to Milestone
GnomeBaker
Unknown
Unknown
gnomebaker (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

Currently, there is no way to tell from the GUI whether the data on a CD or DVD was burned correctly, and therefore external tools have to be used to perform the verification.

Many users do not know the existance or simply do not have the skills to execute this external tools.

Verification of the written data is a very basic functionality which IMHO oppinion every burning application should implement.

This leads to a very odd situation I've observed: many GNOME users have a "clean" GNOME desktop with no other kde applications than k3b, although GnomeBaker is great, stable and the default GNOME CD-burning application. The point is, many of these users use k3b for the *sole* reason that k3b *can* do data verification after burning and GnomeBaker cannot.

Note that I'm not claiming this to be based on statistical information. This is just a subjective observation.

Many thanks.

Revision history for this message
Neilen Marais (neilenmarais) wrote :

Lack of verify is pretty much a deal breaker to me. It's a pity since gnomebaker seems like a very clean and well designed app.

Changed in gnomebaker:
importance: Undecided → Wishlist
status: Unconfirmed → Confirmed
Revision history for this message
Mantas Kriaučiūnas (mantas) wrote :

It seems developing of gnomebaker is pretty slow, so, I can recommend Brasero CD burning tool (http://sourceforge.net/projects/bonfire/ ), which already has verification after burn, good multisession support and other goodies ;)

Revision history for this message
Mario Đanić (mario-danic) wrote :

Indeed this is a very useful feature. If you can provide a patch, I will be most glad to apply it.

Revision history for this message
Hugo Lía (hugolia) wrote :

Is development of GnomeBaker still active? I wonder how this simple change of adding a verification check is not yet implemented.
This bug report is four years old and we are still waiting some patch, correction or implemention.
Is there any plan to implement it?

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.