How can I read files from an NTFS drive on Linux?

Thank you for the explanation.
Are you sure, though, that the AppImage is actually unpacked, rather than just mounted (file-system in user space)?

kofa@eagle:~$ mount
...
Filmulator_v0.11.2rc11.AppImage on /tmp/.mount_FilmulIPK11W type fuse.Filmulator_v0.11.2rc11.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=1000)

Dive in and have a look at your /tmp folder, this is digikam on my installation. Seem to be actual files.

All mounted file systems hold files, whether they are from a hard disk, a network share, an SD card or a mounted CD image. That directory under /tmp is just a mount point, and I’m pretty sure the contents are read directly from the AppImage via FUSE. That’s why mount lists the image file, and that’s why the files are read-only (check the editor’s title bar in your screenshot). The ā€˜ro’ in mount’s output ((ro,nosuid,nodev,relatime,user_id=1000,group_id=1000)) means read-only.

I see this thread going on about the source of the install, but the statement you made indicates it just isn’t supported. Not following what installing from another source will do.

So are mounts to NTFS just not supported in Digikam? If that’s the answer fine, I just am thrown off by the long thread about installing from an app image, not sure what that is solving, or does it solve the problem? Has anyone confirmed?

For Digikam, it’s simple: if you can see the files in a file manager, digikam can see them (its album structure has a 1:1 correspondence with the underlying directory structure). Sorry, I’m not using NTFS, so don’t know if Linux can handle it. (for darktable, it’s basically the same)

Some issues ca be due to different install methods, e.g. snap or flatpak, where the snap or flatpak blocks access to certain parts of the file system. In that case, digikam won’t ā€œseeā€ those parts of the filesystem, and can’t use them…

And all the noise about appimage is due to appimage being the ā€œofficialā€ Linux package that’s distributed, afaik. If for one reason or another that doesn’t work, you have to find another solution (OBS usually ends up having a package for a decent number of distributions).

IIRC in the past it was basically a case of installing cifs-utils and mounting the share. Is that not true anymore?

Same… at some point I had to mount NTFS drives in Linux and this wasn’t a problem They even support writing to them now. But that was ages ago and I quickly erased that souvenir from my mind (in the same batch as my very modest contribution to the VisualBasic code corpus on this planet).

1 Like