GNOME Bugzilla – Bug 611344
Total size to burn reported to be -2147483648 MiB
Last modified: 2010-06-19 19:35:01 UTC
Original report: http://bugs.debian.org/568606 by Leandro Lucarella. The progress fails because the total size reported to be burned is "-2147483648 MiB" (the "-" is not a typo) so the progress when burning is approximately 0. I've seen this behaviour burning a DVD with 4.4GiB of data and another with 4.1GiB, in both simulation and real burning.
Thanks for the report. I tested with stable and trunk but the problem did not show up. My guess is that the problem comes from a backend that reports a bad size (probably -1 or a problem related to mixing guint64 and guint). Anyway could you ask your user to create a log of such a session please (brasero -g > log 2>&1)? Thanks.
Note that this used to happen with the wodim backend in 2.26, but now this is with the libburn backend. I’ll ask the requested information.
Created attachment 162075 [details] stdout+stderr log I'm having the same problem with brasero 2.30.1 on Fedora 13. The burning process appears to complete just fine, with the DVD being finalized and readable, but after the disk is finalized brasero prompts that an unknown error has occured and offers the option to save the burn session log.
Created attachment 162076 [details] brasero session log
Hi, thanks for the answer. I recently fixed a problem with g_signal_emit () which expected a long argument and was only passed 1 or -1 (not 1L or -1L) which caused things very similar to what you describe. This fix is already in master and gnome-2-30 branch ready for brasero-2.30.2. Could you give it a try please and let me know if it works? This bug really looks like #618942 at least for the last comment.
Created attachment 162272 [details] stdout+stderr for brasero 2.31.2 I checked out the latest git version (2.31.2 in the about dialog), and it worked perfectly, the total compilation size was displayed properly and the burn progress percentage was calculated correctly. I've attached the log, just in case it is of any further use to you. Thanks!
Thanks for reporting. Closing the bug but feel free to reopen it.