[Digikam-devel] [digikam] [Bug 348586] digikam does not write description to XMP sidecar file anymore

[Knut Hildebrandt]

https://bugs.kde.org/show_bug.cgi?id=348586

--- Comment #24 from Knut Hildebrandt <knut.hildebrandt at gmx.de> ---
(In reply to Gilles Caulier from comment #22)
> Baloo support is activated on your computer. Deactivate ir and try again to
> see any changes....

Hey  Gillles,

Baloo support was NOT activated. Since I thought something was wrong with the
configuration  I activated it to just deactivate it immediately after. That
caused all meta data to disappear in digikam. Since I wanted to prevent digikam
writing these "changes" to the sidecar files I killed it. While restarting it
In got following error messages:

Restart with existing old DB:
The database is not valid: the "DBVersion" setting does not exist. The current
database schema version cannot be verified. Try to start with an empty
database.

Only the second restart brought up this:
The schema updating process from version 4 to 6 failed, caused by an error that
we did not expect. You can try to discard your old database and start with an
empty one. (In this case, please move the database files "digikam3.db" and
"digikam4.db" from the directory "/run/media/knut/Bildarchive"). More probably
you will want to report this error to the digikam-devel at kde.org mailing list.
As well, please have a look at what digiKam prints on the console. 

Went back to an older version of the database where only the meta data of two
albums should have been missing. Unfortunately no tags where shown in digikam
for all RAW data pictures (nef) whose meta data had been saved to XMP sidecar
files. But In could reimport them from the sidecar files. Now only the Tile and
Description of a few pictures are missing, probably because I had changed them
with one of the affected versions of digikam and thus they were missing in the
sidecar files. The positive side; after reentering them I'll make sure they
will be in the sidecar files.

Cheers Knut

-- 
You are receiving this mail because:
You are the assignee for the bug.