Hi,
I want to change from Windows to Linux. All my drives are formated with NTFS (exept Linux-root).
How can I read files from a NTFS-drive in DigiKam?
Is it possible to depose the DigiKam-database on NTFS too?
In Linux/Gnome4/Ubuntu appear NTFC- drives on the left taskbar automatically.
In Darktable I don’t see any NTFS-Drives.
Modern Linux can read/write NTFS drives without problem.
When mounted correctly they appear as directories in the general tree (there is no notion of “drives” in Linux). Check in /mnt or /media. You can also see if they appear in /etc/fstab or the output of findmnt in a terminal.
Your partition manager may also help you to discover them and automount them on startup.
A possible problem with NTFS drives on Linux is their status. If they were not properly detached from the WIndows system (Windows system was in some sleep state and not totally shutdown), they keep their “in use” flag, and the Linux filesystems won’t mount them.
Last, if accessing a removable NTFS drive is OK, I would strongly advise making backups and moving to Linux filesystems because these are usually a lot faster, and fully support Unix ways (executable bit and authorizations in general, supported filenames, etc…).
Thank you for the answer.
On Linux I can open NTFS-Files without any problems.
But how can I connect DIGIKAM whith NTFS?
I don´t see any connection to NTFS on DigiKam NTFS. Please see the screenshot.
Best regards
ftomasch
What distribution of Linux do you use?
How did you install Digikam and darktable? Using some universal package like snap/Flatpak, or your distribution’s native package format (for Mint/Ubuntu/Debian, that would be a ‘deb’ package, for RedHat/Fedora, an ‘rpm’ package).
I’m asking because normally all applications should have access to the same paths, but snap and other package formats impose security restrictions, which you may have to relax, but how you do that depends on the packaging.
Note that digikam uses KIO, and you’re using the gnome desktop. All the bits to access drive mounts are likely not there for digikam to use.
I use Ubuntu 23.04 with Gnome 4.
Digikam 8 is directly from Ubuntu Software
Unfortunately (in this case), Ubuntu Software allows you to install software from several sources. For example, Ubuntu ships Firefox as a snap package by default. So the fact that you installed it from the Software Centre does not answer the question.
Edit: I’ve checked my own machine (I do not have digikam installed), and I think it looks like a native deb package.
OK?
But I’m very confused.
What can I do?
or, can I do something???
Maybe the easiest way would be to copy the images over to a Linux-formatted drive — that way, you can be sure to avoid any potential issues AND you have the added bonus of a backup (even though most Linux distros support read — and some support write — using a non-native file system is always going to be more risky).
On my Kubuntu 22.04, Digikam is a native package so there are no restrictions. You can check if you have the “native” package or a “snap” version by starting a terminal and entering
>$ type digikam
if it says /snap/bin/digikam you have the snap version, otherwise it will likely say /usr/bin/digikam and you have the native/regular version.
Your file dialog is showing you the “root” /, so you have to expand it and see if a directory somewhere looks like you NTFS drive. See my previous post to figure out which directories these drives are masquerading as.
Yes, I checked. It’s a Snap.
Then, I found and downloaded the program as ´"appimage".
Unfortunately I could not start it.
Now I need a break …
Thank you for the very good information
If you download an AppImage, make sure you set it as executable. From the command-line:
chmod +x Whatever.AppImage. Consult your desktop environment’s documentation for the GUI equivalent. After that, you should be able to launch it.
I do not use ‘snap’ anything but this worth a read and maybe substitute Digicam for Meshlab.
You do need the ntfs-3g package to read/write NTFS I cannot think it is not installed by default but you can check in a terminal (1)
ntfsinfo -V
Your appimage download and snags with Ubuntu 23.04
The appimage as a single file requires fuse to run. Check that it is installed (2)
fusermount -V
All being well, initially run the executable appimage in a terminal with a dot-slash (3)
./digiKam-8.0.0-x86-64.appimage
It is a nice, although large appimage, to make it more permanent extract using the --appimage-extract switch (4)
And you can run that from the squashfs-root directory using (5)
./AppRun
That saves unpacking every time to the root temp directory. Everything working ? Make a .desktop file for that AppRun file.
I don’t understand, as digikam 8 (at least the beta version) is also a native package in Ubuntu 23.04.
https://packages.ubuntu.com/lunar/amd64/digikam/download
It’s not the release version, but quite close to it, I think.
You can remove ‘snap’ support completely (make sure you follow all steps, including ‘Additional comments’):
Unfortunately, the PPAs (personal package archives, alternative software sources often providing more up-to-date versions of software) mentioned on digikam.org either don’t support 23.04 (digiKam - photo management (Xenial & newer) : Rob Savoury) or do not provide digikam (Kubuntu Backports : “Kubuntu Package Archives” team)
WIth ‘snap’ completely wiped from my Kubuntu 23.04 system:
kofa@eagle:~$ apt show digikam
Package: digikam
Version: 4:8.0.0~+beta1-0ubuntu3
Priority: optional
...
kofa@eagle:~$ sudo apt install digikam
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
digikam-data digikam-private-libs libastro1 libkf5akonadi-data libkf5akonadicontact-data libkf5akonadicontact5abi1 libkf5akonadicore-bin libkf5akonadicore5abi2 libkf5akonadiprivate5abi2 libkf5akonadiwidgets5abi1
libkf5calendarcore5abi2 libkf5contacteditor5 libkf5grantleetheme-data libkf5grantleetheme-plugins libkf5grantleetheme5 libkf5mime-data libkf5mime5abi2 libmagick++-6.q16-8 libmarblewidget-qt5-28 libqt5serialport5
libqt5sql5-mysql libshp2 marble-plugins marble-qt-data opencv-data
Suggested packages:
digikam-doc akonadi-server
The following NEW packages will be installed:
digikam digikam-data digikam-private-libs libastro1 libkf5akonadi-data libkf5akonadicontact-data libkf5akonadicontact5abi1 libkf5akonadicore-bin libkf5akonadicore5abi2 libkf5akonadiprivate5abi2 libkf5akonadiwidgets5abi1
libkf5calendarcore5abi2 libkf5contacteditor5 libkf5grantleetheme-data libkf5grantleetheme-plugins libkf5grantleetheme5 libkf5mime-data libkf5mime5abi2 libmagick++-6.q16-8 libmarblewidget-qt5-28 libqt5serialport5
libqt5sql5-mysql libshp2 marble-plugins marble-qt-data opencv-data
0 upgraded, 26 newly installed, 0 to remove and 0 not upgraded.
Need to get 46.4 MB of archives.
After this operation, 156 MB of additional disk space will be used.
Don’t understand ? Well you said you had downloaded the appimage and it is version 8
and from a terminal you should be able to run (providing dependencies satisfied)
./path-to-/digiKam-8.0.0-x86-64.appimage
If you are replying to me: I’m not the original poster; I did not download the AppImage, was just suggesting it. What I didn’t understand is why there is a snap version installed when there is a deb package. I guess Ubuntu is offering both. As I never use the GUI to manage packages, have got rid of snap completely after it broke my Firefox, and don’t use Digikam, I assume I simply do not run into this situation.
No, not you, got you mixed up with post no. 10 ie.
Then, I found and downloaded the program as ´"appimage".
Unfortunately I could not start it.
Ubuntu has a “Software Center” where you are liable to get a ‘Snap’ and that is much like a ‘flatpak’. A digikam snap will be ‘sandboxed’ and that is probably the reason for not seeing external drives.
I had a quick look through the Ubuntu PPA’s and nothing as recent as that digikam appimage.
I am sort of old-fashioned, I still use synaptic package manager and sometimes dpkg with deb pakages. It is all about what you are happy with.
Ubuntu Software can present multiple sources for a package. It’s easy not to notice. Look at the right side of the title bar. Here’s an example where you can choose either the [expletive deleted] snap or a deb:
Why would one do that? I only use a handful of AppImage-packed software, but always just keep it as the original file, without extracting. What are the benefits of extracting?
As ever up to the user.
It might be a practical reason, The appimage requires fuse2 (deprecated) and fuse3 is installed. see: How to Enable AppImage Support in Ubuntu 23.04 - OMG! Ubuntu Careful with that one if you want ntfs. Installing fuse2 might remove ntfs-3g
Philosophical reason. The appimage unpacks to the tmp folder as a hidden file. Close the appimage and those files are deleted. That might be ok for you, the appimage maybe only used occasionally. What about if you open that appimage 10 times a day ? This is the digikam appimage in /tmp 661 MB 8175 files.
In that case you might want to consider extracting the appimage and running from a folder of your choice.
