package openvpn 2.4.0-4ubuntu1.3 failed to install

Bug #1703266 reported by Matthew D. Mower
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openvpn (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Ubuntu GNOME 17.04 64bit (freshly installed today, no packages from non-standard repositories, aside from Google Chrome).

Installation hangs here:

mdmower@YOGA14:~$ sudo apt purge network-manager-openvpn-gnome
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libpkcs11-helper1 network-manager-openvpn openvpn
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  network-manager-openvpn-gnome*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 479 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 186375 files and directories currently installed.)
Removing network-manager-openvpn-gnome (1.2.6-2ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Setting up openvpn (2.4.0-4ubuntu1.3) ...

The following processes were running during the hang:

mdmower@YOGA14:~$ sudo ps aux | grep openvpn
root 3672 0.0 0.0 61064 3920 pts/0 S+ 16:29 0:00 sudo apt install openvpn
root 3673 13.1 0.4 118256 74692 pts/0 S+ 16:29 0:01 apt install openvpn
root 3715 2.2 0.1 62444 17020 pts/1 S+ 16:29 0:00 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/openvpn.postinst configure
root 3722 0.0 0.0 4496 760 pts/1 S+ 16:29 0:00 /bin/sh /var/lib/dpkg/info/openvpn.postinst configure
root 3728 0.0 0.0 4496 1668 pts/1 S+ 16:29 0:00 /bin/sh /usr/sbin/invoke-rc.d openvpn cond-restart
root 3749 0.0 0.0 4496 1712 pts/1 S+ 16:29 0:00 /bin/sh -e /etc/init.d/openvpn cond-restart
mdmower 3760 0.0 0.0 14240 916 pts/2 S+ 16:29 0:00 grep --color=auto openvpn

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: openvpn 2.4.0-4ubuntu1.3
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 libpkcs11-helper1:amd64: Install
 openvpn:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Jul 9 16:30:13 2017
ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
InstallationDate: Installed on 2017-07-09 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt 1.4
SourcePackage: openvpn
Title: package openvpn 2.4.0-4ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Matthew D. Mower (mdmower) wrote :
Revision history for this message
Matthew D. Mower (mdmower) wrote :

I reinstalled Ubuntu GNOME (I had barely started on a fresh installation when this issue arose), and installed openvpn first thing. Installation succeeded without issue. I won't be able to reproduce this issue, so feel free to mark it 'invalid'.

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Unfortunately the attached logs don't help much. A full ps output, like ps fauxw, would have perhaps shown in more detail what was going on, which process called what, etc.

I'll mark this bug as incomplete for now. If it happens again, feel free to update it. Otherwise, it will expire on its own after a while.

Thanks!

Changed in openvpn (Ubuntu):
status: New → Incomplete
Revision history for this message
Alexander Lasley (lasleyaj) wrote :

I am also experiencing this bug on a system installed last night. I got a hang while running 'apt install network-manager-openvpn-gnome', gave up and killed the process, and I am now getting a hang again while running 'dpkg --configure -a'.

'ps fauxw' seems to indicate that the post-install script is waiting on 'plymouth --ping'. And indeed if I run that command separately, it does not return.

Revision history for this message
Alexander Lasley (lasleyaj) wrote :

This appears to be fixed with the latest version of the plymouth package. It turns out my system was not entirely up-to-date when I tried to install network-manager-openvpn-gnome.

For those who make it here from a search engine, you can make the post-install script complete by finding the pid of 'plymouth --ping' and killing it. The script will retry a few times but give up eventually. Then you should be able to get back to a state where you can upgrade the rest of your packages before retrying this one.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in openvpn (Ubuntu):
status: Incomplete → Expired
Revision history for this message
iroli (roland-lezuo) wrote :

bug still present in 17.10.
relevant ps fauxw output here:

root 11199 0.0 0.0 88768 4940 pts/1 S+ 21:31 0:00 | | \_ sudo apt install network-manager-openvpn
root 11200 0.3 0.4 128036 75684 pts/1 S+ 21:31 0:00 | | \_ apt install network-manager-openvpn
root 11252 0.0 0.0 31528 9240 pts/4 Ss+ 21:31 0:00 | | \_ /usr/bin/dpkg --status-fd 50 --configure --pending
root 11263 0.0 0.1 71300 18948 pts/4 S+ 21:31 0:00 | | \_ /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/openvpn.postinst configure
root 11270 0.0 0.0 4608 908 pts/4 S+ 21:31 0:00 | | \_ /bin/sh /var/lib/dpkg/info/openvpn.postinst configure
root 11276 0.0 0.0 4608 1712 pts/4 S+ 21:31 0:00 | | \_ /bin/sh /usr/sbin/invoke-rc.d openvpn cond-restart
root 11300 0.0 0.0 4608 1716 pts/4 S+ 21:31 0:00 | | \_ /bin/sh -e /etc/init.d/openvpn cond-restart
root 11305 0.0 0.0 12936 924 pts/4 S+ 21:31 0:00 | | \_ plymouth --ping

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.