Bug 635265 - Brasero produces coasters when attempting to burn multiple discs in parallel
Summary: Brasero produces coasters when attempting to burn multiple discs in parallel
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: brasero
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-18 14:16 UTC by Stewart Adam
Modified: 2011-06-28 12:40 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-28 12:40:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Stewart Adam 2010-09-18 14:16:10 UTC
Description of problem:
When attempting to burn multiple discs at once in Brasero, as soon as the first disc is finished it seems that the "eject" step halts progress on the other discs that are burning, producing coasters.

I have reproduced this using two drives:
- one is an internal LG 22x DVD-RW writer
- the other an eSATA-connected 22x DVD-RW/BD-ROM combo

I am writing a 4.3GB ISO image to blank DVD-R discs, but I assume the above applies to audio/video discs burned in parallel as well (untested).

Version-Release number of selected component (if applicable):
brasero-nautilus-2.30.2-1.fc13.x86_64
brasero-2.30.2-1.fc13.x86_64

How reproducible:
Always

Steps to Reproduce:
1. In Nautilus, right-click the ISO and select Write to disc...
2. Wait 2 minutes
3. Repeat step 1, but choose another drive
  
Actual results:
As the first disc finishes, the second one will stop burning producing an incomplete disc

Expected results:
Multiple discs can be burned in parallel without affecting the other optical drive(s)

Additional info:
I have tried burning a disc from Nautilus and one in the Brasero application itself as well, that didn't change anything.

The drive selection on the Nautilus dialog isn't that great either. I have to click "Properties" and look at the window title (which is the drive model #) to determine which drive is actually going to be used.

Comment 1 Bug Zapper 2011-05-31 13:10:41 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2011-06-28 12:40:17 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.