Bug 511429

Created attachment 186362 [details]
DebugView log

Created attachment 186363 [details]
Windows 10 Pro Event Log

Is your MySQL server a MySQL or MariaDB server? Which version are you using?

For a debug log, the Qt debug variable must be set; otherwise, we'll only see warnings. It's best to enable the option for internal debugging in the digiKam setup under Miscellaneous -> System (restart digiKam). Although, I don't think we'll see anything more in the log with this problem.

Maik

@Gilles, Qt already has both the QMYSQL and QMARIADB drivers. We will likely need to enable this choice in the setup process in the future. The two projects are drifting further and further apart, although access to MariaDB via the MySQL Connector should still be ensured for now.

Maik

(In reply to Maik Qualmann from comment #3)
> Is your MySQL server a MySQL or MariaDB server? Which version are you using?
> 
> For a debug log, the Qt debug variable must be set; otherwise, we'll only
> see warnings. It's best to enable the option for internal debugging in the
> digiKam setup under Miscellaneous -> System (restart digiKam). Although, I
> don't think we'll see anything more in the log with this problem.
> 
> Maik

Thank you Maik for the reply...
This is a old Ubuntu 18 server and mysql  Ver 14.14 Distrib 5.7.42, for Linux (x86_64)
New debug log is added.

Created attachment 186364 [details]
New debug log

The face database cannot be updated because the "context" column no longer exists. This is because the next update step was once incompatible with MySQL (this has since been fixed). Since you have all the databases individually, the best solution is to delete all tables in "digikamface"; digiKam will recreate them.

Maik

Maik,

I suppose that bot mariadb and mysql QtSql driver are only available for Qt6. Right ?

In all cases i will need to patch AppImage, macOS, and Windows bundles in this way.

Best

Gilles

(In reply to Maik Qualmann from comment #7)
> The face database cannot be updated because the "context" column no longer
> exists. This is because the next update step was once incompatible with
> MySQL (this has since been fixed). Since you have all the databases
> individually, the best solution is to delete all tables in "digikamface";
> digiKam will recreate them.
> 
> Maik

I deleted the entire "digikamface" database and recreated it. Unfortunately, digiKam still crashes. It's possible that there's some issue on this particular computer, as digiKam runs without any Qt6 problems on the other four computers, and using the same MySQL server database.

Created attachment 186365 [details]
After deleted digikamface database

At least your face database is now clean.
We probably won't be able to resolve the crash any further at the moment.
Do you have the MySQL client installed? If so, you could try temporarily replacing the digiKam libmysql.dll file.

Maik

Maik,

From you comment 4, you said that Mysql and Mariadb QtSql driver are split. I don't see this info in the Qt doc :

https://doc.qt.io/qt-6/sql-driver.html#qmysql-for-mysql-or-mariadb-5-6-and-higher

The Qt base config script do not have both backend separated :

https://code.qt.io/cgit/qt/qtbase.git/tree/config_help.txt

Database options:

  -sql-<driver> ........ Enable SQL <driver> plugin. Supported drivers:
                         db2 ibase mysql oci odbc psql sqlite mimer
                         [all auto]
  -sqlite .............. Select used sqlite [system/qt]  

And it's true that only one driver name "mysql" exists for both :

https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/sqldrivers

So we have 2 solutions : 

1/ Create 2 bundles each time to support both separately, depending of the dependencies passed at Qt configuration.
2/ Create one dedicated sql driver for Mariadb (or Mysql) based on the current one from Qt and make it available in digiKam with the relevant settings adds to the Setup/Database. 

1/ I'm not favorable as it will increase the complexity for the packaging. 
2/ This will require more work but it will safe i think for the future.

Best

Gilles

Another possibility is to report to the Qt bugzilla a request to have a new QtSql driver for Mariadb, and not just one for both Mysql and MariaDb.

Gilles

QSqlDatabase::drivers() includes the MariaDB driver. However, I think that QMYSQL and QMARIADB are currently the same thing.

QList("QMARIADB", "QMYSQL", "QSQLITE")

We shouldn't do anything further at the moment.

Maik

During Christmas time, i will rebuild the whole digiKam installer from scratch with VCPKG packages updated (opencv, qt, ffmpeg). We will see if the problem remain.

Gilles Caulier

(In reply to caulier.gilles from comment #15)
> During Christmas time, i will rebuild the whole digiKam installer from
> scratch with VCPKG packages updated (opencv, qt, ffmpeg). We will see if the
> problem remain.
> 
> Gilles Caulier

Thank you Gilles! I will test it.