The above workaround isn't enough to totally resolve the issues with
AppArmor and this application inside LXD.  I also had to switch to aa-
complain for PostgreSQL migration so features will have to be thoroughly
tested to identify it.  I'm willing to setup a secondary instance to do
any testing that is necessary but I don't know anything about AppArmor
to fix the profile.

Added note: It seems that migration may be broken in Quassel-Core in
general but I'm reporting that on their tracker as it seems to be a bug
on their end but setting up for PostgreSQL seemed to work in complain
mode.  It is untested in enforce mode.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.

  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
Status in apparmor package in Ubuntu:
Status in quassel package in Ubuntu:

Bug description:
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
  container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to