I'm having the same problem and have no idea how to fix it. Sometimes it
doesn't even display the writing speed, everything goes blank.
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you
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
** Attachment added: Screenshot 2
http://launchpadlibrarian.net/25382596/shot2.png
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: debug output
http://launchpadlibrarian.net/25382534/brasero-debug2.txt
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Screenshot 1
http://launchpadlibrarian.net/25382556/shot1.png
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here you are. Notice that writing speed is also not reported correctly.
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: Screenshot 3
http://launchpadlibrarian.net/25382603/shot3.png
--
Brasero shows wrong progress-information when burning more than 2GiB
https://bugs.launchpad.net/bugs/353694
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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?. May you also take
an screenshot of the issue? are you using growisofs?
** Changed in: brasero
