package libertined:amd64 1.7+17.04.20170320.1-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script was killed by signal (Terminated)

Bug #1676005 reported by Ari Torhamo on 2017-03-25
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Status tracked in Devel
Christopher Townsend
Christopher Townsend
libertine (Ubuntu)
Christopher Townsend

Bug Description

Got a message of a problem with the package "libertine" during the upgrade from Ubuntu Gnome 16.10 to 17.04 final beta, but the upgrade was finished anyway. This automated error report seems to think it was a fresh install, but it was an upgrade. I don't know if it's related, but after the upgrade the boot goes to loop with the latest available kernel 4.10.0-13, but boots normally with 4.8.0-41 (which I'm using now). The last point of the loop is Stopping User Manager for UID 121...

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libertined:amd64 1.7+17.04.20170320.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Sat Mar 25 00:45:34 2017
 Removing libertined:amd64 (1.7+17.04.20170320.1-0ubuntu1) ...
 Shutting down the libertined service...
 dpkg: error processing package libertined:amd64 (--remove):
  subprocess installed pre-removal script was killed by signal (Terminated)
ErrorMessage: subprocess installed pre-removal script was killed by signal (Terminated)
InstallationDate: Installed on 2016-12-13 (101 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
 dpkg 1.18.10ubuntu1
 apt 1.4~rc2
SourcePackage: libertine
Title: package libertined:amd64 1.7+17.04.20170320.1-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script was killed by signal (Terminated)
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Ari Torhamo (ari-torhamo) wrote :
tags: removed: need-duplicate-check
Ari Torhamo (ari-torhamo) wrote :

Interestingly, with the kernel 4.10.0-14 that I just upgraded to the boot doesn't go to loop. With the kernel 4.10.0-13 it still does.

Changed in libertine (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Christopher Townsend (townsend)

Fix committed into lp:libertine at revision 452, scheduled for release in libertine, milestone Unknown

Changed in libertine:
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.7.1+17.04.20170331-0ubuntu1

libertine (1.7.1+17.04.20170331-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * When starting pasted, ensure DISPLAY is set and valid before continuing to
    run. (LP: #1666472)
  * Fix pasted to work with rootless Xmir. (LP: #1671257)
  * Add a '-x' option to pkill so it only kills the libertined process(es)
    and nothing else. (LP: #1676005)
  * Remove hard-coded dependency on libraries.

  [ Larry Price ]
  * Bump version to 1.7.1
  * Gracefully handle creating a LibertineContainer object when the container
    backend is unavailable.
  * Update libertine xmir components to not depend on container backends.
    (LP: #1671938)
  * Catch all errors and gracefully shutdown libertined. (LP: #1671009)
  * Fix method call from ContainerControl d-bus to interfaces.
  * Update signal handlers in test_libertine_service to reflect new API.
  * Inject client for accessing ContainerControl within containers.
  * Rearchitect libertine service python backend for simpler access to running
    tasks. (LP: #1669091)
  * Ignore completions from dependencies during snapcraft build.
  * LXD needs to forward host environment to container when running arbitrary
  * Add client object to list_app_ids_task to avoid making reentrant service
  * Take advantage of new network subcommand during lxd init on newer
  * Prevent installing empty package names and appropriately update status for
    unstopped containers.
  * Modifications to make test_libertine_service more stable.
  * Reopen the database file after every failure to grab the lock.
    (LP: #1662655)

 -- Larry Price <email address hidden> Fri, 31 Mar 2017 20:09:39 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers