This bug was fixed in the package mysql-5.5 - 5.5.20-0ubuntu1
---
mysql-5.5 (5.5.20-0ubuntu1) precise; urgency=low
* New upstream release.
* d/mysql-server-5.5.mysql.upstart: Fix stop on to make sure mysql is
fully stopped before shutdown commences. (LP: #688541) Also
possilby unrelated issue:
my mysqld does not start anymore but i see a different output in the dmesg log,
while the mysql logfiles hold no data (0 byte size) or are old.. so additional
to not being functional it does not log useful things itself. why doesn't it
log an error to error.log if it
** Branch linked: lp:ubuntu/mysql-5.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917542
Title:
cannot create socket file in /run/mysql because of apparmor profile
To manage notifications about
** Branch linked: lp:~clint-fewbar/ubuntu/precise/mysql-5.5/merge-from-
ddebian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917542
Title:
cannot create socket file in /run/mysql because of
