After the release of Focal, I did a fresh install with mariadb server.
I did a mysqldump backup of the existing mythtv (bionic) mariadb
database and installed mythtv (mythbackend + mythfrontend + plugins) and
configured it to work with the current setup.
This all worked almost perfectly, just needing minor tweaks.
I have been installing updates to the system mostly when they are available.
I noticed that after an update to the system just recently, the
mythfrontend was giving a segfault when exiting, causing the crash to be
detected and mythfrontend to restart. Further investigation showed
indications that libmysqlclient was involved.
I downgraded to the previous version of libmysqlclient, and the problem
ceased. All was working as previously.
Upgrading to the latest (security fix) caused the problem to start
again. I downgraded again and locked the version, and the problem went
away again. I don't have any external facing mysql connections, so
security is not an imperative at the moment, but it does make me nervous
not to have security updates.
To cause the problem :- install the latest mysqlclient
To workaround the problem : downgrade the mysqlclient
If you need me to test anything, please let me know.
Good luck, and thanks,
Kim
On 9/5/20 1:18 am, Leonidas S. Barbosa wrote:
> Hi Kim,
>
> Thanks for report this issue. Could you please provides detailed steps
> in how to reproduce it?
>
After the release of Focal, I did a fresh install with mariadb server.
I did a mysqldump backup of the existing mythtv (bionic) mariadb
database and installed mythtv (mythbackend + mythfrontend + plugins) and
configured it to work with the current setup.
This all worked almost perfectly, just needing minor tweaks.
I have been installing updates to the system mostly when they are available.
I noticed that after an update to the system just recently, the
mythfrontend was giving a segfault when exiting, causing the crash to be
detected and mythfrontend to restart. Further investigation showed
indications that libmysqlclient was involved.
I downgraded to the previous version of libmysqlclient, and the problem
ceased. All was working as previously.
Upgrading to the latest (security fix) caused the problem to start
again. I downgraded again and locked the version, and the problem went
away again. I don't have any external facing mysql connections, so
security is not an imperative at the moment, but it does make me nervous
not to have security updates.
To cause the problem :- install the latest mysqlclient
To workaround the problem : downgrade the mysqlclient
If you need me to test anything, please let me know.
Good luck, and thanks,
Kim
On 9/5/20 1:18 am, Leonidas S. Barbosa wrote:
> Hi Kim,
>
> Thanks for report this issue. Could you please provides detailed steps
> in how to reproduce it?
>