>From your log: Jan 24 19:08:23 hostname systemd[1]: virtlogd.socket: Socket service virtlogd.service already active, refusing. Jan 24 19:08:23 hostname systemd[1]: Failed to listen on Virtual machine log manager socket. Jan 24 19:08:23 hostname systemd[1]: Dependency failed for Virtual machine log manager.
This later makes the actual service fail: virtlogd.service: Job virtlogd.service/start failed with result 'dependency' But that is not what usually happens, I've seen so many of these upgrades - something has to be uncommon at this installation and to debug we need to find what it is. Otherwise there is not a lot that can be actioned upon. If not having a lot of custom config maybe you want to purge/reinstall libvirt* packages. Otherwise please have a look why that virtlogd.socket is not starting. Maybe there is a zombie process or anything else blocking resources the service needs to open the socket? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745193 Title: package libvirt-daemon-system 3.6.0-1ubuntu6 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1745193/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
