schema update to V 14 failed
Maik Qualmann
metzpinguin at gmail.com
Sun May 14 11:52:13 BST 2023
The update tries to create the "modificationDate" column in the "Albums" table,
but it already exists. The cause is unclear, the digiKam4.db was already used
with a newer digiKam version? The update has already been aborted and
restarted?
Install SQLiteBrowser, open digiKam4.db, go to Albums table and delete
modificationDate column.
Maik
Am Sonntag, 14. Mai 2023, 12:11:35 CEST schrieb jdd at dodin.org:
> Hello,
>
> I recently moved to openSUSE Tumbleweed (from openSUSE 15.3) and digikam
> don't works anymore.
>
> my computer is an asus tuf 706iu amd+nvidia gaming one
>
> to make things simpler, I will speak of digikam appimage 8.0.0, but I
> have the same result with my distribution version or any 7.7, 7.8 or 7.9
> appimage version.
>
> I can open a bug on kde bugtracker, but I'm not familiar with it and
> maybe here the problem may seems easy to fix.
>
> in short, digikam don't start. I get a message (in french, tranlated
> approx) "can't update shema from 13 to 14"
>
> on the terminal I have among other things:
>
> "Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> schema initialization"
>
> and with:
> export QT_LOGGING_RULES="digikam*=true"
>
> I get a long error log (in the text file below)
>
> any hint?
> thanks
> jdd
More information about the Digikam-users
mailing list