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

Jim Abernathy jfabernathy at gmail.com
Sun May 10 16:15:14 UTC 2020


On 5/10/20 11:23 AM, 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]


I built a test system with Ubuntu 20.04 and the default version of 
mariadb-server and mythtv v31 was unstable. Since it was a development 
test system, I decided to punt until later. This will have to get fixed 
before I update my v31 production system from 18.04 to 20.04. But I have 
3 years before that is required.

Jim A




More information about the mythtv-users mailing list