After some more thinking I think it could be worth unblocking the mysql
migration sooner than later. My rationale is explained here:
https://code.launchpad.net/~legovini/britney/mysql-8/+merge/384720
Weighting it is up to the release team.
--
You received this bug notification because you are
Thanks Lars. I dropped the britney hint MP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-
set,
@Otto The usr/share/mysql/charsets/Index.xml file from mysql 5.7 (or
older versions of 8.0) does not cause this issue. MySQL does not and has
never had any MariaDB compatibility, and can not be expected to work
properly if internal MySQL files are replaced by ones from MariaDB.
That said, this is
Has anybody tested using libmariadb3? There are no backwards
incompatible changes in libmariadb3 - MythTV should run just fine with
libmariadb3.
If there will be backwards incompatible updates the library will be
dumped to libmariadb3. If Oracle MySQL has now in libmysqlclient21
version 8.0.20
I would suggest that you put proper debian/control conflicts for
libmysqlclient21 to signify that things that worked with
libmysqlclient20 might stop working. If libmysqlclient21 is incompatible
with libmysqlclient20 ways of doing things, it will automatically be
incompatible with any previous
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mariadb-10.3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Thanks for the help! I'm running build with the patch I have to
prevent the segfault as well, so it shouldn't be quite as vulnerable to
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
As this seems to be a bug on the mariadb side rather than on the mysql
side, I filed this MP to unblock the groovy mysql-8 migration:
https://code.launchpad.net/~legovini/britney/mysql-8/+merge/384660
Let's see if I've got all the bits right :)
--
You received this bug notification because you
The root cause of this problem seems to be the fact that
libmysqlclient21 from mysql-8.0 tries to use charset files from mariadb,
but they are not compatible with it and lead to a segfault. More details
in this Debian bug I filed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961672
** Also
This is preventing mysql-8.0 (8.0.20-0ubuntu1) from migration from
groovy-proposed to groovy, so I added the update-excuse tag. I also
added the regression-update tag as this bug landed in Focal with the
8.0.20-0ubuntu0.20.04.1 security upload of mysql-8.0.
--
You received this bug notification
** Tags added: update-excuse
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes
Simply doing "if (cs && cs->coll && cs->coll->uninit) {" fixes the
segfault in the test case, so I just need to check with a dev if that's
a sane way to handle this (or if I'd just be hiding the symptom)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for looking into it more. This might be what the devs need, so
I'll pass it on (I've been trying to figure out exactly what causes it
to work with upstream's package (or a libmysqlclient21 built just
plainly with cmake, make, make install), but no luck.
--
You received this bug
Sorry I don't have an Oracle login to report the bug upstream and don't
want one. Hopefully someone else can report it to them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
From:
bool init_compiled_charsets(myf flags MY_ATTRIBUTE((unused)))
there are charsets being added to "all_charsets" (global variable)
through:
void add_compiled_collation(CHARSET_INFO *cs) {
DBUG_ASSERT(cs->number < array_elements(all_charsets));
all_charsets[cs->number] = cs;
From:
bool init_compiled_charsets(myf flags MY_ATTRIBUTE((unused)))
there are charsets being added to "all_charsets" (global variable)
through:
void add_compiled_collation(CHARSET_INFO *cs) {
DBUG_ASSERT(cs->number < array_elements(all_charsets));
all_charsets[cs->number] = cs;
I've done a little more debugging. Hopefully this output from a gdb
session helps.
The segfault occurs here because in this case cs->coll is NULL
https://github.com/mysql/mysql-server/blob/8.0/mysys/charset.cc#L925
I don't know where the latin2_general_nopad_ci character set is coming
from since
This is probably the same as https://bugs.launchpad.net/ubuntu/+source
/qtbase-opensource-src/+bug/1877183
I'll experiment a bit and see if maybe there are any compiler flags we
use that are causing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hm, if I install upstream's libmysqlclient21_8.0.20, there's no
segfault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21
Thanks for the test case. Connecting to a mariadb server isn't supported
(and thus not tested at all), but segfaulting is pretty bad, so
hopefully we can get this fixed with all the information you've
provided.
It's important to note, though, that MariaDB and MySQL diverge more and
more with
Attached a bt full of the crash
** Attachment added: "bt_full.txt"
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+attachment/5371665/+files/bt_full.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Attached is a new reproducer that just uses the libmysqlclient directly
without using Qt.
It's based on an example from a zetcode tutorial.
I used this to compile it :-
gcc mysql_test.c -o mysql_test -I/usr/include `mysql_config --cflags --libs`
The interesting thing is if you comment out both
I can confirm that the test program above causes segfault with current
libmysqlclient21 but not with previous version, using mariadb as the
server.(sorry, it took me a while to get all the dependencies together
to compile and execute the program.)
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-8.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
My tests were done with a remote server running mariadb-server-10.1
running on a default Ubuntu 18.04.4 LTS server.
The client side was running on Ubuntu 19.10 but others have also
reported problems on 20.04 LTS.
As Kim has said downgrading to libmysqlclient21 back to 8.0.17 does fix
the
Is this when using MariaDB or when using MySQL?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes mythtv-
set,
Sample run under gdb with backtrace showing the crash with the test app.
** Attachment added: "backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877504/+attachment/5370903/+files/backtrace.txt
--
You received this bug notification because you are a member of Ubuntu
This simple test application may be easier for you to reproduce this
bug.
You will have to change the host,user name,password and database name to
valid options for you but once you do that the test app will crash every
time it exits.
** Attachment added: "Simple test app using QT to reproduce
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
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877504
Title:
new version of libmysqlclient21 8.0.20-0ubuntu0.20.04.1 causes
30 matches
Mail list logo
