package libvirt-bin 1.3.1-1ubuntu10.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Brian Ignacio]

I installed libvirt after upgrading to Ubuntu 16 from Ubuntu 14. Never worked it. It says i modified the defaults file but i haven't.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvirt-bin 1.3.1-1ubuntu10.3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Oct 7 12:44:53 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-03-06 (214 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=16e1597b-671b-4b46-a39d-f9b44687dc40 ro quiet splash vt.handoff=7
SourcePackage: libvirt
Title: package libvirt-bin 1.3.1-1ubuntu10.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-08 (28 days ago)
modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2016-09-10T12:54:33.838339

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Christian Ehrhardt  (paelzer)]

Hi,
the automatic report lists that as modified conffile:
/etc/libvirt/qemu/networks/default.xml changed at 2016-09-10T12:54:33.838339.

Maybe you didn't change the file manually but some other tool did it?

In the log I see it trying to (re)start libvirt after the upgrade but failing:
10月 07 12:45:02 hostname libvirtd[6375]: No se pudo inicializar capa de auditoría: Permiso denegado
10月 07 12:45:02 hostname libvirtd[6375]: No se puede conectar al socket de netlink con protocolo 0: Permiso denegado
10月 07 12:45:02 hostname systemd[1]: Failed to start Virtualization daemon.
10月 07 12:45:02 hostname systemd[1]: libvirt-bin.service: Failed with result 'exit-code'.
10月 07 12:45:02 hostname systemd[1]: libvirt-bin.service: Start request repeated too quickly.

If you really made no intentional changes to the conffile I'd recommend back it up e.g.:
cp /etc/libvirt/qemu/networks/default.xml ~/backup-default.xml

Then purge and reinstall libvirt.
Be careful that I don't know what dependencies that will also uninstall.
Make sure you reinstall them as well afterwards.

It will tell you so with e.g.:
The following packages will be REMOVED:
  libvirt-bin uvtool-libvirt

So in my case uvtool-libvirt would be removed due to the dependency.

Remove it with purge like
sudo apt-get remove --purge libvirt-bin

Then install it again
sudo apt-get install libvirt-bin

After that you are surely on the default configuration and it should work.
If you are curious take a look at the diff you had:
vimdiff /etc/libvirt/qemu/networks/default.xml ~/backup-default.xml

Share what you have found and if you still think it is a bug please report the details and set it to new again.

[Launchpad Janitor (janitor)]

[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.]