Brasero reports blank CD's free space incorrectly.

Bug #438494 reported by Daniel LaGesse on 2009-09-29
This bug affects 14 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

I right clicked an ISO in Nautilus, and selected burn to disc. As the burning application is Brasero, I would assume the initial dialog belongs to it as well. The dialog showed in the 'Select a disc to write to' area 'Blank CD-R Disc: 6.9 MB of free space'. Obviously this is incorrect.

It looks like a simple bug in the display code, as the software didn't notice, and the ISO burned perfectly. Screenshot is attached.

Running Karmic circa alpha 5. Upgrading to alpha 6 soon (guess why I'm burning the ISO =P ), will report on whether it still exists.

ProblemType: Bug
Architecture: amd64
Date: Mon Sep 28 21:13:10 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.27.92-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: brasero
Uname: Linux 2.6.31-10-generic x86_64

Daniel LaGesse (dlagesse1992) wrote :
Daniel LaGesse (dlagesse1992) wrote :
Pedro Villavicencio (pedro) wrote :

thanks for the report Daniel, is this still an issue with 2.28.0 ?

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Daniel LaGesse (dlagesse1992) wrote :

This is still an issue with 2.28.0.

Daniel LaGesse (dlagesse1992) wrote :

Still an issue with 2.28.1.

tags: added: likely-dup
Twig (pfirth) wrote :

I'm also getting this issue on i386 with brasero version 2.28.1-0ubuntu1 trying to burn the latest live cd.

Twig (pfirth) on 2009-10-11
Changed in brasero (Ubuntu):
status: Incomplete → Confirmed
Daniel LaGesse (dlagesse1992) wrote :

Why the likely-dup tag? I didn't see any similar ones when I reported it.

Twig (pfirth) wrote :

Having just burned another ISO image, I think I may have spotted a possible connection. The free space reported seems to in fact be the total amount of space available on the blank cd minus that which would be used by the files contained within the image.

So, for example, if my blank CD can hold 700Mb of data and my ISO image is 100Mb, Brasero will report something similar to:

Blank CD-R Disc: 600Mb of free space.


Daniel LaGesse (dlagesse1992) wrote :

That is possible. I've only used one ISO for checking the bug, so that explains why I always see the same number.

So feature, not bug? if so terribly implemented. 'Free space after burning would be more appropriate, and neither is useful in a CD burning situation where adding files is very rare.

Elfy (elfy) wrote :

This is confusing - appears to be as said above and brasero reports how much space is left.

PlaidRadish (jeff-plaidradish) wrote :

I realize this is already confirmed. I can concur with all of the reports above. It is happening on the latest kernel update AND it is reporting the amount of free space that WILL BE left on the CD after the burn.

But... I don't think that's very helpful. If Brasero reported both the total free space, AND how much free space would be left over, that would save us all a bit of quick head math, but the way it is right now is not helpful... how do we request to have this changed?

Andreas Heinlein (aheinlein) wrote :

Still an Issue with Lucid. See attached screenshot.

Still Happening in 2.30.0

ubuntu-bug brasero apport information

Daniel Stone (danielstone) wrote :

When this ever gets a fix there should also be a warning on the disk blanking that it does not support rewritable discs

How would you call this "low importance"? This is the only and default burning app included with Ubuntu, and the application makes so many mistakes, that the user can't reasonably be expected to see through this.

My experience was that the blank CD size was wrong, and I couldn't select my CD from the drop-down menu. I would click it, but it didn't show up as the selected CD. So, I got sick of clicking that button and hit "Burn" instead, and magically it started burning. It burned everything fine.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers