GNOME Bugzilla – Bug 575238
Wrong burn percentage, size of burnt data etc shown up
Last modified: 2010-01-27 12:15:14 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/277977 "This was observed while copying a 700MB CD to another: (See screenshot)" "there is no percentage in the progress bar but the window title still says things like "1547% done" the "31 MiB of 2 MiB" problem hasn't been fixed either tested it with brasero 0.9.1" screenshot: http://launchpadlibrarian.net/23787136/Bildschirmfoto-Brasero%20-%20CD%20wird%20gebrannt%20%281547%25%20fertig%29.png brasero log: http://launchpadlibrarian.net/23788173/brasero-debug.txt Thanks you,
Created attachment 132865 [details] Percentage bug
Still seeing this issue with brasero 2.26.0. I have a laptop (1 drive) and used "copy disc". After reading the source CD to 100% I replaced it with a blank CD-R and it started burning (with this bug)
Thanks for the report. I recently fixed a bug very similar to that one. Could someone try to reproduce that bug with master please?
I have this bug too. 1) I started to write the iso image in 8x 2) Disk being recorded, but brasero displays the wrong speed 3) On 45 percent progessbar cleaned and brasero showed 0 %, but disk continued writing and wrote correctly on logs I find: Sep 1 15:52:50 edgar-desktop kernel: [ 7129.262883] cdrom: This disc doesn't have any tracks I recognize! Sep 1 15:52:50 edgar-desktop kernel: [ 7129.396277] end_request: I/O error, dev sr0, sector 0 Sep 1 15:52:50 edgar-desktop kernel: [ 7129.396288] Buffer I/O error on device sr0, logical block 0 Sep 1 15:52:50 edgar-desktop kernel: [ 7129.397183] end_request: I/O error, dev sr0, sector 0 Sep 1 15:52:50 edgar-desktop kernel: [ 7129.397189] Buffer I/O error on device sr0, logical block 0 screens: http://launchpadlibrarian.net/31119568/step1.png http://launchpadlibrarian.net/31119598/step2.png version: 2.26.1
We believe that this has been fixed. Phillipe, do you remember which revision made the fix? Anyway, could you please try with a recent version (i.e. 2.28) and set either to VERIFIED or reopen if this still occurs. Thanks in advance!