https://bugs.kde.org/show_bug.cgi?id=444479
--- Comment #3 from Martin Senftleben <li...@drmartinus.de> --- Thank you, Mike, that was a helpful hint. Here is the output: "digikam.widgets: Use installed icons digikam.general: Switch to widget style: "breeze" digikam.general: AlbumWatch is disabled digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "digikam" DB Face Name: "digikam" DB Similarity Name: "" Connect Options: "" Host Name: "localhost" Host port: 1111 Internal Server: false Internal Server Path: "" Internal Server Admin Cmd: "mysqladmin" Internal Server Serv Cmd: "" Internal Server Init Cmd: "" Username: "drmartin" Password: "XXXXXXX" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 12 digikam.coredb: Core database: makeUpdates 12 to 13 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Die Abfrage konnte nicht ausgeführt werden" "Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50537, now running 100604. Please use mariadb-upgrade to fix this error" "1558" 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ] Statement [ "\n DROP PROCEDURE IF EXISTS create_index_if_not_exists;\n " ] digikam.coredb: Core database: schema update to V 13 failed! digikam.coredb: Core database: cannot process schema initialization" I hope this answers Gilles questions as well. It seems it's using MariaDB? As mentioned above, I do not know what digikam is doing in the background, I was always content with what it does, until this bug occured. -- You are receiving this mail because: You are watching all bug changes.
