<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 6/1/20 1:08 PM, Jeremy D. Eiden
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:7d553c40-9939-03a8-e32c-697a8541e7fe@gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p><br>
      </p>
      <div class="moz-cite-prefix">On 6/1/20 12:00 PM, Richard Shaw
        wrote:<br>
      </div>
      <blockquote type="cite"
cite="mid:CAN3TeO07j3+jiZ4e48a-G5ZE14RfKaQSt6w3n+GsYUKCrWrUdg@mail.gmail.com">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <div dir="ltr">
          <div dir="ltr">On Mon, Jun 1, 2020 at 10:16 AM Peter Bennett
            <<a href="mailto:pb.mythtv@gmail.com"
              moz-do-not-send="true">pb.mythtv@gmail.com</a>> wrote:<br>
          </div>
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex"><br>
              The latest mysql client library causes segfaults when a
              process using <br>
              mariadb exits. See bug reports:<br>
              <br>
              <a
                href="https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504</a><br>
              <a
                href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961672"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961672</a><br>
              <br>
              There does not seem to be any fix coming soon, based on
              comments in the <br>
              bug reports. The bug reports imply that mysql should
              change their <br>
              package to conform to mariadb. That is not likely to
              happen.<br>
              <br>
              If upgrading to Ubuntu 20.04 make sure you are using mysql
              not mariadb, <br>
              or else downgrade package libmysqlclient21 to the older
              version.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I'm not sure what the package availability is on
              Ubuntu, but on Fedora we no longer use the mysql client,
              but use the mariadb one which provides the same
              capability:</div>
            <div><br>
            </div>
            $ dnf --repoid=rawhide repoquery --provides
            mariadb-connector-c<br>
            libmariadb.so.3<br>
            libmariadb.so.3()(64bit)<br>
            libmariadb.so.3(libmariadb_3)<br>
            libmariadb.so.3(libmariadb_3)(64bit)<br>
            libmariadb.so.3(libmariadbclient_18)<br>
            libmariadb.so.3(libmariadbclient_18)(64bit)<br>
            libmariadb.so.3(libmysqlclient_18)<br>
            libmariadb.so.3(libmysqlclient_18)(64bit)<br>
            mariadb-connector-c = 3.1.8-1.fc33<br>
            mariadb-connector-c(x86-32) = 3.1.8-1.fc33<br>
            mariadb-connector-c(x86-64) = 3.1.8-1.fc33<br>
            <div> </div>
            <div>Thanks,</div>
            <div>Richard</div>
          </div>
        </div>
        <br>
      </blockquote>
      <p><br>
      </p>
      <p>Opensuse Tumbleweed and 15.1 also use the mariadb one, I've
        seen no issues.</p>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
    </blockquote>
    <p>This may be a solution. I have not investigated it. MythTV may
      have to be rebuilt using the mariadb lib?</p>
    <p> The default Ubuntu install uses mysql. Only those who have
      manually installed mariadb would be affected by this issue.<br>
    </p>
    <p><br>
    </p>
  </body>
</html>