Any help? Database problem

Help
1

I’m a newbie and just update Digikam from 7.0 to the last version mas now I got this message

The database has been used with a more recent version of digiKam and has been updated to a database schema which cannot be used with this version. (This means this digiKam version is too old, or the database format is too recent.) Please use the more recent version of digiKam that you used before.

I’m using chromeos flex in an old Dell pc and it was working fine with the old version.

thanks,

Jorge

2

Hi @jossanaijr and welcome here on the forum.

I read your post but don’t understand what is happening.
You write you updated form version 7.0 to a more recent version. Which version is that?

When you now use Digikam it tells you the database has gained a format belonging to a newer version of Digikam than the one you use at the moment, while with your 7.0 version it was okay. That looks like you now use an older version than 7.0, so again: which version do you use right now?

Did something else happen between the update and the first use of the updated program?

3

Hi! Thank you for your reply!
I was using version 7.9.0 and upgraded to 8.8.0.

As I said, I’m using an old Dell with ChromeOs Flex, Lynux active.
Here what I really did using AI:

The primary issue I encountered with your previous digiKam version (7.9.0) was a persistent GUI Flickering Bug and subsequent problems with Database Migration.

1. The Core Problem: Interface Flickering

The main observable issue was Interface Flickering (or screen tearing/shaking) whenever you interacted with the application.

  • Symptom: The display screen, particularly in the image editor, would oscillate or tremble, making the application unstable and difficult to use.

  • Root Cause: This was likely caused by a rendering bug stemming from an incompatibility between the Qt Framework (the underlying GUI technology used by digiKam) and the display server (X11 or Wayland) in your ChromeOS Flex/Crostini Linux environment. The older version’s code struggled to draw the interface correctly.

  • Solution: This was resolved by upgrading to digiKam 8.8.0, which uses updated Qt libraries that fixed the rendering instability.

2. The Secondary Problem: Database Blockage

After solving the flickering issue, the upgrade process immediately ran into a series of errors blocking the database update and face recognition.

  • Database Lock: The old database file (digikam4.db) was initially locked due to incomplete transactions from the old version and permission restrictions imposed by your NTFS/exFAT external drive when mounted in Crostini.

  • The Face Recognition Failure: The final problem was the Face Recognition Scan getting stuck at 0% after the database migration.

    • Root Cause: This specific failure was due to an AppImage/Platform Incompatibility. The newer digiKam 8.8.0 face recognition engine (which runs in a multi-threaded background process) was blocked by the strict sandboxing (security limitations) of the Crostini environment, preventing the scan from ever starting.

  • Data Integrity: Despite the errors, your metadata (tags, ratings, keywords) was successfully migrated and secured within the 8.8.0 database file.

4

Hi! Any suggestion?

THanks,

Jorge