Wrongly identifies a black DVD as having 0 space

[_whitehawk_]

Binary package hint: brasero

This was happening with 0.8.2 in Ubuntu 8.10 and I've just upgraded to 9.04 Beta which contains version 2.26.0 of Brasero and exactly the same thing is happening.

This is on a 64 bit AMD system running 64 bit Ubuntu.

If I insert a blank DVD or CD and use Brasero as launched by Gnome and add anything to the "Files" list, the "space" shows 100% and is red.

However, if I fire up Brasero independently and then start to add files, it gets as far as calculating a checksum, but then bails out saying that there is 0 space on the disc.

End result is no burning for me :-(

Just as a by-the-by, I tried K3B (which I used to use), but that keeps locking up when it ejects the disc and re-loads it to verify the data.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/brasero
NonfreeKernelModules: nvidia
Package: brasero 2.26.0-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: brasero
Uname: Linux 2.6.28-11-generic x86_64

[Pedro Villavicencio (pedro)]

Thanks for your report, could you run brasero from the command line as: brasero --debug &> brasero-debug.txt perform the operation to reproduce the bug and attach the resulting file to the report?. Thanks in advance

[_whitehawk_ (ubuntu-gavsworld)]

Hmmm ... strange ... it appears to work today!

However, tracing back the sequence of events, there was a funny thing happened with Brasero:

1. Ubuntu 8.10 (Brasero 0.8.2) error as described - 0 space on blank DVD or CD
2. Upgrade to 9.04
3. Rebooted
4. Noticed that Brasero and gstreamer0.10-plugins-bad didn't upgrade (eventually).
5. Performed upgrade on Brasero (to 2.26.0) and gstreamer0.10-plugins-bad
6. Error as before
7. Next day (after shutdown and power up today)
8. Brasero works both from command line and launching when blank media is inserted.

I suspect that there was some shared library resident in memory during the upgrade from 0.82 to 2.26.0 that meant it not loading the new one until after a reboot.

So, perhaps not a Brasero problem now, but maybe an upgrade problem?

[Pedro Villavicencio (pedro)]

Ok good, marking this as fixed then, thanks for the feedback.