Hi, there is a suspicious entry in the log > debconf: unable to initialize frontend: Passthrough > debconf: (Cannot connect to /run/user/1000/pk-debconf-socket: No such file or > directory at (eval 18) line 3.) > debconf: falling back to frontend: Noninteractive
I'm not sure what this is about but will add a dconf task to be considered in that context. Further down I see a more libvirt related thing: > Failed to reload virtlogd.service: Transaction for virtlogd.service/reload is > destructive (virtlogd.service has 'stop' job queued, but 'reload' is included > in transaction). > See system logs and 'systemctl status virtlogd.service' for details. That seems to me as some state is not progressing as expected. The package is only using the common means that the dh_* tools provide to control these services. In general I'd have two questions: 1. before/after this failure, does virtlogd.service start/stop fine or might it be a misconfiguration that breaks it. If so then that has to be resolved as package upgrades will need to be able to restart services. 2. as the log says, is there anything useful in "systemctl status" or maybe a full "journalctl -ux" that could point to the root cause? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928835 Title: package libvirt-daemon-system 6.0.0-0ubuntu8.9 failed to install/upgrade: installed libvirt-daemon-system package post- installation script subprocess returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1928835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
