GNOME Bugzilla – Bug 588452
brasero blindly asumes I am going to create a data CD
Last modified: 2009-12-08 08:27:19 UTC
Hi, in the Media section of nautilus-file-management-properties I have selected to run brasero when a blank CD disc is inserted. This part works fine, but brasero always starts a Data Project although I am going to burn an Audio CD. I cannot tell how often I dragged some audio files into the project and realized just before clicking the Burn button that it will burn the audio files on CD, not the actual audio tracks. I suggest that brasero shows the "Create a new Project" screen on automatic start-up and leaves the choice to me instead of blindly assuming I am going to create a data CD. Even with the new version 2.26.x, just in the tradition of nautilus-cd-burner, brasero still blindly assumes that I am going to create a data CD and shows up the data-only burn:// window when I insert a blank CD. Other information:
Thanks for the report and sorry for answering so long after you reported your request. The problem here is that there are as many expectations as people regarding what its behaviour should be (a bit of an exageration of course). This issue is a matter of personal preferences. The default behavior (used or set in most distros) is meant to fit most of the people and it turns out a majority of them wants to burn a data disc when they insert a blank disc. Now as you point out this behavior can be modified to fit your needs. In the section of the nautilus-file-management-propoerties, I suggest you use "brasero -e" for blank CDs and DVDs to make sure you reach the initial part where it lets you choose the type of project you want. For all these reasons, I'll flag this bug as notabug but feel free to reopen it if you think I missed something.
Philippe, thanks for your response. I have seen that it will be able in future versions of Brasero to switch back and forth between audio and data projects (https://bugzilla.gnome.org/show_bug.cgi?id=558440). I am perfectly fine with this idea, so please consider this bug as fixed as per #558440.