This should definitely be added to the release notes or fixed, but it appears that the problem can be resolved by performing the workaround in the original description.
Also, just doing something to interact with the database (like schedule a dummy recording), always worked to fix the problem for me before I applied the workaround. -- 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 Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
