Hi Mathias, First of all congrats and welcome. Always great to see newcomers.
The journalctl output doesn't reveal anything we don't already know. Yes journalctl does tend to go on forever; I suppose we'd need to know more precisely when things first started going wrong in order to isolate where in journalctl any relevant error messages might be. However in looking again at your DpkgHistoryLog.txt it seems your system was already in an error state of some sort from an earlier upgrade, at least two weeks before this error got triggered. Unfortunately that log doesn't go back before Feb 1st. If you have backups of /var/log/dpkg.log.* you could scan through them for the first time that "Error: Sub-process /usr/bin/dpkg returned an error code (1)" appears. In googling for the abstractions/mysql error message Lukas spotted, I've run across other instances of people hitting it: * https://askubuntu.com/questions/1100517/why-does-apparmor-fail-after-i-install-mysql-on-18-04-1-lts * https://askubuntu.com/questions/252340/how-to-fix-apparmor-could-not-open-error-when-installing-phpmysql * https://stackoverflow.com/questions/37165586/mysql-installation-ubuntu-server-could-not-open-abstractions-mysql * https://serverfault.com/questions/1125302/ubuntu-cant-start-configure-mysql-server-after-upgrading-ubuntu-from-18-04-to-2 (These have some workarounds that people in the past have found fixed things, however I'd strongly caution that some of those commands may be inapplicable or make things worse. Make sure your system data is backed up if you attempt any of those ideas.) From these discussions, I am gleaning that uninstalling and reinstalling mysql and/or apparmor, perhaps in association with php has triggered this condition for others. Whatever the cause, this seems like a pertinent issue for the distro engineering team to investigate, but we'd need to have a better idea on what conditions led up to it. If you are able to review the above links and/or the archived dpkg.log.* files and reconstruct the steps you took that led to the first instance of the error, that would greatly help us in identifying how to reproduce it. ** Changed in: mysql-8.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098522 Title: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld in profile /etc/apparmor.d/usr.sbin.mysqld at line 9: Could not open 'abstractions/mysql' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/2098522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
