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 577483 - brasero burnproof greyed out even when drive supports it
brasero burnproof greyed out even when drive supports it
Status: RESOLVED NOTABUG
Product: brasero
Classification: Applications
Component: general
2.26.0
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-03-31 15:35 UTC by Pedro Villavicencio
Modified: 2009-05-11 09:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Pedro Villavicencio 2009-03-31 15:35:38 UTC
this report has been filed here:

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

"For some reason Brasero greys out the option for burnproof, making in unselectable, even when the drive supports that feature."

"
The device in question is Lite-On LH-20A1S. It works with 'burnproof' on the commercial Nero software.

http://www.liteonit.com/global/index.php?option=com_content&task=view&id=199&Itemid=67
"

"Nero Linux appears to call the feature 'smart-burn' like the documentation for the Lite-On drive. It's essentially all the same feature from the end user perspective though."

"
The feature apparently goes by various names depending on the manufacturer:

JustLink, ExacLink, Seamless Link, BURN-Proof, Smart-Burn, Power Burn, Safe Burn."

"

This page briefly describes some of the types of burn protection. It sounds like this may be a per vendor extension, so it may be that only some of the extensions are implemented in Brasero.

http://www.burnworld.com/cdr/hardware/bu.htm"

brasero log:

http://launchpadlibrarian.net/24543744/brasero-debug.txt

thanks in advance,
Comment 1 Philippe Rouquier 2009-05-11 09:54:05 UTC
Thanks for the report.

I'm afraid this is not a bug: MMC standards only define burnproof (or related technologies) for CDs and DVDs-R. For the other types of media, the way they are written (overwrite, more or less like a hard drive) means that they don't need such a thing as burnproof or related technologies. This process is safe in itself and won't (shouldn't??) fail.

That's why I chose to leave the checkbox greyed out when burning to these media.
I knew this would confuse the users and probably scare them but I didn't know how to do it otherwise (maybe remove it?).

I checked the log you sent me and the user was having a DVD+R inserted it seems, that's why he didn't have burnproof.

On the other hand, if a user has a CD/DVD-Rw inserted and if burnproof isn't available then, that will be a bug indeed. You can tell your users to try with a CD or a DVD-R.

If you come up with another idea or if this happens with CDs and DVD-Rw, please reopen the bug and let me know.

Just a quick note, the command line arguments have changed slightly. Please ask your user to add "--brasero-media-debug" to the command line when they want to create a full log so as to have all the debug stuff about media initialization. Thanks in advance.