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 591393 - Brasero doesn't report current free space, but instead the space you *will* have after burning
Brasero doesn't report current free space, but instead the space you *will* h...
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
git master
Other All
: Normal normal
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-08-11 00:29 UTC by Jud Craft
Modified: 2018-09-21 16:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
picture of Image Burning window (80.42 KB, image/png)
2009-08-11 00:32 UTC, Jud Craft
Details

Description Jud Craft 2009-08-11 00:29:41 UTC
Please describe the problem:
Brasero shows an incorrect free space amount on the blank disc when burning disc images (CDs in particular).

Steps to reproduce:
0. Insert a blank CD.
1. Find a disc image file.
2. Open it to bring up the "Image Burning" window.
3. Look at the "Select a disc to write to" box, and read the free space.


Actual results:
Brasero says that my blank CD has a very small amount of free space (in the range of 60 megabytes).

Expected results:
Brasero should show the full amount of space for a CD-R, or the space remaining for a CD-RW.

Does this happen every time?
Yes.

Other information:
This does not prevent you from using Brasero, but it is a little confusing when Brasero tells you your new blank CD only has 60 MB of space.
Comment 1 Jud Craft 2009-08-11 00:32:02 UTC
Created attachment 140404 [details]
picture of Image Burning window

Note how Brasero gives a very small value of free space for a brand new blank CD.
Comment 2 joerg.schilling 2009-08-11 11:49:12 UTC
What is the current state of the media inquestion?

What do you see when calling:

cdrecord -minfo

with this medium in the drive?

BTW: If the output from cdrecord is correct, then you found 
another reason why brasero should not issue own SCSI commands but
rather ask cdrecord to do this because:

1) cdrecord is OS independent

2) cdrecord knows many workarounds for firmwarebugs.

Comment 3 Philippe Rouquier 2009-09-03 18:49:53 UTC
Thanks for the report. This is not a bug as brasero display the free space _after_ the image will be burnt; as you may have seen your disc is 700M and your image is 634M that's why brasero tells you that after burning the image, there will be 68M of free space.
Comment 4 Jud Craft 2009-09-03 21:45:43 UTC
I see.  I'm quite alright with that.  But the UI caption is very ambiguous.

It clearly says "Blank Disc:  68M Free", which can easily be interpreted as "Your blank disc has 68M free".  Instead, it should say "68M remaining after burn" or "Disk usage: 634M/700M" or something like that.

And even better, move the caption somewhere else.  The dropdown should be merely be "Blank CDR Disc", and once selected, a progress bar below it could give the space.

That one UI control is just trying to do too many things at one time.
Comment 5 Daniel Boles 2017-10-21 14:20:32 UTC
(In reply to Philippe Rouquier from comment #3)
> Thanks for the report. This is not a bug as brasero display the free space
> _after_ the image will be burnt; as you may have seen your disc is 700M and
> your image is 634M that's why brasero tells you that after burning the
> image, there will be 68M of free space.

Well, that is a bug, as it leads users like me to think that their Quick Blank was not sufficient, so they waste their time on a Full Blank - only to find the same result and then realise it's because Brasero uses a completely, pointlessly unintuitive definition of free space.
Comment 6 Daniel Boles 2017-10-21 14:23:13 UTC
Surely, at the very least, the caption should be updated, as Jud said.

See also Bug 711264.

reopening since the stance on this may be different, 8 years later
Comment 7 GNOME Infrastructure Team 2018-09-21 16:42:44 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/65.