The two most similar working/failing sockets have no diff that IMHO would explain the behavior: root@f2:~# diff -Naur /lib/systemd/system/libvirtd.socket /lib/systemd/system/libvirtd-ro.socket --- /lib/systemd/system/libvirtd.socket 2020-03-20 09:34:19.000000000 +0000 +++ /lib/systemd/system/libvirtd-ro.socket 2020-03-20 09:34:19.000000000 +0000 @@ -1,12 +1,14 @@ [Unit] -Description=Libvirt local socket +Description=Libvirt local read-only socket Before=libvirtd.service +BindsTo=libvirtd.socket +After=libvirtd.socket [Socket] # The directory must match the /etc/libvirt/libvirtd.conf unix_sock_dir setting # when using systemd version < 227 -ListenStream=/run/libvirt/libvirt-sock +ListenStream=/run/libvirt/libvirt-sock-ro Service=libvirtd.service SocketMode=0666
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869796 Title: vague error during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1869796/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
