Bug 414148 - Database error on upgrade. Digikam now won't open.
Summary: Database error on upgrade. Digikam now won't open.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Engine (show other bugs)
Version: 6.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR grave
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-14 18:18 UTC by mrflashflood
Modified: 2021-08-17 18:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.4.0
Sentry Crash Report:


Attachments
screenshot of error (28.45 KB, image/jpeg)
2019-11-14 18:18 UTC, mrflashflood
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mrflashflood 2019-11-14 18:18:29 UTC
Created attachment 123933 [details]
screenshot of error

SUMMARY
upgraded from 5.9.0 to 6.4.0. As per instructions I copied out the database folder first. When I started 6.4.0 it said it couldn't find database files and wouldn't start. I then copied in the database folder to the installation directory and tried again. This time it said that it failed to update the database schema from version 9 to version 10 (see attachment). It also said to read the error message from the console but I don't know what that means.

STEPS TO REPRODUCE
1. Reinstalled 6.4.0
2. 
3. 

OBSERVED RESULT
same error

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 10


macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
I upgraded because I wanted to browse photos by location. I could see the thumbnails on a map but couldn't open them. I was hoping the new version would work better.
Comment 1 Maik Qualmann 2019-11-14 20:26:15 UTC
If you copied the database, would it still have existed? Or have you moved the datbase files? Anyway, download DebugView from Microsoft and start it. Then start digiKam and post the messages that appear in DebugView.

Maik
Comment 2 Maik Qualmann 2019-11-19 17:48:42 UTC
Is there any progress here? Without a log file from DebugView we can not help.

Maik
Comment 3 caulier.gilles 2020-01-12 16:55:46 UTC
mrflashflood,

Do you seen the previous message from Maik ???

We needs feedback

Thanks in advance

Gilles Caulier
Comment 4 caulier.gilles 2020-07-14 09:41:36 UTC
Hi,

Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here:

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier
Comment 5 caulier.gilles 2020-07-30 09:45:07 UTC
digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2021-03-30 08:31:50 UTC
digiKam 7.2.0 official release is published with more than 360 files closed from bugzilla:

https://www.digikam.org/news/2021-03-22-7.2.0_release_announcement/

Can you reproduce the dysfunction with this version ?

Thanks in advance for your feedback

Gilles Caulier
Comment 7 Maik Qualmann 2021-08-17 18:54:17 UTC
I am closing the bug report. We currently have checks at startup to see whether the DB and tools are available. We can also upgrade the DB in the event of major changes in a new MySQL server version.

Maik