@Richard IMHO likely a different issue. This here was of the 16.04 time and some odd ordering of the services that provided socket activation.
We don't use socket activation anymore in 19.10 therefore I'd think this would be a better a new bug. In on this new bug directly add answers to: - is that happening right after install of libvirt or later? - what does this say $ sudo systemctl status libvirtd $ sudo lsof +fg '/var/run/libvirt/libvirt-sock' - as it was important to people affected by the bug here, did restarting the libvirt service help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583688 Title: libvirt-sock not recreated on service restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
