GnomeBaker can't burn a file with an equal sign in the name

Bug #89018 reported by Brian Pitts
4
Affects Status Importance Assigned to Milestone
GnomeBaker
Unknown
Unknown
gnomebaker (Ubuntu)
Fix Released
Low
Lionel Le Folgoc

Bug Description

Binary package hint: gnomebaker

Steps to reproduce:
Create a file named a=b
Add this file to a GnomeBaker project
Attempt to burn

Output:
Executing 'mkisofs -gui -V GnomeBaker data disk -A GnomeBaker -p Brian Pitts -iso-level 3 -l -r -hide-rr-moved -graft-points --path-list /tmp/GnomeBaker-brian/gnomebaker-BZHJOT | builtin_dd of=/dev/hdc obs=32k seek=0'
INFO: UTF-8 character encoding detected by locale settings.
 Assuming UTF-8 encoded filenames on source filesystem,
 use -input-charset to override.
mkisofs: No such file or directory. Invalid node - 'b=/home/brian/a=b'.
:-( write failed: Input/output error

Revision history for this message
ryanmbruce (ryanmbruce) wrote :

I am also having trouble with this, I got a minutely different error:

GnomeBaker 0.6.0
genisoimage 1.1.2 (Linux)

Executing 'genisoimage -gui -V Backup Vol.2 -A GnomeBaker -iso-level 3 -l -r -hide-rr-moved -J -joliet-long -graft-points --path-list /tmp/GnomeBaker-bobo/gnomebaker-PIGWXT | builtin_dd of=/dev/hdd obs=32k seek=0'
I: -input-charset not specified, using utf-8 (detected in locale settings)
genisoimage: No such file or directory. Invalid node - '5.m4a=/home/bobo/music/My Music/Radiohead/Hail To The Thief/2+2=5.m4a'.
:-( write failed: Input/output error

This seems like a fairly serious problem in genisoimage, and might be subject to a format string vulnerability (please correct me if I'm wrong, but I think the importance should be raised until proven otherwise).

Please let me know if I can provide more useful information.

Revision history for this message
ryanmbruce (ryanmbruce) wrote :

This bug has been reported on the sourceforge tracker for gnomebaker as well:

http://sourceforge.net/tracker/index.php?func=detail&aid=1736869&group_id=127397&atid=708499

Cheers,
-Ryan

Revision history for this message
Goedson Teixeira Paixão (goedson) wrote :

The attached patch should fix the problem. I'm uploading this to Debian as gnomebaker 0.6.0-9 now.

Revision history for this message
Goedson Teixeira Paixão (goedson) wrote :

The attached patch should fix the problem. I'm uploading this to Debian as gnomebaker 0.6.0-9 now.

Revision history for this message
Goedson Teixeira Paixão (goedson) wrote :

This bug is fixed in Debian's 0.6.0-9 revision of the gnomebaker package.

Changed in gnomebaker:
assignee: nobody → ubuntu-universe-sponsors
status: New → Fix Committed
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

Thanks, I am going to merge it from unstable.

Changed in gnomebaker:
assignee: ubuntu-universe-sponsors → mrpouit
importance: Undecided → Low
status: Fix Committed → In Progress
Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

gnomebaker (0.6.0-9ubuntu1) gutsy; urgency=low

  * Merge from Debian unstable, remaining Ubuntu changes:
    - debian/patches/21_-export-dynamic_for_glade.dpatch: Add, based on
      guidance from <did447 at gmail dot com>, fixing libglade problem
    - Modify Maintainer value to match Debian-Maintainer-Field Spec
    - debian/patches/07_improved_gnome_menu_entry.dpatch: add polish desktop
      entries from <dominikowski at gmail dot com>
  * debian/patches/07_improved_gnome_menu_entry.dpatch: updated to remove
    "Applications" from the Categories to keep it up-to-date with debian.

gnomebaker (0.6.0-9) unstable; urgency=low

  * debian/patches/19_crash_when_writing_data_project.dpatch: Warn user about
    non-writable temporary directory when writing a data disc project
    (LP: #108000).
  * debian/patches/20_escape_filenames.dpatch: Fixes the handling of file names
    containing the '=' or '\' characters (LP: #89018)
  * Removed "Applications" from the Categories in the GNOME menu entry

 -- Lionel Le Folgoc <email address hidden> Mon, 27 Aug 2007 23:01:45 +0200

Changed in gnomebaker:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.