[digiKam-users] Fail to update from schema 10 to schema 11

[Maik Qualmann]

Am Dienstag, 5. Juli 2022, 03:13:05 CEST schrieb David MARTIN:
> Hi list,
> 
> I get an error message when upgrading from 7.1 to 7.7
> When I launch the appimage from the connand line I get the following output:
> 
> ./digikam.appimage
Please enable debug output with:

export QT_LOGGING_RULES="digikam*=true"'

Post the terminal messages. I assume you have MySQL and no rights to create triggers 
in the database.
See also this old bug report: https://bugs.kde.org/show_bug.cgi?id=440458[1]

Maik

> -- digiKam Linux AppImage Bundle
> -- Use 'help' as CLI argument to know all available options for digiKam
> application.
> -- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
> --        to enable all debug messages on the console, use 'export
> QT_LOGGING_RULES="digikam*=true"'.
> Check library libudev.so.0
> Check library libxcb-dri3.so.0
> Check library libcrypto.so.1.1
> Check library libssl.so.1.1
> Check library libnss3.so
> Check library libnssutil3.so
> Check library libsmime3.so
> Check library libpango-1.0.so.0
> Check library libpangocairo-1.0.so.0
> Check library libgmodule-2.0.so.0
> 
> -- Preloading shared libs:
> :/tmp/.mount_digikauQFzm0/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/li
> :bxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1:/usr/lib/x86_64-l
> :inux-gnu/libssl.so.1.1:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64
> :-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x
> :86_64-linux-gnu/libpango-1.0.so.0:/usr/lib/x86_64-linux-gnu/libpangocairo-1
> :.0.so.0:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
> Digikam::CoreDbAccess::checkReadyForUse: Core database: cannot process
> schema initialization
> 
> Can you help me?
> 
> Kind regards
> 
> Dave



--------
[1] https://bugs.kde.org/show_bug.cgi?id=440458
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220705/4c68beea/attachment-0001.htm>