Comment 3 for bug 322647

Revision history for this message
Mathias Gug (mathiaz) wrote :

The relevant messages from the log are:

Setting up mysql-server-5.0 (5.0.67-0ubuntu6) ...

 * Stopping MySQL database server mysqld 
[ OK ]

Reloading AppArmor profiles /sbin/apparmor_parser: Unable to replace "/usr/share/gdm/guest-session/Xsession". Profile version not supported by Apparmor module

 Profile /etc/apparmor.d/gdm-guest-session failed to load

/sbin/apparmor_parser: Unable to replace "/usr/lib/cups/backend/cups-pdf". Profile version not supported by Apparmor module

 Profile /etc/apparmor.d/usr.sbin.cupsd failed to load

/sbin/apparmor_parser: Unable to replace "/usr/sbin/mysqld". Profile version not supported by Apparmor module

 Profile /etc/apparmor.d/usr.sbin.mysqld failed to load

 Skipping profile /etc/apparmor.d/usr.sbin.mysqld-akonadi.dpkg-new

: Warning.

 * Starting MySQL database server mysqld 
[fail]

invoke-rc.d: initscript mysql, action "start" failed.

dpkg: error processing mysql-server-5.0 (--configure):

 subprocess post-installation script killed by signal (Interrupt)

Setting up libhtml-template-perl (2.9-1) ...

The apparmor related messages are probably not responsible for the package failure. It seems that the mysql-server hasn't been able to be started. Could you post the content of /var/log/daemon.log at the time of the upgrade?