Second, we need to use the correct edition of our DigiKam, if it was installed via the package manager it is 1, if Flatpak was used to install our DigiKam, then it is 2, and if you’re using DigiKam on MacOS 3. (Remember, the assumed repository path is: ~/Pictures/DigiKams/, see: Step 1): sed -i "s,Database Name=.*,Database Name=,g" "$/Pictures/DigiKams" If it blows up, close Digikam on all computers, restore the database to a known good version and you should be good to go. Backup that database, actively try to mess it up by doing similar things on two computers and see what happens.
Remove all values from the database variables in our digikamrc.template. Make regular backups and worst case you restore from backup if anything blows up. If the digikamrc wasn’t in one of the previous locations, then try to find it by typing: find ~ -type f -name digikamrc Step 4: start digikam and after it crashes open /.xsession-errors and look towards the end for digikam output. open kdebugdialog -> deselect all, then search for digikam -> select all, then apply and exit. If you’re using DigiKam on MacOS, type the following, then ignore Step 4: cp -v ~/Library/Preferences/digikamrc ~/Pictures/DigiKams/digikamrc.template Re: Digikam does not find database when starting. If you have installed DigiKam, via Flatpak, type: cp -v ~/.var/app//config/digikamrc ~/Pictures/DigiKams/digikamrc.template If you have installed DigiKam, via your package manager, type: cp -v ~/.config/digikamrc ~/Pictures/DigiKams/digikamrc.template Now copy that settings file to our repository directory, and rename it to digikamrc.template. (Of course you can re-configure them later once you open that library). Because we’re going to make your configuration you’re about to make the default configuration for each new library you’re going to create. Now, open up the DigiKam and go to Settings -> Configure digiKam. (in this tutorial, we will assume it’s: ~/Pictures/DigiKams/): mkdir ~/Pictures/DigiKams Step 2 (optional): Make a repository directory to store all libraries in. And since DigiKam stores the media’s data in a database, we want to give each library we’re about to create its own digikamrc and its own database files to store all the media’s data it needs about our collections. If we think about it, the second option seems to be better, simply because some settings make sense in some libraries, while they don’t in others. Letting each photo library have its own digikamrc.One global digikamrc for all photo libraries.etc, in a MySQL (or MariaDB) or SQLite database (default) which we’ll cover it in this article. DigiKam stores the media’s metadata, media’d thumbnails, image’s finger-prints, media’s information.But if it was being installed via Flatpak, it will live in ~/.var/app//config/. DigiKam stores all its application settings like the GUI settings and database’s information in a file called digikamrc usually lives in ~/.config/ if it was installed via your distro package manager, or if it was being compiled from the source.But before doing that we need to know how does DigiKam work by default. We are going to write a small BASH script to achieve our goal which makes DigiKam capable of managing multiple photo libraries.
0 kommentar(er)
