Hello,
I’m in the process of trying to move from Windows to Linux, and so I have a new machine running Linux Mint 22.2.
I already have digiKam running on a Windows 10 machine, where Mysql Internal is used to manage my photo collection. In that setup, the photo themselves are stored on a NAS, and I keep the digiKam database on the local hard drive. I’m trying to replicate that setup with the new Linux machine, but I’m unable to get the Mysql Internal database set up.
I’m using digiKam v8.7, which I’ve installed via the Software Manager using Flatpak. I’ve also installed the Mariadb-server v10.11.13 from the Software Manager - I know this is an older version, but it’s the one one available via the Software Manager, and I was trying to avoid installing software directly, where possible (by ‘directly’, I mean that I was trying to avoid having to follow the install instructions give at Download MariaDB Server - MariaDB.org, for example.) Also, I couldn’t find any minimum Mariadb version number that digiKam requires.
Anyway, the issue I have is that as part of the digiKam setup process when Mysql Internal is selected, you have to tell it where a few mariadbd binaries are located. To do this, there’s a ‘Find’ button for each one, which opens a file dialog. My memory of doing this on Windows is that you just browse to the folder where the binary is located, and you’ll somehow be able to just select that folder (the ‘Open’ button will become enabled, or something similar.)
My problem is, that even when I browse to the location where I’m certain the binaries are installed, I can never select that location - i.e. I’m not able to tell digiKam where to find the mariadb binaries.
Can anyone help with this?
I’ve verified the location of where the binaries are located using the which command from the cmd window. So, for example, I get this:
- which mariadbd
- /usr/sbin/mariadbd
As described above, when I browse to this folder using digiKam, I can’t select this folder to tell it that the binary is located there (even though it definitely is there, it seems.)
I get the same results with each of the other files that digiKam is looking for (mariadb-admin, mariadb-upgrade, mariadb-install-db)
I could try to update mariadb to a newer version, but before doing so I was hoping someone might be able to point out some silly mistake I’m making which is causing all this to happen.
Thanks for any help!