Bug 528375

Summary: Brasero disregards burn speed setting
Product: [Fedora] Fedora Reporter: Tapani Mattila <tapani.mattila>
Component: braseroAssignee: Xavier Lamien <lxtnow>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 15CC: beland, gmureddu, lxtnow
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:14:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tapani Mattila 2009-10-11 18:53:16 UTC
Description of problem:
Selecting a specific write speed in brasero doesn't have any effect. Brasero always writes at full speed. This causes easily write errors.

Version-Release number of selected component (if applicable):
brasero-2.26.3-1.fc11.x86_64

How reproducible:
Every time (tested 10 times)

Steps to Reproduce:
1.Open an iso file for writing either from Nautilus or from Brasero's UI.
2.Set writing speed to 4x or any other than maximum.
3.Begin burning.
  
Actual results:
Burn operation is done at maximum speed.

Expected results:
Burn operation is done at 4x speed.

Additional info:
I only tested burning ready ISO images. I tested with speeds 2x, 4x and maximum.
Dvdrecord writes at requested speed.

HW: Lite-On LH-20A1S

Comment 1 Bug Zapper 2010-04-28 10:47:33 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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 2010-06-28 15:00:12 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.

Comment 3 Tapani Mattila 2010-08-29 18:44:56 UTC
Still reproduces with F13: brasero-2.30.2-1.fc13.x86_64.

In addition to note in original report:
Tested also by creating a data project to write files from hard disk.

Comment 4 Christopher Beland 2010-09-03 20:17:41 UTC
Also reported for Fedora 12 as Bug 565984.

Comment 5 Gian Paolo Mureddu 2010-12-05 07:53:31 UTC
I've seen some speed inconsistencies with Brasero in pretty much every Fedora release where I have used it (began using it in Fedora 9, I think, previously I used K3B).

I've made a few test cases, and noticed some rather ugly and erratic behaviour of Brasero.

1. Brasero doesn't seem to enable Burnproof (Burnfree) buffer under-run protection by default, nor there seems to be a configurable option to tell it to use it always, neither in the GUI nor the GConf preferences, or not that I've been able to find (up to Fedora 13, I have yet to test in 14, though I'm pretty sure the situation won't have changed... much)

2. It only writes at full speed... when you burn from an image or allow it to create an image of the content you want prior to actually burn it. Burning files "on-the-fly" results in a highly erratic speed, and usually stays very, very low. Often times when this happens data is corrupted in the disk. By contrast if I manually call cdrecord/wodim/etc and set burnfree and a rather large FIFO (~250 Mb) data burns at the requested speed just fine, device buffer never empties, some times the FIFO varies and I've not seen a case of data corruption.

Apparently you can only enable Burnfree when burning from the contextual menu in Nautilus, and often times I have the option greyed out. Just tried with some files and with an image, with the image I get the option when mastering the files with the burn:/// URI in Nautilus, and try to burn on-the-fly I cannot enable burnfree.

Comment 6 Bug Zapper 2011-06-02 17:37:22 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 7 Tapani Mattila 2011-06-22 19:09:51 UTC
Reproduced with F15 X86_64.
Not dependent of hardware.
Now tested also with burning a data disk directly without creating an image file first.

Comment 8 Fedora End Of Life 2012-08-07 20:15:00 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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