Bug#462451: brasero doesn't work when files to burn contain spaces

[Alan Baghumian]

> On Thu, 2008-01-24 at 19:56 -0300, Alvaro Herrera wrote:
> When trying to burn a data DVD containing filename with whitespace,
> brasero seems to convert the spaces to %20 and then attempt to read
> them.  When this fails, it simply punts and shows a dialog box saying
> "No such file or directory", with no indication as to what exactly is
> going on.
>
> strace'ing the process tells the tale: I can see an lstat call like
> this:
> lstat("/home/media/stuff/foo%20bar/baz%20qux", 0x7fffc4d13790) = -1
> ENOENT (No such file or directory)
> when there is no such file.  (There is a file named
> "/home/media/stuff/foo bar/baz qux" instead).
>
> FWIW, in case it matters, the thing I dropped into the right pane is the
> /home/media/stuff directory, not the "foo bar" directly.
>
> I find this rather unfulfilling.

I have 0.7.0 installed on my system. I tried to make an ISO file with some
files containing spaces in the names. Then mounted the ISO using a command
like:

# mount -o loop brasero.iso tmp/

And checked the contents. Everything seems to be OK. Would you please do
the same test with 0.6.x (your) version to see what happens? If you got
corrupted file names, so this means that this problem has been fixed in
new upstream version.

Cheers,
Alan