Brasero thinks the capacity of a blank dvd -r is 4.3 GB when it's actually 4.7 GB or 4.3GiB
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Brasero |
Expired
|
Medium
|
|||
brasero (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Starting in 11.10 nautilus reports file (iso) size in actual GB, but brasero incorrectly uses 4.3 GB as the capacity of a dvd -r
The actual numbers of a dvd -r are
available space - 4,706,074,624 bytes/2,297,888 sectors/
So an iso that is near the true max file size of a dvd -r, while it will fit , is now rejected by brasero as being to large for the media
Ex. - have an iso that can and has been burned to dvd -r
Actual size - 4,691,394,560 bytes
Nautilus/properties reports - 4.7 GB (4,691,394,560 bytes)
Brasero shows iso size as 4.7 GB, media capacity as 4.3 GB, refuses to burn
(as a comparison a dvd burner, ImgBurn, that just uses bytes/sectors for filesize & media avaialble space shows this & will burn
iso size - 4,691,394,560 bytes/2.290.520 sectors : dvd -r media - Free Sectors: 2,297,888 ; Free Space: 4,706,074,624 bytes
K3b use GIB so it also has no problems burning the above mentioned iso
So it would seem brasero, gnome/nautilus, ubuntu need to get on the same page here & brasero needs to use the same method for both filesize & media capacity, either GB or GIB
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: brasero 3.2.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-1-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Tue Nov 29 01:12:45 2011
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111126)
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: brasero
UpgradeStatus: No upgrade log present (probably fresh install)
description: | updated |
summary: |
Brasero thinks the capacity of a blank dvd -r is 4.3 GB when it's - actually 4.7 GB + actually 4.7 GB or 4.3GiB |
Changed in brasero: | |
importance: | Unknown → Medium |
status: | Unknown → New |
Changed in brasero: | |
status: | New → Expired |
Thank you for your bug report, Pedro could you check if that happens to you and upstream it if that's the case?