All operations to start/stop a container should use libertine-lxc-manager

Bug #1628587 reported by Christopher Townsend
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Christopher Townsend
Trunk
Fix Released
Medium
Christopher Townsend
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

Currently, libertine-launch uses libertine-lxc-manager for starting and stopping a container. libertine-container-manager should as well in case a user decides to do container operations with l-c-m while an app is open. Right now in that scenario, l-c-m would just shut down the container without regard for the running app.

Related branches

Changed in libertine (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

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

Changed in libertine:
status: In Progress → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.4.3+17.04.20161121.2-0ubuntu1

---------------
libertine (1.4.3+17.04.20161121.2-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * Fix old libertine package breaks/replaces version for proper
    upgrading.

 -- Christopher Townsend <email address hidden> Mon, 21 Nov 2016 19:45:35 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
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.