I will try to investigate what happened that the socket path was used instead of listen (maybe in one of the debugging attempts, I did not supply the listen parameter ?). I'm sorry to not be able to provide an immediate answer on this one since I can't reach my test system at the moment since I'm currently on a different network.
But AFAIK the /etc/apparmor.d/libvirt/libvirt-<uuid>.files is autogenerated. IMHO if its possible to have a socket option it should parse and add the file to the appropriate profile. Adding it by hand gets overwritten once you stop and start the VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069534 Title: libvirt doesn't include *.vnc files with apparmor profiles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1069534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
