Add a New Comment Rich Markup
whats the state of this bug? i can reproduce it with all filenames that have chars that need shell escaping but graveman do not use. graveman is quite a good alternative to k3b, but if it chokes on such trivial things, it gives bad light on itself. thanx in advance for any info on the progress!
Graveman doesn't know how to handle whitespace in filenames. I tried to burn an iso file named "/home/arie/dir file/naam.iso . I got this error: (graveman:18338): GLib-CRITICAL **: unquote_string_inplace: assertion `err == NULL || *err == NULL' failed After renaming the directory it works.
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only logged-in users can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Copyright © 2024 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Page source code
Powered by Savane 3.13-caa5.Corresponding source code