Summary: | Akonadi server fails with MariaDB 10.5.5 | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | physkets <physkets> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | rikmills, sknauss, taeyeon |
Priority: | NOR | ||
Version: | 5.15.0 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/pim/akonadi/-/commit/3d85f3726bffe11a89f1188ecfb4b606d3375ada | Version Fixed In: | 15.5.2 |
Sentry Crash Report: |
Description
physkets
2020-08-20 17:43:56 UTC
I am not entirely sure whether this is the same issue, but the usr.bin.akonadiserver (as well as mysqld_akonadi) AppArmor profile is broken with MariaDB 10.5.x. Apparently, 10.5.x renamed all paths and executables to be mariadb-branded while the mysql versions are now symlinks (I believe the inverse was true up to 10.4.x); which messes up the Akonadi AA profiles pretty thoroughly, since AA works with paths and seems to (sensibly) always follow links for permission checks. Relevant MariaDB (server) PR: https://github.com/MariaDB/server/pull/1544 This would (at least in my case) result in EACCES when trying to start the database server: org.kde.pim.akonadiserver: process error: "execvp: Permission denied" This can be worked around by disabling AA for akonadi (sudo aa-disable /usr/bin/akonadiserver). This is on Arch Linux with Applications 20.08.0-1, Frameworks 5.73.0-1, Qt 5.15.0-4 and MariaDB 10.5.5-2. A possibly relevant merge request was started @ https://invent.kde.org/pim/akonadi/-/merge_requests/34 |