Hi, Desperate trouble here.
installed 3.8 using OBS latest release (over a current 3.6.1) Ubuntu studio 20.04
it crashed after the performance yes no message.
Removed ./config/darktable
re ran and it launches ok.
After much messing around and moving backup files one by one. The problem is pointing towards the data.db file.
library.db seems ok and I can see my photos and collections etc. But with a new data.db I have lost a considerable tag hierarchy. ie no tags.
If I replace the new data.db with my old one. dt fails to launch.
Your tags should be also saved in the xmp sidecar files. If your database is damaged and you don’t find a way to repair, you should be able to start with a fresh database, then reimport your images/edits.
thx for the comments
Ill need to look into the suggestions as am im not sure how to accomplish either.
I did however:
I have 3.6.1 on another machine so I copied the old data.db file over to it and it launched fine, all tags are visible etc.
So it looks very much like an incompatibility for 3.8 to read the 3.6.1 data.db?
I’m on Ubuntu 20.04, building dt from source. Transferring the databases data.db and library.db from 3.6 to 3.8 worked without any problems for me. So I’m quite sure, there is no incompatibility “per se”. I suspect your version 3.6 database might be damaged, causing the adaption from 3.6 to 3.8 to fail.
Let’s say it this way:
if there was an incompatibility between the 3.6.1 database format and dt 3.8.0, a lot of users would have been very unhappy already…
And you might want to use sidecar files in the future, they are a redundant storage for tags and edits, (thus useful when you have problems with the database, or don’t want to use one, as some do) and help with interaction between different programs. Another program certainly won’t use the dt database (and vice versa), but sidecars can be read by various programs.
(I use digikam to add captions and tags, because I prefer the interface there. dt reads those tags from the sidecar file, and digikam can also read tag and rating info after changes in dt)
thx rvietor.
incompatibility might not have been the best word. Obviously 5 gazillion users would have flagged such a problem earlier on. I guess Im trying to work out why 3.6 can read it fine but 3.8 can’t. Its(my db file) corrupt but only in a way 3.8 can’t read it.
I looked at paperdigits note re sqlite and as mentioned will have to read up as to how that works ie not enough info in that post for someone with zero knowledge on such things. Ive had family stuff to contend with today so not had much time to read.
As for sidecar files… xmps? yeah they should all be present.
and Ive imported a folder or two (because i also keep my images in a folder hierarchy so its fairly easy) to test the import and rebuild lib and I think I see how that works now. tags are appearing. Just going to take a while I guess to import the folder tree.
I’ve done some reading and google searches and I’m afraid none the wiser. i’m not sure how to implement this sqlite PRAGMA integrity_check
is it a cli command?
Assuming that sqlite is installed and darktable is at its default location you do the following from a terminal:
cd ~/.config/darktable
cp data.db data.db.org
sqlite3 data.db
sqlite> PRAGMA integrity_check;
ok
sqlite> .quit
I do not have an sqlite executable, it is called sqlite3. You use Ubuntu and I’m assuming it is the same in your case. If not: try sqlite instead of sqlite3
The cp step is just to make sure that you have a copy (probably already one present called data.db-snp-xyz, but better make 100% sure).
sqlite3 data.db starts sqlite and loads data.db. You see some info and then the sqlite> prompt.
If the PRAGMA integrity_check; does not return ok, you have a database problem…
Many thanks.
Weird thing was that last night:
Nothing came up in the installed app search menu
Sqlite3 did not come up in the software centre search
A browser app did which I installed and could open see the tags etc
I didn’t however try just entering the cli
Note: last night I started with new db files and started importing the photo files.(more info coming)
This morning:
I went to install it from terminal and it was already installed.
Anyway ignoring all this I ran the PRAGMA integrity_check; (on the old db files)
and got the ok on both db files.
Ill assume this side thread is closed and he problem is elsewhere
Ok so last night I began with fresh db files and started importing the photo files.
My thinking was this would at least “defrag like” the db so was probably a good thing todo anyway. I let it churn thru over night.
This morning:
close/ open dt for good measure.
check the tags.
info presented using DB browser.
old db has 3496 elements
new db (built by importing images) has 3320
Probably explained by the “cleanup”
I also seem to have lost all synonyms.
in the browser db tags/ columns
it has ID,name,synonyms,flags
While most have NULL some have flags=4 Any idea what flags are?
ok may have found the/a problem.
Whilst browsing the old data.db to manually add all my synonyms back I noticed one tag had a flag value of 655364. Unusual as all the others are either null or under 6