Bug 442589

Summary: digikam does not start after upgrade, can not update Sqlite DB schema
Product: [Applications] digikam Reporter: Paul Richter <nobuyuki.richter>
Component: Database-SqliteAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: metzpinguin
Priority: NOR    
Version First Reported In: 7.3.0   
Target Milestone: ---   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed/Implemented In: 7.4.0
Sentry Crash Report:

Description Paul Richter 2021-09-17 10:53:12 UTC 
SUMMARY


STEPS TO REPRODUCE
1. Run digikam from console
2. 
3. 

OBSERVED RESULT

Dialog box says:
Failed to update the database schema from version 12 to version 13. Please read the error messages printed on the console and report this error as a bug at bugs.kde.org.

Console says:
digikam.dbengine: No DB action defined for "UpdateSchemaFromV12ToV13" ! Implementation missing for this database type ( "QSQLITE" ).
digikam.dbengine: Attempt to execute null action
digikam.coredb: Core database: cannot process schema initialization



EXPECTED RESULT
Program starts normally


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Slackware 15 / 
(available in About System)
KDE Plasma Version: 5.85.0
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Occurs after upgrading digikam from 7.2 to 7.3 via Slackware packages
Comment 1 Maik Qualmann 2021-09-17 11:09:34 UTC 
In digiKam-7.3.0 definitely exists the section for "UpdateSchemaFromV12ToV13" in the dbconfig.xml. How else other users should already be changed to digiKam-7.3.0 without problems? This is a package problem of your distribution. You probably use an old dbconfig.xml. Reports this problem to your distribution or check your installation.

Maik
Comment 2 Maik Qualmann 2021-09-26 20:21:58 UTC 
Is there any feedback? As already said, this is not a bug in digiKam-7.3.0 that we could fix.

Maik
Comment 3 Paul Richter 2021-09-27 09:49:01 UTC 
I was able to fix it by deleting another locally compiled 7.2 version in /usr/local. The program was loading that conflicting dbconfig.xml instead. Thank you for your information on dbconfig.xml that helped me resolve the problem.

I think would be helpful if the error message contained such information, if it could be determined at the time the error occurs. 

I have resolved this issue as Not A Bug.
Comment 4 Maik Qualmann 2021-09-27 18:07:24 UTC 
Thanks for the feedback.

Maik