Bugzilla Bug 66528

Muine crashes on badly escaped files, this seems to be due to some gnome-vfs
bug exposed by muine. A quick workaround for muine would be the attached patch
as long as gnome-vfs hasn't been investigated. It just checks if vfs can
actually get file info & returns if it can't.


A small backtrace that shows the probable vfs problem (note that this bt is
already taken from a slightly altered muine codebase).

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1149189040 (LWP 27864)]
0x42a61e2c in metadata_load (filename=0x1 <Address 0x1 out of bounds>,
    error_message_return=0x447f35ac) at metadata.c:672
672                     gnome_vfs_file_info_unref (info);
(gdb) print info
$1 = (GnomeVFSFileInfo *) 0x8da6ac8
(gdb) print *info
$2 = {name = 0x8daf170 ") - End Of The World.mp3",
  valid_fields = GNOME_VFS_FILE_INFO_FIELDS_NONE,
  type = GNOME_VFS_FILE_TYPE_UNKNOWN, permissions = 0,
  flags = GNOME_VFS_FILE_FLAGS_LOCAL, device = 0, inode = 0, link_count = 0,
  uid = 0, gid = 0, size = 0, block_count = 0, io_block_size = 0, atime = 0,
  mtime = 0, ctime = 0, symlink_name = 0x0, mime_type = 0x0, refcount = 1,
  reserved1 = 0x0, reserved2 = 0x0, reserved3 = 0x0, reserved4 = 0x0,
  reserved5 = 0x0}
(gdb)

The file in this case is  'No Doubt \(Rem Cover\) - End Of The World.mp3'

Created an attachment (id=41227) [details]
patch to workaround weird filenames

I have this very problem with muine.  Otherwise it seems to work well and I'm
getting used to using the thing ;)

Will this patch make it into portage soon, or should I start re-naming all my
files?  I have a *lot* to re-name.

BTW, the files I'm having the problems with have an apostrophe in the name,
e.g.:

Yngwie Malmsteen_1984_Rising Force_05_Icarus' Dream Suite Op 4.flac

Please see bug #72770 for an ebuild that should fix the problem. Tested
locally, muine survives with an MP3 named like the one foser mentioned. Please
report back if it works/doesn't work.

Marking TEST-REQUEST, pending feedback.