I'm not clear on what the issue with mailman is but if removing the
LimitUIDRange option from your Apache config solves it then it's
probably expected behaviour when calling a setuid root executable
(Exim?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Changed in: mailman (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349433
Title:
AppArmor breaks seccomp @ Apache mpm-itk
To manage notifications abo
Note that the 'Operation not permitted' error in the original
demonstration is desired behaviour- when this does /not/ happen the
seccomp filter is not working as intended. It's not clear to me what
problem you're see'ing but it /could/ be an affect of the seccomp filter
in mpm-itk (governed by the
also affect x86 installations
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/960757
Title:
whoopsie crashed with SIGSEGV in g_object_newv()
To manage notifications about this bug go to:
https://bugs