https://bugs.kde.org/show_bug.cgi?id=349617
pmarget...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pmarget...@gmail.com
--- Comment #12 from pmarget...@gmail.com ---
(In reply to Brian Frick from comment #11)
> Thank you for that command. I store media on a separate partition that I can
> share with my Windows boot, and bind those folders to the respective home
> directories. So `udiskctl dump` shows
>
> org.freedesktop.UDisks2.Filesystem:
> MountPoints: /home/frick/Music
> /home/frick/Pictures
> /home/frick/Videos
> /mnt/Share
>
> When clicking on the device in the sidebar, Dolphin will open Music (first
> in MountPoints, not last in fstab as I had thought).
>
> But (just me guessing) I think most desktop users using bind mounts are
> going to configure them in fstab, and that adds a "Configuration" dictionary
> at the top of the block with a 'dir' element storing the original device's
> mount point (for me, that's 'dir': <b'/mnt/Share'>). If the udisks issue
> isn't fixed, I think taking the path from 'dir', or, if not found, the
> shortest path from MountPoints would cover most cases.
Good points made here, my use case for bind mounts is indeed fstab setup for
xdg_dirs on a shared ntfs mount.
My workaround for this bug was creating an additional bind mount for the drive
itself pointing to a hidden folder in my home directory. This correctly opens
drive root in dolphin et al but it's hacky and I'd much rather see a proper
solution in the form of fstab being parsed like Brian Frick suggested.
--
You are receiving this mail because:
You are watching all bug changes.
