Hi Simon, UEFI Lenovo desktop PC is what I'm running Xenial on.
I'm the new maintainer for network-manager-l2tp VPN plugin for NetworkManger : https://github.com/nm-l2tp/network-manager-l2tp I started an IPSec/L2TP connection using network-manager-l2tp before issuing the 'sudo ipsec status'. So it may be something with network- manager-l2tp IPSec connections that triggers the issue. I've encountered a few scenarios with strongswan and network-manager-l2tp where an IPSec connection hasn't been established yet, and was hoping to check the connection status in the code by invoking 'ipsec status {connection name}', before it tries to do a L2TP connection. Tommorow I'll try and do a bit more testing on other Xenial installs and maybe try an IPSec connection without network-manager-l2tp on the PC with the issue to see if I can reproduce. Will get back to you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1587886 Title: strongswan ipsec status issue with apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1587886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
