libertine-lxc-manager should start on demand

Bug #1591350 reported by Stephen M. Webb on 2016-06-10
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

The libertine-launch tool should attempt to start the libertine-lxc-manager daemon once if it's not already running.

Related branches

Christopher Townsend (townsend) wrote :

This may not be possible since if we launch libertine-lxc-manager from libertine-launch, then it belong in the cgroup of that particular launched application and not be accessible by other attempted launches. Let alone that the process will get killed when that cgroup get torn down.

That said, I'll investigate to see if there is some way to launch it on demand via some other method.

Changed in libertine:
milestone: 1.3 → 1.4
Christopher Townsend (townsend) wrote :

The solution is to port over libertine-lxc-manager to be a DBus service and activate it when needed.

Changed in libertine (Ubuntu):
importance: Undecided → Medium
status: New → Triaged

Fix committed into lp:libertine at revision 290, 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)
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.4.1+16.10.20160914-0ubuntu1

libertine (1.4.1+16.10.20160914-0ubuntu1) yakkety; urgency=medium

  [ Brandon Schaefer ]
  * Refactor the libertine-session-bus to be a class, so we will be on the
    same process and we can actually test LSB more then just running it and
    checking exit code.
  * Add a get_logger function to the libertine utils. This function will get
    the logger __libertiner_logger__ which will only be setup once, with one

  [ Chris Townsend ]
  * Switch libertine-lxc-manager to be a DBus service and activate it on demand
    via DBus. (LP: #1591350)
  * Add check for special LIBERTINE_JENKAAS_TESTING environment variable for
    the smoke testing harness.
  * Bump version to 1.4.1.

  [ Larry Price ]
  * Return user to homepage when container has been destroyed from under them.
    (LP: #1604015)
  * Introduce a method in ContainersConfig to refresh the database depending
    on an md5 checksum.
  * Creating the first container moves user to ContainersView screen.
    (LP: #1615697)
  * Inject a ContainersConfig instance when creating containers.
  * Fix crash in ContainersConfig when getting host arch by using HostInfo
  * Create a signal to indicate that container creation has begun.

 -- Christopher Townsend <email address hidden> Wed, 14 Sep 2016 14:46:02 +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