Claudius,
We have a similar setup (last version of Ubuntu and a slightly older
version of mysql server) but it is working. Is your desired directory
on the same drive?
If you think AppArmor is the culprit you might want to switch the
profile for mysqld to complain as described here:
https://help.ubuntu.com/11.10/serverguide/C/apparmor.html
That will make AppArmor only complain and not actually stop any
perceived naughtiness that mysqld is up to.
For reference, I set ours up to deposit all the data onto a separate
drive mounted at "/data" in a directory called mysql. You need to
make sure that mysql has the propper permissions to the desired
directory as well. After disabling AppArmor, I changed our mysqld
AppArmor profile by adding a couple lines to the profile
usr.sbin.mysqld:
/usr/sbin/mysqld {
...
/data/mysql/ r,
/data/mysql/** rwk,
...
}
Then I reloaded AppArmor and the system was happy again.
If you are having issues with the my.cnf file I found it a bit easier
to manipulate them using MySQL Workbench via the server administration
it provides, though all I needed to change in my.cnf was the binding
address (for external access) and the data directory, which you have
already done.
Let me know if you're still having issues!
-Ben