XCA v2.5.0 MariaDB/MySQL error Driver not loaded about xca HOT 7 CLOSED

The problem is version 6.5.3.
When I run xca.exe from a cmd windows I get the error message: Cannot mix incompatible Qt library (6.5.3) with this library (6.5.2)

When installing 6.5.2 instead it works.
BUT, you will have to create a new db connection.
Previous db connection were saved as user@server/QMYSQL3:db_name
New connections are saved as user@server/QMYSQL:db_name
The file where these connections are stored is located in C:\Users%USERNAME%\AppData\Roaming\xca

from xca.

You installed the MinGW variant ?

from xca.

Yes, I did.
I tried even the last version, 6.5.3: it didn't work

from xca.

I have the same issue on macOS (after the upgrade to macOS 14.0). Is there a place to download the macos mysql driver that is known to work? Did some looking around, and there are some instructions to build it yourself, but so far no success (I am also by far a Qt expert).

from xca.

You're right, jensver!
The solutions, after installing qt_mysql_driver (MinGW flavour) version 6.5.2 (not newer), are two:

1. recreate all remote DB connections: you have to remove the AppData\Roaming\xca directory, start XCA and create new MariaDB connections;
   OR
2. go to AppData\Roaming\xca, edit the file "dbhistory" substituting every occurrence of "QMYSQL3:" with "QMYSQL:"

The second solution maintain existing remote DB connections.

from xca.

You're right, jensver!
The solutions, after installing qt_mysql_driver (MinGW flavour) version 6.5.2 (not newer), are two:

1. recreate all remote DB connections: you have to remove the AppData\Roaming\xca directory, start XCA and create new MariaDB connections;
   OR
2. go to AppData\Roaming\xca, edit the file "dbhistory" substituting every occurrence of "QMYSQL3:" with "QMYSQL:"

The second solution maintain existing remote DB connections.

from xca.

Jesus Christ, I've been banging my head against the wall for an hour.

Thanks for the solution @jensver

@chris2511 I am grateful for your great software, I really am, but this needs to be much better documented (and preferrably fixed or worked around by the installer). For the last hour I thought I had lost access to my certs and keys...

from xca.