buggraveman - Bugs: bug #18678, Spaces in filenames

 
 

bug #18678: Spaces in filenames

Submitted by:  None
Submitted on:  Wed 03 Jan 2007 08:59:33 AM UTC
 
Severity:  3 - Normal Status:  None
Assigned to:  None Originator Name:  Arie Timmerman
Open/Closed:  Open Release:  * 0.3.12
Fixed Release:  None cdrecord version: 
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Wed 08 Aug 2007 06:29:11 PM UTC, comment #1: 

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!

Damir Perisa <damir>
Wed 03 Jan 2007 08:59:33 AM UTC, original submission:  

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.

Anonymous

 

(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

 

Carbon-Copy List
  • -email is unavailable- added by damir (Posted a comment)
  •  

    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.

     

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9