Interesting, so it really isn't an apparmor deny as I first thought. It seems to reset the device a lot and then give up after a while.
You are using 19.10 already, that should clearly be new enough for 3.1 support. Unfortunately I have no 3.1 device nor a Hub (only 3.0 devs around me) to test this on my own. I'll ask a few friends, until then we might step by step try to get mroe debug data from you until we spot something. You could check out [2] and enable verbose libvirt logging. This often is really verbose, but somewhere in between one can find an error like what exactly on the USB attachment might fail. Attach the log that you generate here and maybe also mention a timestamp when you tried to attach the device so it can be found more easily in the log. P.S. It might also be worth to report it to the libvirt ML [1], quite often one recognizes the case or knows a fix already. If you happen to do so, leaving me a link here so everyone casn follow would be nice. P.P.S. there will in a few weeks be the new qemu/libvirt versions that are coming for 20.04 - would you be willing and able to test those as well or would that put your main system in a unstable state (20.04 is in development still)? [1]: https://www.redhat.com/mailman/listinfo/libvir-list [2]: https://libvirt.org/logging.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858319 Title: libvirt usb 3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1858319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
