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 639989 - "Write to Disk" can't handle multiple burners
"Write to Disk" can't handle multiple burners
Status: RESOLVED DUPLICATE of bug 584893
Product: brasero
Classification: Applications
Component: nautilus-extension
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2011-01-19 20:45 UTC by Frank Griffin
Modified: 2012-11-13 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frank Griffin 2011-01-19 20:45:41 UTC
Originally reported at Mandriva Bugzilla as https://qa.mandriva.com/show_bug.cgi?id=62235

If you have two DVD burners, load a blank DVD into each, select an ISO image,
right-click, and select "Write to Disk", nautilus will choose one of them for
the target.  If you then use the target drop-down to try and select the other
one, there are some problems:

1) Only one blank media choice is displayed.  One or two empty selections are
also displayed, but if you select them, you get the blank media anyway.

2) Provided the two blank media are identical, there is no way to determine
which of them nautilus is displaying.  A mouseover will display the device
name, but that's not much help if both drives are identical.

3) Nautilus doesn't seem to realize that it is already burning to the "blank"
media in drive A, and will start a second burn operation to that drive.  This
second operation will read the ISO to create the checksum, and then hang
waiting for the first burn to complete.  Somebody knows that the first device
is locked, but nautilus doesn't appear to.  This also points up that nautilus is always displaying the same drive for "blank disk"

4) I guess nautilus is using brasero under the covers, but although brasero
in native mode has its own problems, it does display two separate choices for
the blank media if you fire it up and try to burn an ISO while nautilus is
using drive A.  So, nautilus doesn't appear to be letting brasero prompt for
the device choice.

5) Brasero doesn't realize that nautilus is using one of the drives for a burn,
but displays both as available for selection.  Again, you can't tell the
difference from the descriptions displayed, except for the fact that the "empty
space" part of the description for the one nautilus is burning to will decrease
if you keep cancelling and restarting the burn request in Brasero.

In sum, the nautilus (or is it gvfs now ?) device management is faulty, and
both it and Brasero need more unique ways to display the burn target choices.

I don't see any way around working the device assignment
(e. g. /dev/sr0) in there whether it's newbie-friendly or not.
Comment 1 Cosimo Cecchi 2011-10-09 19:56:16 UTC
-> brasero
Comment 2 Matěj Cepl 2012-11-13 15:00:43 UTC

*** This bug has been marked as a duplicate of bug 584893 ***