[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1010576: akonadi cannot kill mysql due to apparmor rules



Hi,

the fix is already in master, it is actually just a typo in the profile name:
https://invent.kde.org/pim/akonadi/-/commit/
a6fb4c7de13eed9d90237388113425413bf4d733

that may be worth to backport.
 
> If I set akonadi's profile to complain instead of enforce, akonadi can
> kill mysql ok:
> 
> sudo aa-complain /etc/apparmor.d/usr.bin.akonadiserver
> sudo systemctl reload apparmor.service

you don't need to restart apparmor after set akonadiserver to complain mode.


> Somehow mysql should be running in the mysqld_akonadi profile but it is
> running in fact unconstrained and therefore akonadiserver is not allowed
> to send a signal to it. Don't know how to fix that, though.

I see the same apparmor issue, but Akonadi is still not able to kill mariadb 
process.

 
> I suspect the fact that mysql hangs after suspend/resume is a different
> bug in mysql.

yepp - But I have no idea how to debug this.

regards,

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: