Basak. You were wrong at the beginning and your still wrong. The bug is
mysql and apparmor dont work together. Period. I havent had any problems at
all no matter what configuration i had as soon as I uninstalled mysql and
loaded another database. Please quit telling people there is nothing wrong
Sorry Robie but you are still wrong. It is a bug but mostly because mysql
is more the problem and not Ubuntu. Changing databases does fix the bug.
Changing ubuntu doesn't make the bug go away.
Gary
On Apr 21, 2017 6:39 AM, "Robie Basak" <1610...@bugs.launchpad.net>
wrote:
> I think it's time to
Hello all. I have been trying to figure out just what is going on like
all of you. The problem is that Oracle has messed with mysql to the
point that it no longer works like it should. The fix is Mariadb, or any
other database program. I'm not into conspiracies but Oracle has a
vested interest
** Changed in: apparmor/2.10
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658239
Title:
base abstraction missing glibc /proc/$pid/ things
To manage
ok. The "bug" is reproducible. It has happened on every time i have
installed ubuntu 16.04 (all iterations). It is quirky because if you do
a reboot three times in a row, the error message goes away and apparmor
allows mysql to start without any errors. on the same machine with
exactly the same
Ok. You guys have had way too long to at least post something besides
"this isn't a bug" retort to the original post. BTW, that was back in
August of last year. Most of us who have taken the time to look into
solutions to the issue would like to know that at least some programmer
somewhere in the
** Changed in: mysql-5.7 (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1610765
Title:
mysql server fails to start due to faulty apparmor profile
To
Ok Robie Basak, You can now consider the original post an official bug
report. I am getting the same log entries as Richard except the fsuid
for my server log is 107. This is the second time on version 16.04.1
and first time on 16.04.2 that this has happened. The only permanent
fix I have found
