Libertine

libertine-container-manager does not work properly in the Terminal App

Series devel
Bug #1605354

Bug #1605354 reported by Christopher Townsend on 2016-07-21

This bug affects 4 people

	Status	Importance	Assigned to
Libertine	Won't Fix	Medium	Unassigned
Devel	Won't Fix	Medium	Unassigned
Trunk	Won't Fix	Medium	Unassigned
libertine (Ubuntu)	Won't Fix	Medium	Unassigned

Bug Description

When running libertine-container-manager from within the Terminal App, create and sometime install-package will fail. This is due to some type of confinement issue with the Terminal App.

At the very least, l-c-m should check to see if it's running in the Terminal App and if so, display a message and exit.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2016-07-28:

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

Changed in libertine (Ubuntu):
status:	New → Confirmed

Christopher Townsend (townsend) on 2016-07-29

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

Christopher Townsend (townsend) on 2016-09-07

Changed in libertine:
milestone:	1.4 → 1.5

Revision history for this message

Larry Price (larryprice) wrote on 2016-12-19:

I'm fairly certain this has been resolved within the Terminal app since it's now installed by default alongside Unity 8.

Revision history for this message

Larry Price (larryprice) wrote on 2016-12-19:

Welp, looks like it does still happen when creating chroot containers, just at the very end of create (the best possible time).

Christopher Townsend (townsend) on 2017-01-12

Changed in libertine:
milestone:	1.5 → 1.6

Christopher Townsend (townsend) on 2017-02-15

Changed in libertine:
milestone:	1.6 → 1.7

Revision history for this message

Christopher Townsend (townsend) wrote on 2017-02-24:

I just tried this on a Xenial+Overlay classic U8 (ie, deb based) setup and I could successfully create a chroot type Libertine container on the system using the Terminal App.

Since Vivid support is only in security update mode and Click packages are transitioning to snaps, I'm just going to close this Won't Fix with the caveat that is does work on the desktop.