I took a little overview, these services are usually only needed for special cases (locks for e.g. net disks), and almost never configured - so this was undetected for quite a while.
Xenial: started, /etc/default/virtlockd installed Zesty: started, /etc/default/virtlockd not installed Artful: not started, /etc/default/virtlockd not installed Debian (Buster): not started, /etc/default/virtlockd not installed I brought a fix into Debian a while ago: 3.5.0-1: * [dd2991f] Ship default file for virtlockd * [c3b6ff2] Ship default file for virtlockd (Closes: #863648) It was not considered SRU worthy (given how few edit the file and could just create it), but but in addition it seems lost or inactive in Artful. For the service not being started that begins in Artful. So this came in via Debian and we picked it up not realizing the issue so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729516 Title: virtlockd not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1729516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
