A second device to add which would be in: /run/udev/data/c189:134 But only allow the first device in the apparmor rules. Only if that would trigger a deny on the second attach it would help to add the second rule later. And it does not show up, so a new rule on the second attach would not have helped.
Maybe libusb tries to be smart and only rescan if devices where plugged/unplugged. So I retested 1. second device physically detached 2. attach first device to guest 3. attach second device physically to machine 4. attach second device to guest Still no re-read. So there is a qemu issue related to all of it that libusb context would have to be refreshed. Until that is fixed we can only go for ther static rules. Need to spawn a few discussions in both upstreams about that. P.S. the [1] of comment #16 should have been: [1]: http://elixir.free-electrons.com/linux/latest/source/Documentation/admin-guide/devices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552241 Title: libvirt-bin apparmor settings for usb host device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1552241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
