console-setup postinstall never ends in Ubuntu 16.04

Bug #1571025 reported by Luis Mondesi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Today while doing a normal `apt-get upgrade`, the latest console-setup package for Ubuntu 16.04 got stuck since 11:10 until about 14:25h when I realized it was still running and I had to kill the process manaully.

$> sudo apt-get upgrade
...
Setting up console-setup (1.108ubuntu14) ...

$> ps -ef | grep console-setup
...
       PID PPID USER NI RSS S STIME COMMAND
24542 24482 root 0 1812 S 11:10 /bin/sh /var/lib/dpkg/info/console-setup.postinst configure 1.108ubuntu13
24482 22027 root 0 18320 S 11:10 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/console-setup.postinst configure 1.108ubuntu13
...
$> date
Fri Apr 15 14:25:11 EDT 2016

$> apt-cache show console-setup
Package: console-setup
Priority: important
Section: utils
Installed-Size: 437
Maintainer: Ubuntu Installer Team <email address hidden>
Original-Maintainer: Debian Install System Team <email address hidden>
Architecture: all
Version: 1.108ubuntu14

Revision history for this message
Luis Mondesi (lemsx1) wrote :

Ran the same `sudo apt-get upgrade` after updating my lists and got the same behavior:

$> lsproc console-setup
  PID PPID USER NI RSS S STIME COMMAND
22693 22692 root 0 18628 S 14:27 /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/console-setup.postinst configure 1.108ubuntu13
22692 18652 root 0 13864 S 14:27 /usr/bin/dpkg --status-fd 47 --configure console-setup:all ubuntu-minimal:amd64 libssl-doc:all libssl1.0.0:amd64 libssl1.0.0:i386 libssl-dev:amd64 openssl:amd64 libwnck-3-common:all libwnck-3-0:amd64 gir1.2-wnck-3.0:amd64
22752 22693 root 0 1640 S 14:27 /bin/sh /var/lib/dpkg/info/console-setup.postinst configure 1.108ubuntu13

Revision history for this message
Luis Mondesi (lemsx1) wrote :

This is the strace

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

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

Changed in console-setup (Ubuntu):
status: New → Confirmed
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.