Summary: | After upgrade to Applications 19.04.3: Akonadi can't connect to local MySQL server any more | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | tsa |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | CC: | brent, fknghostile, stefan.galinski |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
tsa
2019-07-12 07:02:17 UTC
Same here, on two similarly configured machines all PIM applications were rendered unusable. Stopgap solution that worked for me: install akonadi-backend-sqlite and then remove akonadi-backend-mysql. Perhaps I should have added that I tried to fixes permissions for /var/lib/mysql (if you run /usr/bin/akonadiserver you'll get an error about that), to remove ~/.local/share/akonadi, but nothing helped or led to more info (to me). Same problem here. I've tried deleting akonadi's configs and folders.... and making a clean install of my packages...but still refusing to connect. I solved the problem. It'a an AppArmor issue. You need to edit your AppArmor configuration. vim /etc/apparmor.d/usr.sbin.mysqld-akonadi The content looks like this from the beginning. I only added a lot's of stuff at the top. ``` # vim:syntax=apparmor #include <tunables/global> /usr/sbin/mysqld-akonadi { #include <abstractions/base> /usr/sbin/mysqld-akonadi r, /usr/sbin/mysqld cx, profile /usr/sbin/mysqld { /run/user/1000/akonadi/default/mysql.pid rwmk, /run/user/1000/akonadi/default/mysql.socket rwmk, /run/user/1000/akonadi/default/mysql.socket.lock rwmk, /sys/devices/system/node/* r, /sys/devices/system/node/ r, /etc/mysql/* r, /etc/mysql/mysql.conf.d/ r, /etc/mysql/mysql.conf.d/* r, /sys/devices/system/node/node0/meminfo r, [more lines] ``` Afterwards reload the apparmor configuration for the file. apparmor_parser -r /etc/apparmor.d/usr.sbin.mysqld-akonadi You can restart Akonadi via the Akonadi console or a system restart now. At least it worked for me and I'm fine again. :-) I think updates were just released that fix it. As stated in comment#4, this is an apparmor issue. (In reply to Stefan Galinski from comment #4) > I solved the problem. It'a an AppArmor issue. > > You need to edit your AppArmor configuration. > > vim /etc/apparmor.d/usr.sbin.mysqld-akonadi > > The content looks like this from the beginning. I only added a lot's of > stuff at the top. > > ``` > # vim:syntax=apparmor > > #include <tunables/global> > > /usr/sbin/mysqld-akonadi { > #include <abstractions/base> > /usr/sbin/mysqld-akonadi r, > /usr/sbin/mysqld cx, > > profile /usr/sbin/mysqld { > /run/user/1000/akonadi/default/mysql.pid rwmk, > /run/user/1000/akonadi/default/mysql.socket rwmk, > /run/user/1000/akonadi/default/mysql.socket.lock rwmk, > /sys/devices/system/node/* r, > /sys/devices/system/node/ r, > /etc/mysql/* r, > /etc/mysql/mysql.conf.d/ r, > /etc/mysql/mysql.conf.d/* r, > /sys/devices/system/node/node0/meminfo r, > [more lines] > ``` > > Afterwards reload the apparmor configuration for the file. > > apparmor_parser -r /etc/apparmor.d/usr.sbin.mysqld-akonadi > > You can restart Akonadi via the Akonadi console or a system restart now. > > At least it worked for me and I'm fine again. :-) I don't have any "usr.sbin.mysqld-akonadi" in my KDE Neon. Finally i've created (i think) usr.sbin.mysqld-akonadi file with: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.mysqld-akonadi and fix the trouble as is suggested. Thank you! |