Progress bar stays on 0% even after the burning begins

Bug #346489 reported by Botond Szász
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

When starting to burn a disk, for a while the progress bar shows the progress correctly, but after a while, it changes to 0% and stays like that for the rest of the process. It looks exactly like when I start the burn process and Brasero did not yet calculated the remaining time, and progress bar is at 0%. This only happens in the latest version of Brasero (2.26.0-0ubuntu1) that comes in Jaunty (alpha 6). It used to work correctly in earlier versions.

Revision history for this message
Botond Szász (boteeka) wrote :

In this particular case I was burning an image file, but the exact same thing happens when burning files (data project).

Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

summary: - [brasero] Progress bar stays on 0% even after the burning begins
+ Progress bar stays on 0% even after the burning begins
Changed in brasero (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Botond Szász (boteeka) wrote :

I followed your instructions. Here it is the debug output. The problem happened this time too. Somewhere around 50% the progress bar just went to 0% and stayed there for the rest of the burning process.

Revision history for this message
Everthon Valadão (valadao) wrote :

same here! the first time this happened, I thought it had "freezed/crashed", so I canceled the burning and lost a DVD :(
but after, I tried again (with a little more patience) and the burning process concluded successfully, even with the progress bar stuck in 0%: this could be very confusing to newbies!

Revision history for this message
Pat Leamon (pleamonhp) wrote :

I just noticed this on ubuntu 64bit / jaunty. It seems to be hitting the integer limit (about 2gig) and then going to zero. If your burn is big enough (over 4.2 gig) the progress bar resumes again from the start - and then the burn finishes.

Revision history for this message
Jefferson H. Xavier (jeffersonx) wrote :

I have the same problem here. Sometimes Brasero fails when I burn images with 2GB or more. When it works, the progress bar stays on 0% after 2GB and it shows "Writing track 01".

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

Me too. I've just burned a 2,5GB .iso image into a DVD-R disc, and brasero never changes the progress bar and percent indicator: it always stays at 0%.

Revision history for this message
Dave Jeffery (kecske-bak) wrote :

Seems to be a fix available upstream:

Fix #582261 – brasero shows 0% done, while continues burning discgnome-2-26
Fixed an overflow in variable that stopped wodim/cdrecord to work properly for a size over 2GiB

Revision history for this message
Ard (termernator) wrote :

Hey! Anybody here?! :) It's simle bug, so please - fix it!

Revision history for this message
Raffles10 (stuartclampit) wrote :

If Ubuntu is going to include Brasero in it's distribution it really needs to work properly, this progress bar bug is basic stuff, if this continues Ubuntu should include k3b instead of Brasero, even on Gnome !

Revision history for this message
Scott Minster (sminster) wrote :

This is likely the same bug as https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/370999. Burning progress over 2 gigabytes fails. That bug references upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=582261, which indicates it is fixed in 2.26.3. IIRC, Karmic will have 2.28, so this fix should be there.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.