[Akonadi] [Bug 383991] New: Akonadi 17.08.0 / 5.6.0 with MariaDB 10.2.8 - Plugin pvio_socket could not be loaded: not initialized

[Dennis Schridde]

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

            Bug ID: 383991
           Summary: Akonadi 17.08.0 / 5.6.0 with MariaDB 10.2.8 - Plugin
                    pvio_socket could not be loaded: not initialized
           Product: Akonadi
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: server
          Assignee: kdepim-bugs at kde.org
          Reporter: devurandom at gmx.net
  Target Milestone: ---

When starting Akonadi 5.6.0 / 17.08.0 on a system with MariaDB 10.2.8, I see
the following in ~/.local/share/akonadi/akonadiserver.error.old:
```
Database error: Cannot open database.
  Last driver error: "QMYSQL: Unable to connect"
  Last database error: "Plugin pvio_socket could not be loaded: not
initialized"
QSqlQuery::exec: database not open
Database error: Cannot open database.
  Last driver error: "QMYSQL: Unable to connect"
  Last database error: "Plugin pvio_socket could not be loaded: not
initialized"
QSqlQuery::exec: database not open
Unable to open database "Plugin pvio_socket could not be loaded: not
initialized QMYSQL: Unable to connect"
```
(Newlines inserted by me.)

This issue was also reported with Akonadi 17.04.3 and MariaDB 10.2.7 [1,2].  We
are using QtSQL 5.7.1.

Upgrading the database does not fix this error.  It persists after the
following commands:
```
/usr/sbin/mysqld --defaults-file=$HOME/.local/share/akonadi/mysql.conf
--datadir=$HOME/.local/share/akonadi/db_data/
--socket=/tmp/akonadi-mysql.socket
mysql_upgrade --socket=/tmp/akonadi-mysql.socket
kill $MYSQL_PID
```

Downgrading MariaDB to 10.1.25 prevents this error from happening [3].  The
issue seems to be related calls to QSqlDatabase::removeDatabase() and
QSqlDatabase::addDatabase() in
akonadi-17.04.3/src/server/storage/dbconfigmysql.cpp:492 [4].

For more information, please also see the full report in the Gentoo bug tracker
[5].

[1]: https://bugs.gentoo.org/show_bug.cgi?id=626464#c0
[2]: https://bugs.gentoo.org/show_bug.cgi?id=626464#c3
[3]: https://bugs.gentoo.org/show_bug.cgi?id=626464#c21
[4]: https://bugs.gentoo.org/show_bug.cgi?id=626464#c29
[5]: https://bugs.gentoo.org/show_bug.cgi?id=626464

-- 
You are receiving this mail because:
You are the assignee for the bug.