Hi, the corresponding AppArmor policy is shipped by akonadi packages and maintained by the Debian/Kubuntu Qt/KDE Maintainers, so I'm relaying this info there.
Dear Debian/Kubuntu Qt/KDE Maintainers, see Christian Boltz reply on this thread :) Sedat Dilek (2020-09-03): > I switched over the database-backend of Akonadi-Server in KDE/Plasma > from MySQL to PostgreSQL. > > In my dmesg logs I see: > > [ DMESG ] > > root# LC_ALL=C dmesg -T | egrep apparmor | grep akonadi > [Thu Sep 3 15:27:34 2020] audit: type=1400 audit(1599139654.969:28): > apparmor="DENIED" operation="file_mmap" info="Failed name lookup - > disconnected path" error=-13 profile="postgresql_akonadi" name="" > pid=2126 comm="postgres" requested_mask="wr" denied_mask="wr" > fsuid=1000 ouid=1000 > > I followed the Debian AppArmor wiki to get a first impression of how > AppArmor works. > > There exists a "postgresql_akonadi" AA-profile, but cannot classify > what the above information from dmesg says to me. > > Just for the sake of completeness: > I have created a "dileks" PostgreSQL database-user with > role/permissions "createdb" and within my user-account a new database > via "createdb akonadi-dileks". > > Can you give a hand?
