Package: mariadb-server-core-10.3 Version: 1:10.3.22-1 mariadb-server-core-10.3 installs the mariadb charset files in /usr/share/mysql:
$ dpkg -L mariadb-server-core-10.3 | grep charset /usr/share/mysql/charsets /usr/share/mysql/charsets/Index.xml /usr/share/mysql/charsets/README /usr/share/mysql/charsets/armscii8.xml /usr/share/mysql/charsets/ascii.xml [...] /usr/share/mysql/charsets/swe7.xml The location of these files causes the libmysqlclient20 client library to consider them charset files from mysql, and it tries to use them. I think this behavior is wrong, as the charset files do not belong to mysql, however it is not immediately causing user-visible issues. Things are worse with mysql-8.0, not yet in Debian but packaged in Ubuntu. In mysql-8.0 the charset file format is not compatible with the older versions, and this causes the client library to segfault when trying to use the charset files from mariadb. Relevant Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504 I'm not sure of the best way to fix this, maybe mariadb needs to use the /usr/share/mariadb namespace for its resources. Paride