I've suffered this same bug under Hardy, using Brasero 0.8.1. I don't have the log file produced, but was mostly identical to the one in the first comment of this bug report (except that my file names were different, of course ;))).
I thought that the bug was related to the file integrity check plugin, but looks like it wasn't. I think that the problem lies in activating the "Increase compatibility with Windows" checkbox: after that Brasero asks if you want the "windows incompatible" files renamed. I answered no, the checkbox was unchecked but somewhat Brasero did a weird mix... Probably Brasero tried to do the "increase(d) compatibility with Windows" but without renaming files and all went wrong...
I think I'm able to reproduce the bug, if more information is needed.
I've suffered this same bug under Hardy, using Brasero 0.8.1. I don't have the log file produced, but was mostly identical to the one in the first comment of this bug report (except that my file names were different, of course ;))).
I thought that the bug was related to the file integrity check plugin, but looks like it wasn't. I think that the problem lies in activating the "Increase compatibility with Windows" checkbox: after that Brasero asks if you want the "windows incompatible" files renamed. I answered no, the checkbox was unchecked but somewhat Brasero did a weird mix... Probably Brasero tried to do the "increase(d) compatibility with Windows" but without renaming files and all went wrong...
I think I'm able to reproduce the bug, if more information is needed.
Raúl