I had this problem on a vanilla update from jaunty to karmic. Everything seemed to update okay, but later when I went to run a MySQL backup I couldn't do it. It was only then that I realized that karmic included an "upgrade" to MySQL 5.1. The upgrade had not completely worked.
I went in and tried reinstalling from Synaptic, and that's when I got this error. This caused me a lot of trouble. Not finding the exact cause of the error, I tried going back to 5.0, and ultimately purged MySQL and tried a fresh install. Even that didn't work. Of course purging caused many of my installed applications to be removed, so it's been an ongoing hassle.
The GRUB_CMDLINE_LINUX_DEFAULT="quiet splash apparmor=0" work-around allowed me to install and configure MySQL 5.1. At this point things are looking good, although my testing has been very limited. I haven't looked at what went wrong with apparmor; perhaps someone here will explain it and save me the trouble.
This is the second update in a row that had some major failure for me (jaunty and karmic). I am a technical user, and I keep my systems in good order, so it is disappointing that we are seeing this sort of update trouble. I understand that upgrades are a major support hassle, but if we want common users to embrace Ubuntu we are going to need a smooth upgrade process. Perhaps the six month upgrade cycle is too aggressive?
I had this problem on a vanilla update from jaunty to karmic. Everything seemed to update okay, but later when I went to run a MySQL backup I couldn't do it. It was only then that I realized that karmic included an "upgrade" to MySQL 5.1. The upgrade had not completely worked.
I went in and tried reinstalling from Synaptic, and that's when I got this error. This caused me a lot of trouble. Not finding the exact cause of the error, I tried going back to 5.0, and ultimately purged MySQL and tried a fresh install. Even that didn't work. Of course purging caused many of my installed applications to be removed, so it's been an ongoing hassle.
The GRUB_CMDLINE_ LINUX_DEFAULT= "quiet splash apparmor=0" work-around allowed me to install and configure MySQL 5.1. At this point things are looking good, although my testing has been very limited. I haven't looked at what went wrong with apparmor; perhaps someone here will explain it and save me the trouble.
This is the second update in a row that had some major failure for me (jaunty and karmic). I am a technical user, and I keep my systems in good order, so it is disappointing that we are seeing this sort of update trouble. I understand that upgrades are a major support hassle, but if we want common users to embrace Ubuntu we are going to need a smooth upgrade process. Perhaps the six month upgrade cycle is too aggressive?
Tom