Thanks for taking to prepare a debdiff and conduct some testing. However I'm not comfortable with releasing an update that changes the signal handling, especially removing one.
I'd like to understand *why* is mysqld crashing in the first place. It seems that mythbackend is making mysqld crash. Could you enable the general query log (http://dev.mysql.com/doc/refman/5.0/en/query- log.html) and try to figure out which SQL statement makes the daemon crash? If the proposed debdiff fixes the issue it means that something during the boot process sends a HUP signal to the mysql_safe process. I'd like to figure out what is sending the HUP signal to mysql_safe. ** Changed in: mysql-dfsg-5.0 (Ubuntu Jaunty) Status: Fix Committed => Confirmed ** Tags removed: verification-needed -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
