Comment 33 for bug 299956

Unfortunately, all the broken ISO images that I have that suffer this problem are fairly large; too large for an attachment.

I'd like to discuss the particular problems that I'm having and make sure we're all on the same page. I also have a theory what the problem is. Let's say I have an image f.iso. Opening the image in Gnome Archive Manager (file-roller) or mounting it with gvfs (Gnome Archive Mounter) will show "broken" filenames with the ";1" suffix (which is actually a version number, part of the Rock Ridge CD filesystem extensions). However, if I mount the image normally, with the mount command, the file system is shown correctly. Please verify that this so. For example, if I do this:

mkdir f
sudo mount -o loop f.iso f
ls f

...I will see the correct filenames, without the Rock Ridge version number. So whatever the problem is, it is a discrepancy between the CD filesystem as implemented in the kernel versus as implemented in (userspace) gvfs. Assuming that we all agree about this, then we have determined that the problem is in the backend shared by gvfs and file-roller.

Now, let's do another test. Let's use the isoinfo command to see what it thinks about the given image. Try this:

isoinfo -d -i f.iso

On images that suffer this problem, isoinfo always tell me "NO Rock Ridge present" even though the typical ";1" suffix appears, indicating RR extensions. So now it seems like the image was made with RR extensions, but either the userspace tools aren't detecting it, or the presence of RR isn't correctly marked in the image. Can you please verify that the above command reports no RR extensions for all ISO images that suffer this problem?