UDF not properly recognised

[Andrew Jorgensen]

UDF iso images almost always also have an ISO9660 file-system on them but the two filesystems need not point to the same set of files.

I recently downloaded an iso image that has all the real data on UDF and just a README.TXT on ISO9660 which basically just says "This CD requires a system which supports the UDF filesystem." File Roller only sees the README.TXT. It should probably use UDF if it's available since it doesn't have all of the restrictions that ISO9660 has and the only reason to have a different set of files on the two filesystems is if UDF contains data that ISO9660 can't contain properly.

[Sebastien Bacher (seb128)]

Thanks for your bug. What does "isoinfo -J -R -l -i image.iso" list?

[Andrew Jorgensen (ajorg)]

$ isoinfo -J -R -l -i image.iso
isoinfo: Unable to find Joliet SVD

[Sebastien Bacher (seb128)]

isoinfo is doing the same, either a bug from genisoimage or from the image, reassigning

[Arthur Peters (amp)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Andrew Jorgensen (ajorg)]

This bug still exists. Viewing the vista iso image does exactly the same thing now as it did when I first reported.

It's notable that the new gvfs archive stuff also does exactly this.

[Gaetan Nadon (memsize)]

I was able to reproduce the problem in Intrepid ubuntu-8.10-alternate-amd64. The File Roller does not recognize the UDF filesystem on the MS Vista iso image. It only displays the README text. It is worth noting that Ubuntu mounts the file system correctly and adds an icon labeled UDF volume. The UDF support in Ubuntu is sufficient for applications to mount and explore UDF filesystems.

The isoinfo command was perhaps misleading. It is documented as reading ISO9600 filesystems, no mention of UDF. The command with the -d option states that the vista image does not contain either Joliet nor Rock Ridge extensions. Invoking the command with -R would list the Rock Ridge extension but silently returns as there is none. Invoking the command with -J would list the Joliet extension but issues an error message which may mean a bug in the command or a bad iso. In fact, it's just that the Joliet extension is not there.

Given that the UDF support is present in Ubuntu, it would be appreciated if the File Roller developer make a support statement regarding UDF file system.

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Sebastian Schauenburg (sschauenburg)]

This issue still exists in 9.04 (here: amd64)
 * File-roller and Archive-mounter (gvfs) only 'see' the README.TXT

Workaround: Mount the image manually (with mount -o loop), works perfectly.

[Sebastien Bacher (seb128)]

The issue is an upstream one, it would be nice if somebody having it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

[Pedro Villavicencio (pedro)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=589158

[neuromancer (neuromancer)]

Same problem with iso of puppy linux: http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/pup-431.iso
I've tried to create a bootable usb disk with default ubuntu tool (usb-creator-gtk) but it exit and report:
Unable to find Joliet SVD

Also isoinfo report same problem:
isoinfo -J -R -l -i pup-431.iso
isoinfo: Unable to find Joliet SVD

[Tim Wieneke (tim-spen)]

same for the ubuntu lucid sparc image:
isoinfo -J -R -l -i /tmp/lucid-server-sparc.iso
isoinfo: Unable to find Joliet SVD

[Rodrigo Primo (rodrigosprimo)]

I have the same issue with ubuntu-10.04-desktop-powerpc.iso

I was trying to create a usb stick usb-creator-gtk (so not using file-roller) and I got:

isoinfo: Unable to find Joliet SVD

Same thing if I try to call isoinfo directly:

isoinfo -J -R -l -i ubuntu-10.04-desktop-powerpc.iso
isoinfo: Unable to find Joliet SVD

[alelondon (alelondon)]

same here as #12

[arky (arky)]

DEBUG:root:mount: /media/30CA-7EE9
DEBUG:root:add_target: /org/freedesktop/UDisks/devices/sdb1
DEBUG:root:device_added: /org/freedesktop/UDisks/devices/sda1
DEBUG:root:device_added: /org/freedesktop/UDisks/devices/sda2
DEBUG:root:device_added: /org/freedesktop/UDisks/devices/sda3
DEBUG:root:device_added: /org/freedesktop/UDisks/devices/sdb
DEBUG:root:disk added: /org/freedesktop/UDisks/devices/sdb
DEBUG:root:add_target: /org/freedesktop/UDisks/devices/sdb
DEBUG:root:device_added: /org/freedesktop/UDisks/devices/sda4
DEBUG:root:Backend told to add: /home/iise/Images/lupu-501.iso
DEBUG:root:['isoinfo', '-J', '-i', '/home/arky/lupu-501.iso', '-x', '/.disk/info']
isoinfo: Unable to find Joliet SVD
ERROR:root:Could not extract .disk/info.
DEBUG:root:No source selected.
DEBUG:root:No source selected.
DEBUG:root:cancel_install

$ isoinfo -J -R -l -i lupu-501.iso
isoinfo: Unable to find Joliet SVD

[laysan_a (laysan-a)]

I have the same issue with usb-creator. It picks-up my kubuntu 10.04 alternate.iso just fine (I assume because The Powers have decided to include a joliet file system in the (k)ubuntu installation disks (so this doesn't have to be fixed?). However, my two puppy installation disks for my dell i8k don't have joliet, so they don't get recognized (unable to find Joliet SVD).

I would have thought this would be fixed by now, (2 years, and how many distributions?), if for no other reason, than out of pride (since Joliet is a MS specification).

[Peter M. Clausen (pclausen)]

still there using ubuntu 11.04, with this iso: chakra-2011.09-edn-i686.iso from http://sourceforge.net/projects/chakra/files/2011.09/chakra-2011.09-edn-i686.iso/download

[Peter M. Clausen (pclausen)]

Workaround: instead of 'usb-creator-gtk' use 'unetbootin'

[chemicalfan (mike-lumsden)]

Is this still an issue with the current releases (Mint 17, Ubuntu 14.04)?