Comment 5 for bug 1951903

We know that libvirtd can't be removed as it is early in the postrm and at this time we know it will trigger:

$ delgroup libvirtd
/usr/sbin/delgroup: `libvirt-dnsmasq' still has `libvirtd' as their primary group!

But removing it afterwards when it can be removed only ends up breaking slightly different:

RET=20 Unsupported command "the" (full line was "The group `libvirtd' does not exist.") received from confmodule.

Maybe the sysuser config of libvirtd makes debconf want to remove it, but in the combination we have in place this fails and that makes it fail badly. I need to track this down in more detail, but this week will unlikely find time for it.

As a workaround for now, I found that removing/purging libvirt-daemon-system once more passed fine so you can just re-run whatever you did to trigger the purges and the second time it should pass.