Red Hat Bugzilla – Bug 397951
brasero miscomputes size of audio cd
Last modified: 2008-06-16 22:53:48 EDT
Description of problem:
When I tried to burn a audio cd from two .ogg files, brasero saw that they had a
length of approximately 70 minutes. But when it went to burn it complained, that
my 80 minutes cd-r was to small because it would need 722MB.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. create new audio project
2. add .ogg files with length of 70minutes
3. insert 80minutes cd-r
brasero stops and demands 722MB of free space
it should burn.
This may be a limitation of your CD-burner rather than a software problem. Have
you burned 70+ or 700MB+ CDs on that burner before ? With other cd burning
software ? Can you burn, say, a 750MB iso file with nautilus ?
Yes, I burned bigger cds before. I also burned some dvds ;). I also used
gnomebaker (which is currently out of use because of another bug) successfully
for burning complete audio cds.
The problem is, that the cd-r in my drive has 700MB and a 70minutes audio cd
should fit. It should _not_ take about 722MB of space.
This could of course be a problem with my system but as long as I don't know
where brasero gets its estimated size infos I blame it ;).
I also noticed this bug and it's a brasero problem. It's fixed in 0.7 and maybe
a backport for 0.6 is also available. Please take a look here :
It'll be really good if it can be fixed at least in F8. Is this possible?
Can you verify this build fixes your problem ?
brasero-0.6.1-2.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update brasero'
it is not fixed for ISO burning, I tried to burn a 690MB data CD image (ISO
Brasero indicates I have 703,1MB free on my CD-RW,
I click on Burn,
then it asks for erasing CD,
I click on Erase.
It then issues an error saying there is no sufficient space on my CD because it
I'm sure that the 690MB ISO can fit on my 700MB CD because I burnt it using
Nautilus and all was OK (right-click on the iso file in Nautilus, choose burn,
then erase when asked).
$ rpm -q brasero
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.
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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 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.