[Bug 1365939] Re: package man-db 2.6.7.1-1 trigger froze during dist upgrade from 12.04.

Jeremy Schneider 1365939 at bugs.launchpad.net
Fri Sep 19 14:38:23 UTC 2014


just in the off chance off chance that someone is watching their email
today and has suggestions for additional diagnostics info, i will leave
my system hung for a few hours before i finish the upgrade.  let me know
if you have any requests.

based on @lkalev's original bug report, and also on
http://askubuntu.com/questions/453831/help-online-upgrade-
from-12-04-to-14-04-stuck which appears to be describing the same
problem, it seems that the workaround is to just kill the "perl
frontend" process and the installation process should restart itself and
complete successfully.  i'll try this later today.

this might be a bug in the frontend upgrade script rather than man-db.
it seems that dpkg properly failed the man-db upgrade, but the frontend
program got hung after dpkg failed.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to man-db in Ubuntu.
https://bugs.launchpad.net/bugs/1365939

Title:
  package man-db 2.6.7.1-1 trigger froze during dist upgrade from 12.04.

Status in “man-db” package in Ubuntu:
  Confirmed

Bug description:
  While upgrading Ubuntu Studio from 12.04 to 14.04.1, the man-db post-
  install trigger froze and I had to kill it. After that the upgrade
  proceeded normally (I ran the man-db update manually after that, just
  in case).

  The process that I killed was blocked on 'futex_wait' (I believe it
  was a Perl script, but I forgot to save the line from the 'ps'
  output).

  Here is the relevant part of the /var/log/dist-upgrade/apt-term.log
  file:

  Preparing to unpack .../python_2.7.5-5ubuntu3_i386.deb ...
  Unpacking python (2.7.5-5ubuntu3) over (2.7.3-0ubuntu2.2) ...
  Preparing to unpack .../python-minimal_2.7.5-5ubuntu3_i386.deb ...
  Unpacking python-minimal (2.7.5-5ubuntu3) over (2.7.3-0ubuntu2.2) ...
  Processing triggers for man-db (2.6.1-2ubuntu1) ...

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **:
  /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to
  call g_type_init()

  (process:30797): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init()
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.32.4/./gobject/gtype.c:2722: You forgot to call g_type_init() at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  GLib-CRITICAL **: g_once_init_leave: assertion `result != 0' failed at /usr/lib/perl/5.18/DynaLoader.pm line 207.
  dpkg: error processing package man-db (--unpack):
   subprocess installed post-installation script was killed by signal (Terminated)
  Processing triggers for doc-base (0.10.3) ...
  Processing 2 changed doc-base files...
  Registering documents with scrollkeeper...
  Processing triggers for desktop-file-utils (0.20-0ubuntu3) ...
  Errors were encountered while processing:
   man-db
  Setting up python-minimal (2.7.5-5ubuntu3) ...
  Selecting previously unselected package python-oauthlib.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: man-db 2.6.7.1-1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6
  Uname: Linux 3.13.0-35-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  Date: Thu Sep  4 09:13:59 2014
  DuplicateSignature: package:man-db:2.6.7.1-1:ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
  ErrorMessage: ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
  InstallationDate: Installed on 2012-09-28 (705 days ago)
  InstallationMedia: Ubuntu-Studio 12.04.1 "Precise Pangolin" - Release i386 (20120818)
  SourcePackage: man-db
  Title: package man-db 2.6.7.1-1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: Upgraded to trusty on 2014-09-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1365939/+subscriptions



More information about the foundations-bugs mailing list