https://bugs.kde.org/show_bug.cgi?id=440590

            Bug ID: 440590
           Summary: digikam 7.3.0 fails to start: cannot process schema
                    initialization
           Product: digikam
           Version: 7.3.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Severity: grave
          Priority: NOR
         Component: Database-Schema
          Assignee: digikam-bugs-n...@kde.org
          Reporter: karsten.defre...@posteo.de
  Target Milestone: ---

SUMMARY
After installing OpenSUSE tumbleweed snapshot 20210727 (which provides digikam
7.3.0) on top of an earlier installation with digikam 7.2.0, digikam fails to
start during 'scanning collections'with GUI message 
"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."


STEPS TO REPRODUCE
1. a digikam 7.2.0 installation from e.g. tumbleweed snapshot 20210712, with a
local mySQL database, and some 10k pictures on a server in a local network
2. update to a snapshot with digikam 7.3.0 (I used 20210727)
3. try to start digikam

OBSERVED RESULT
GUI message: 
"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."
CLI message:
karsten@osl-i5:~> digikam -v
digikam 7.3.0
karsten@osl-i5:~> export QT_LOGGING_RULES="digikam*=true"
karsten@osl-i5:~> digikam
digikam.widgets: Use installed icons
digikam.general: Switch to widget style:  ""
digikam.general: Switch to application font:  QFont(Noto
Sans,10,-1,5,50,0,0,0,0,0)
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:        "digikam"
   Connect Options:          
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
   Host Name:                 ""
   Host port:                 -1
   Internal Server:           true
   Internal Server Path:      "/var/lib/digikam_db/MySQL"
   Internal Server Admin Cmd: "mysqladmin"
   Internal Server Serv Cmd:  "/usr/sbin/mysqld"
   Internal Server Init Cmd:  "mysql_install_db"
   Username:                  "root"
   Password:                  ""

digikam.databaseserver: Database Parameters:
   Type:                      "QMYSQL"
   DB Core Name:              "digikam"
   DB Thumbs Name:            "digikam"
   DB Face Name:              "digikam"
   DB Similarity Name:        "digikam"
   Connect Options:          
"UNIX_SOCKET=/home/karsten/.local/share/digikam/db_misc/mysql.socket"
   Host Name:                 ""
   Host port:                 -1
   Internal Server:           true
   Internal Server Path:      "/var/lib/digikam_db/MySQL"
   Internal Server Admin Cmd: "mysqladmin"
   Internal Server Serv Cmd:  "/usr/sbin/mysqld"
   Internal Server Init Cmd:  "mysql_install_db"
   Username:                  "root"
   Password:                  ""

digikam.databaseserver: Internal Server data path:
"/var/lib/digikam_db/MySQL/.mysql.digikam/db_data"
digikam.databaseserver: The mysql configuration was already up-to-date:
"/home/karsten/.local/share/digikam/mysql.conf"
digikam.databaseserver: Database server: "/usr/sbin/mysqld"
("--defaults-file=/home/karsten/.local/share/digikam/mysql.conf",
"--datadir=/var/lib/digikam_db/MySQL/.mysql.digikam/db_data",
"--socket=/home/karsten/.local/share/digikam/db_misc/mysql.socket")
digikam.databaseserver: Internal database server started
digikam.databaseserver: Running 0 seconds...
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: Unable to execute query" "Column count of mysql.proc
is wrong. Expected 21, found 20. Created with MariaDB 100215, now running
100510. 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
digikam.general: KMemoryInfo: Platform identified :  "LINUX"
digikam.general: KMemoryInfo: TotalRam:  16685096960
digikam.general: Allowing a cache size of 400 MB
digikam.databaseserver: Shutting down database server
digikam.databaseserver: Internal database server stopped
QThreadStorage: Thread 0x7fdb3ba0f2c0 exited after QThreadStorage 13 destroyed
karsten@osl-i5:~> 
EXPECTED RESULT
digikam starts up


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: OpenSUSE Tumbleweed snapshot 20210727
(available in About System)
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.84.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
- The QMYSQL message in the debug output pasted above suggests to run
"mariadb-upgrade". I did not do this yet - would it be a good idea to do so?
- Bugs 412417 and 435065 seems to describe a similar failure, but (as far as I
understand) with different root causes.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to