[Bug 2019203] Re: mysql 8.0.33 binary crashes on startup on armhf

[Mitchell Dzurick]

Hello, This bug has stayed open for a little bit because of it being
tagged affecting linux.

To me it looks like this should be fixed for all our supported releases
at the moment (Oracular,Noble,Jammy,Focal) since the earliest version in
Focal is 8.0.37-0ubuntu0.20.04.3.

I'm tagging Linux as invalid since this shouldn't impact that (to my
understanding), feel free to assign it to linux if my understanding is
incorrect.

** Changed in: linux (Ubuntu Jammy)
       Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu Focal)
       Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/2019203

Title:
  mysql 8.0.33 binary crashes on startup on armhf

Status in MySQL Server:
  Unknown
Status in glibc package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in mysql-8.0 package in Ubuntu:
  Fix Released
Status in glibc source package in Focal:
  Invalid
Status in linux source package in Focal:
  Won't Fix
Status in mysql-8.0 source package in Focal:
  Fix Released
Status in glibc source package in Jammy:
  Invalid
Status in linux source package in Jammy:
  Won't Fix
Status in mysql-8.0 source package in Jammy:
  Fix Released
Status in glibc source package in Kinetic:
  Invalid
Status in linux source package in Kinetic:
  Won't Fix
Status in mysql-8.0 source package in Kinetic:
  Fix Released
Status in glibc source package in Lunar:
  Invalid
Status in linux source package in Lunar:
  Won't Fix
Status in mysql-8.0 source package in Lunar:
  Fix Released
Status in glibc source package in Mantic:
  Invalid
Status in linux source package in Mantic:
  Won't Fix
Status in mysql-8.0 source package in Mantic:
  Fix Released

Bug description:
  From mantic autopkgtests:

  Setting up mysql-server-8.0 (8.0.33-0ubuntu2) ...
  update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
  Renaming removed key_buffer and myisam-recover options (if present)
  ERROR: Unable to start MySQL server:
  2023-05-09T17:23:22Z UTC - mysqld got signal 11 ;
  Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
  BuildID[sha1]=facf2109b23102b169b11737a1fc4bd99de4be1b
  Thread pointer: 0x0
  Attempting backtrace. You can use the following information to find out
  where mysqld died. If you see no messages after this, something went
  terribly wrong...
  stack_bottom = 0 thread_stack 0x100000
  /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x205e0bc]
  /usr/sbin/mysqld(print_fatal_signal(int)+0x29d) [0x1533ba2]
  /usr/sbin/mysqld(handle_fatal_signal+0x71) [0x1533c9e]
  /lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6e7b750]
  /usr/sbin/mysqld(memory::Aligned_atomic<long>::Aligned_atomic()+0x51) [0x1e0d49a]
  /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x1e0d6c4]
  /usr/sbin/mysqld(delegates_init()+0x37) [0x1e0d804]
  /usr/sbin/mysqld(+0x8ec92c) [0x139592c]
  /usr/sbin/mysqld(mysqld_main(int, char**)+0x1959) [0x139a22a]
  /lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6e6b7da]
  /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6e6b87e]
  The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  information that should help you find out what is causing the crash.
  Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues.
  Once the problem is resolved, run apt-get --fix-broken install to retry.
  dpkg: error processing package mysql-server-8.0 (--configure):
   installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/2019203/+subscriptions