kimchi Installation freeze during configure on 16.04

[Mirto Silvio Busico]

Step to reproduce:

1) install Kubuntu 16.04 64Bit
2) apt-get update and apt-get dist-upgrade
3) reboot
4) apt-get install kimchi

The installation freeze at the last step (configuration)

Tried to reboot and issue
sudo dpkg --configure -a --force-all

The operation freeze and if you issue a ctrl+C you see

Configurazione di kimchi (1.5.0-0ubuntu1)...
^Cdpkg: errore nell'elaborare il pacchetto kimchi (--configure):
 sottoprocesso installato script di post-installation interrotto
Si sono verificati degli errori nell'elaborazione:
 kimchi

I was unable to install kimchi

[Launchpad Janitor (janitor)]

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

[gunxfight (chrisonline1991)]

I had this same problem on Ubuntu 16.04 64bit. I upgraded from Ubuntu 14.04.5 if that matters.

Right before "Setting up Kimchi (1.5.0ubuntu1) ..." I get this:

"""
W: plymouth: The plugin label.so is missing, the selected theme might not work as expected.
W: plymouth: You might want to install the plymouth-themes and plymouth-label package to fix this.
"""

I'm also not able to ctrl+c out of it, however that could be because I'm sshed into the server using cygwin terminal and/or using tmux.

[gunxfight (chrisonline1991)]

I had to get kill apt-get to get out of the install. When doing so I found this process still running:

/bin/sh /var/lib/dpkg/info/kimchi.postinst configure

[gunxfight (chrisonline1991)]

I followed this link and was able to fix the issue: https://github.com/kimchi-project/kimchi/issues/821

Basically you need to edit /lib/systemd/system/kimchi.service and change

Requires=libvirtd.service
After=libvirtd.service

To:

Requires=libvirt-bin.service
After=libvirt-bin.service

and edit /etc/pam.d/kichmi and change:

auth sufficient pam_succeed_if.so user ingroup libvirt

To:

auth sufficient pam_succeed_if.so user ingroup libvirtd

[slappinsuspenders (slappinsuspenders)]

May I piggy-back here to ask how I gain ownership of that file?

[Vance Morris (vmorris)]

@slappinsuspenders you'll need to edit it with sudo, or perhaps you'd like to really own it? "sudo chown <filename>" would do this, but I don't think this is what you want to achieve...

Just "sudo vim <filename>" :D