[mythtv-users] segfault in libmysqlclient.so.21

[John]

On 11/05/2020 13:18, Paul Harrison wrote:
> On 10/05/2020 16:23, jksjdevelop wrote:
>
>> MythTV Version : v31.0-13-g2cd6ccb419
>> ubuntu 19.10
>>
>> I have being experiencing segfaults in mythtv processes since 
>> libmysqlclient21 was updated from 8.0.17 to 8.0.20 -about a week ago
>>
>> Reverting to 8.0.17 does fix it.
>>
>> I use10.3.22-MariaDBinstead of Mysql 8.
>>
>> A bit of Googling shows nobody else has the same issue.
>>
>> Is it likely to be a corner case due to using MariaDB any thoughts?
>>
>> mythmetadataloo[2738]: segfault at 8 ip 00007fe22b99623f sp 
>> 00007ffd4cd34570 error 4 in 
>> libmysqlclient.so.21.1.20[7fe22b934000+e7000]
>> mythshutdown[2239]: segfault at 8 ip 00007f9d155f423f sp 
>> 00007fff10f96010 error 4 in 
>> libmysqlclient.so.21.1.20[7f9d15592000+e7000]
>> mythbackend[1691]: segfault at 8 ip 00007fc57cd3023f sp 
>> 00007ffd3e24e6c0 error 4 in 
>> libmysqlclient.so.21.1.20[7fc57ccce000+e7000]
>>
>>
>
> After an update over the weekend I'm seeing this as well.
>
>
> Paul H.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I can confirm that the issue is not present when using mysql 8 instead 
of Mariadb.

I spent several hours struggling to switch from MariaDB to mysql on my 
test system. Got there in the end.

Not looking forward to doing the same with the production system. 
Suspect I will have to when upgrading to Ubuntu 20.04.