[dolphin] [Bug 425319] Mounting an ISO with multiple partitions always mounts the wrong partition

Oded Arbel bugzilla_noreply at kde.org
Fri Aug 14 14:37:40 BST 2020


https://bugs.kde.org/show_bug.cgi?id=425319

--- Comment #2 from Oded Arbel <oded at geek.co.il> ---
(In reply to Kwon-Young Choi from comment #1)
> First of all, the mountiso is just a frontend to `udisksctl` which means
> that if the iso is not mounted correctly, it is probably because of
> `udisksctl`.

The issue is not with the "mount iso" feature - sorry about the confusion,
specifically about the component chosen, I just don't know which other
component to choose. The issue is what happens after "mount iso" completes its
work - i.e. when clicking the newly attached device. As mentioned in the report
- the same behavior is observed with other methods of "mounting an iso".

> On my machine, I tried to create an HFS/Joliet iso image using `mkisofs`:
...
> But I was not able to mount this iso using `udisksctl` (but `fuseiso` and
> `mount` worked).

I have the same issue as well - I have yet to manage to use mkisofs to create
an ISO that `udisksctl` and/or Dolphin can successfully mount - i.e. make it
appear in the "Devices" list in Dolphin, even though `solid-hardware5 list`
does show a device (though it doesn't look correct in some ways, compared to a
commercial ISO). I can mount the ISO manually using mount or fuseiso after
using udisksctl (or Dolphin) but it is not the same behavior and even if I make
a hybrid HFS ISO, mounting manually always goes for the Joliet/RockRdige file
system.

None the less, the problem I reported reproduces 100% with commercial ISOs that
I have.

> * Can you mount your iso file using only `udisksctl` commands?

Yes, but only the second partition: after `loop-setup`, I have /dev/loop24,
/dev/loop24p1 and /dev/loop24p2. with `sudo mount` I can mount either
/dev/loop24 (Joliet/ISO9660 file system) or /dev/loop24p2 (HFS filesystem). I'm
not sure what /dev/loop24p1 is - maybe the isolyzer or solid-hardware output
from above has some clues. When using `udisksctl mount`, only /dev/loop24p2
successfully mounts. So I have a feeling this is indeed not a Dolphin problem
but a udisks2 problem.

> * Could you provide an iso file with which I could reproduce your results?
> You can mail it to me directly at my email address if you want
> (kwon-young.choi at hotmail.fr)

It is commercial software, so I'm not sure that is a good idea, and it is also
very large. I'll email you privately and we can discuss there.

-- 
You are receiving this mail because:
You are on the CC list for the bug.



More information about the kfm-devel mailing list