[Bug 1654647] Re: Starting an app in an LXD type container may fail due to not finding the dbus bridge socket

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Larry Price (larryprice)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  Starting an app in an LXD type container may fail due to not finding
  the dbus bridge socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654647/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654650] Re: Some bind-mounts in LXC type containers are owned by nobody/nogroup

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Some bind-mounts in LXC type containers are owned by nobody/nogroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609982] Re: Applications installed in containers don't have the same localization as what is used on the host system

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Applications installed in containers don't have the same localization
  as what is used on the host system

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1609982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654355] Re: LXC/LXD containers should be frozen instead of shut down when not used

[Christopher Townsend]

** Changed in: libertine/devel
   Status: Triaged => In Progress

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  LXC/LXD containers should be frozen instead of shut down when not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1657490] [NEW] It's possible to have 2 instances of the container managers running at the same time

[Christopher Townsend]

Public bug reported:

It's possible to have 2 instances of a container manager running at the
same time.  For example, launching a Libertine app in U8 will start
libertine-lx{cd}-manager and then running libertine-container-manager
operations in an ssh session will start another instance of libertine-
lx{cd}-manager.

After some investigation, this is due to a systemd user dbus session now
existing when in an ssh session, which is different than the Upstart
session dbus used in the U8 session.  So the service will start for
each.

We need a way to figure out if U8 is running and use it's session dbus
and if it's not running, don't use the libertine-lx{cd}-manager at all.

** Affects: libertine
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

** Changed in: libertine/devel
   Status: Triaged => In Progress

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

Title:
  It's possible to have 2 instances of the container managers running at
  the same time

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1657490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654356] Re: LXC/LXD containers should be automatically started on user login and then subsequently frozen

[Christopher Townsend]

** Summary changed:

- LXC/LXD containers should be automatically started on host boot and then 
subsequently frozen
+ LXC/LXD containers should be automatically started on user login and then 
subsequently frozen

** Description changed:

  To go along with bug #1654355, LXC/LXD containers should be set to
- automatically start on host system boot, and then they should be
+ automatically start on user session login, and then they should be
  subsequently frozen until needed.
  
  We should think about if this should be configurable if anyone does not
- want the container to boot on start.
+ want the container to start on login.
+ 
+ Note: I originally had this as starting a container on host boot, that
+ will cause problems since the containers are unprivileged and need user
+ info when starting.

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

Title:
  LXC/LXD containers should be automatically started on user login and
  then subsequently frozen

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654356/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655980] Re: lxd backend fails to destroy if container is started

[Christopher Townsend]

** Also affects: libertine/devel
   Importance: High
 Assignee: Larry Price (larryprice)
   Status: Fix Committed

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

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

Title:
  lxd backend fails to destroy if container is started

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1655980/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1623946] Re: Integrate the Libertine UI with System Settings

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Integrate the Libertine UI with System Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1623946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1620016] Re: libertine crashed with SIGSEGV in strlen()

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  libertine crashed with SIGSEGV in strlen()

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1620016/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1604015] Re: Seg fault when viewing container during destroy

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Seg fault when viewing container during destroy

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1604015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1615697] Re: When creating a container for the first time in the UI, UI stays stuck on the Welcome page

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  When creating a container for the first time in the UI, UI stays stuck
  on the Welcome page

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1615697/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1605354] Re: libertine-container-manager does not work properly in the Terminal App

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1605354/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1625627] Re: Container's apt cache should be updated before installing new packages

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Container's apt cache should be updated before installing new packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1625627/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550365] Re: Use AdaptivePageLayout instead of PageStack in the GUI

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Use AdaptivePageLayout instead of PageStack in the GUI

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1550365/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1589636] Re: Support launching non-containerized applications

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Support launching non-containerized applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1589636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1591350] Re: libertine-lxc-manager should start on demand

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  libertine-lxc-manager should start on demand

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1591350/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1570077] Re: Need way to cancel in-progress container creation

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Need way to cancel in-progress container creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1570077/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580612] Re: Add support for a LXD backend to Libertine

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Add support for a LXD backend to Libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1580612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1599197] Re: Need an apport hook that will collect relevant info for bug reports

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Need an apport hook that will collect relevant info for bug reports

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1599197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1590051] Re: Need way to add/remove extra bind-mounts inside the container's home directory

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Need way to add/remove extra bind-mounts inside the container's home
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1590051/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1619742] Re: LibreOffice often fails to copy and paste using Libertine pasted

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  LibreOffice often fails to copy and paste using Libertine pasted

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1593417] Re: Need to bind mount /run/cups to allow printing in X apps

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Need to bind mount /run/cups to allow printing in X apps

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1593417/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1592920] Re: Remove workaround for displaying matchbox title bar in chroot containers

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Remove workaround for displaying matchbox title bar in chroot
  containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1592920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] Re: Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1627757] Re: Debconf interactions no longer working

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Debconf interactions no longer working

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1627757/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Programs ran using proot fail on arm64 xenial chroots

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1649649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638079] Re: Move Xmir launching from ubuntu-app-launch to libertine

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Move Xmir launching from ubuntu-app-launch to libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1638079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637535] Re: Add support for helper apps when running in the containerless mode

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Add support for helper apps when running in the containerless mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628589] Re: Need better session management for Libertine X apps

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  Need better session management for Libertine X apps

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628589/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637579] Re: libertine-lxc-manager should be able to recover app/lxc running state if it dies and restarts

[Christopher Townsend]

** Changed in: libertine
Milestone: 1.5 => 1.6

** Changed in: libertine/trunk
Milestone: 1.5 => 1.6

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

Title:
  libertine-lxc-manager should be able to recover app/lxc running state
  if it dies and restarts

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637579/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628563] Re: Need to only install matchbox-window-manager in the container instead of the matchbox metapackage

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Need to only install matchbox-window-manager in the container instead
  of the matchbox metapackage

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1628563/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632729] Re: Running applications in containers should be tracked in ContainerConfig.json

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Running applications in containers should be tracked in
  ContainerConfig.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1632729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628587] Re: All operations to start/stop a container should use libertine-lxc-manager

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1628587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653973] Re: Creating an LXC type container fails

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Fix Committed => Fix Released

** Changed in: libertine/devel
   Status: Fix Committed => Fix Released

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

Title:
  Creating an LXC type container fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1653973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1655977] [NEW] lxd type containers should have option to enter a user password

[Christopher Townsend]

Public bug reported:

Just like lxc type containers, lxd type containers should have the
option for setting a user password.

** Affects: libertine
 Importance: Medium
 Assignee: Larry Price (larryprice)
 Status: Triaged

** Affects: libertine/devel
 Importance: Medium
 Assignee: Larry Price (larryprice)
 Status: Triaged

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: lxd

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: lxd

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

** Changed in: libertine/devel
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  lxd type containers should have option to enter a user password

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1655977/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580612] Re: Add support for a LXD backend to Libertine

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Add support for a LXD backend to Libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1580612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653973] Re: Creating an LXC type container fails

[Christopher Townsend]

@ventrical,

I assume your missing apps started with today's upgrade.  Not sure how
that would happen...could you open a new bug about your problem and in
that bug include the libertine version you are using and also include
the output of 'libertine-container-manager -i $container_id list-apps'
(where $container_id is the id of your containers) shows your apps or
not.  Maybe something else is messed up.

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Creating an LXC type container fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1653973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

[Christopher Townsend]

Looks like we have hit a roadblock with this.  Looks to be issues both
with proot and some kernels such as the one on frieza.

We may just have to require kernels on any device to support
unprivileged LXC's, ie the 3.13 kernel.

** Changed in: libertine/devel
   Status: In Progress => Triaged

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

Title:
  Programs ran using proot fail on arm64 xenial chroots

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1649649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609982] Re: Applications installed in containers don't have the same localization as what is used on the host system

[Christopher Townsend]

** Changed in: libertine/devel
   Status: Triaged => In Progress

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

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

Title:
  Applications installed in containers don't have the same localization
  as what is used on the host system

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1609982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Christopher Townsend]

Some more data points...

I disabled the screen blanking, but that made no difference.

But with the screen not blanked, I started an X app through Xmir and
left U8 idle and observed at almost exactly 10 minutes of idle time, U8
crashed.  This is what was in unity8.log at the time of the crash:

[2017-01-10 15:09:10.552229] mirserver: New display configuration:
[2017-01-10 15:09:10.552346] mirserver:   Output 36: LVDS connected, used
[2017-01-10 15:09:10.552434] mirserver:   Physical size 13,0" 290x160mm
[2017-01-10 15:09:10.552493] mirserver:   Current mode 1366x768 60,00Hz
[2017-01-10 15:09:10.552549] mirserver:   Preferred mode 1366x768 60,00Hz
[2017-01-10 15:09:10.552594] mirserver:   Logical position +0+0
[2017-01-10 15:09:10.552676] mirserver:   Output 43: VGA disconnected
[2017-01-10 15:09:10.552739] mirserver:   Output 46: HDMI-A disconnected
[2017-01-10 15:09:10.552799] mirserver:   Output 51: DisplayPort disconnected
[2017-01-10:15:09:10.553] qtmir.screens: QtCompositor::stop
[2017-01-10:15:09:10.554] qtmir.screens: ScreensModel::onCompositorStopping
[2017-01-10:15:09:10.554] qtmir.screens: ScreenWindow::setExposed 0x1c1e510 
false 0x7f4ed824f020
[2017-01-10:15:09:10.581] qtmir.screens: ScreensModel::update
[2017-01-10:15:09:10.582] qtmir.screens: Screen::setMirDisplayBuffer 
Screen(0x7f4ed824f010) 0x7f4ed815cb40 0x7f4ed815cc90
[2017-01-10:15:09:10.582] qtmir.screens: ===
[2017-01-10:15:09:10.582] qtmir.screens: Screen(0x7f4ed824f010) - id: 36 
geometry: QRect(0,0 1366x768) window: 0x1c1e510 type: "LVDS" scale: 1
[2017-01-10:15:09:10.582] qtmir.screens: ===
[2017-01-10:15:09:10.587] qtmir.screens: QtCompositor::start
[2017-01-10:15:09:10.587] qtmir.screens: ScreensModel::onCompositorStarting
[2017-01-10:15:09:10.587] qtmir.screens: ScreensModel::update
[2017-01-10:15:09:10.587] qtmir.screens: ===
[2017-01-10:15:09:10.587] qtmir.screens: Screen(0x7f4ed824f010) - id: 36 
geometry: QRect(0,0 1366x768) window: 0x1c1e510 type: "LVDS" scale: 1
[2017-01-10:15:09:10.587] qtmir.screens: ===
[2017-01-10:15:09:10.587] qtmir.screens: ScreenWindow::setExposed 0x1c1e510 
true 0x7f4ed824f020
terminate called after throwing an instance of 
'boost::exception_detail::clone_impl'
  what():  Nested Mir Display Error: Failed to update EGL surface: 
EGL_BAD_CONTEXT (0x3006)

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

Title:
  Unity8 crashes with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1521403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654650] Re: Some bind-mounts in LXC type containers are owned by nobody/nogroup

[Christopher Townsend]

I think the solution here is to remove the umounts during
LxcContainer::start_container().  the /usr/lib/locale umount was removed
in the MP for bug #1654648.  I will propose an MP here for removing the
/tmp/.X11-unix umount.

** Changed in: libertine/devel
   Status: Triaged => In Progress

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Some bind-mounts in LXC type containers are owned by nobody/nogroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654648] Re: The container's locale should not be bind-mounted from the host and should be programatically set at container start

[Christopher Townsend]

After further investigation, chroot container types still need the
/usr/lib/locale bind-mount, but that is ok since there is no running
container and each operation on the chroot is independent of another
running operation or running application.

** Tags removed: chroot

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

Title:
  The container's locale should not be bind-mounted from the host and
  should be programatically set at container start

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Christopher Townsend]

This is the easiest way to reproduce for me:

- Unity 8 desktop session, either X+O or Zesty
- Create a Libertine container and install an app in it such as Firefox.
- Start the X app.
- Wait ~30 minutes, ie, leave the system alone.

Xmir seems to exacerbate the issue, but I have observed the crash
without Xmir running.

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

Title:
  Unity8 crashes with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1521403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654648] Re: The container's locale should not be bind-mounted from the host and should be programatically set at container start

[Christopher Townsend]

** Summary changed:

- The host's locale is not being bind-mounted into LXD type containers
+ The container's locale should not be bind-mounted from the host and should be 
programatically set at container start

** Description changed:

- In LXC, we bind-mount /usr/lib/locale/ in order to match the locale of
- the running host.  This is not being done in LXD type containers.
+ All container types should no longer bind-mount /usr/lib/locale from the
+ host and instead should be set at container start time, if different
+ from the host.

** Tags added: chroot lxc

** Changed in: libertine/devel
   Status: Triaged => In Progress

** Changed in: libertine/devel
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  The container's locale should not be bind-mounted from the host and
  should be programatically set at container start

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521403] Re: Unity8 crashes with SIGSEGV in Screen::makeCurrent (./src/platforms/mirserver/screen.cpp:406)

[Christopher Townsend]

Bug #1654581 was duped to this one, but I will say that the crash has
become much more prevalent, like nearly 100% reproducible after the last
qtmir release.

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

Title:
  Unity8 crashes with SIGSEGV in Screen::makeCurrent
  (./src/platforms/mirserver/screen.cpp:406)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1521403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654648] Re: The host's locale is not being bind-mounted into LXD type containers

[Christopher Townsend]

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine/trunk
Milestone: None => 1.6

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  The host's locale is not being bind-mounted into LXD type containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654647] Re: Starting an app in an LXD type container may fail due to not finding the dbus bridge socket

[Christopher Townsend]

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

** Changed in: libertine/trunk
Milestone: None => 1.6

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

Title:
  Starting an app in an LXD type container may fail due to not finding
  the dbus bridge socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654647/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654650] [NEW] Some bind-mounts in LXC type containers are owned by nobody/nogroup

[Christopher Townsend]

Public bug reported:

Some bind-mounts in LXC type containers are owned by nobody/nogroup in
the running container such as /tmp/.X11-unix and /usr/lib/locale.

This is probably the root of the problem of why some package updates
fail and should be investigated so we can potentially get rid of the
umount's in container operations and also get rid of the container
operations/container apps running scenarios.

** Affects: libertine
 Importance: Medium
 Status: Triaged

** Affects: libertine/devel
 Importance: Medium
 Status: Triaged

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

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

Title:
  Some bind-mounts in LXC type containers are owned by nobody/nogroup

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654650/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580612] Re: Add support for a LXD backend to Libertine

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Larry Price (larryprice)

** Changed in: libertine/trunk
Milestone: None => 1.5

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  Add support for a LXD backend to Libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1580612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653973] Re: Creating an LXC type container fails

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Creating an LXC type container fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1653973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654356] [NEW] LXC/LXD containers should be automatically started on host boot and then subsequently frozen

[Christopher Townsend]

Public bug reported:

To go along with bug #1654355, LXC/LXD containers should be set to
automatically start on host system boot, and then they should be
subsequently frozen until needed.

We should think about if this should be configurable if anyone does not
want the container to boot on start.

** Affects: libertine
 Importance: Medium
 Status: Triaged

** Affects: libertine/devel
 Importance: Medium
 Status: Triaged

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: lxc lxd

** Description changed:

  To go along with bug #1654355, LXC/LXD containers should be set to
  automatically start on host system boot, and then they should be
  subsequently frozen until needed.
+ 
+ We should think about if this should be configurable if anyone does not
+ want the container to boot on start.

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- LXC/LXD containers should be automatically started on host boot and then 
subsuquently frozen
+ LXC/LXD containers should be automatically started on host boot and then 
subsequently frozen

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

** Tags added: lxc lxd

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

Title:
  LXC/LXD containers should be automatically started on host boot and
  then subsequently frozen

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654356/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654355] [NEW] LXC/LXD containers should be frozen instead of shut down when not used

[Christopher Townsend]

Public bug reported:

When an LXC/LXD container is no longer needed, it should be frozen
instead of shut down by the respective container manager.

This will make "start up" of the container much faster and will be
particularly useful for LXD containers that take a very long time to
start when fully stopped.

Also of note, memory usage will remain the same since the frozen
container will still reside in memory.  Possibly making this a
configuration option of a container will allow users who want to free
memory when a container is not needed is necessary???

** Affects: libertine
 Importance: Medium
 Status: Triaged

** Affects: libertine/devel
 Importance: Medium
 Status: Triaged

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: lxc lxd

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Description changed:

  When an LXC/LXD container is no longer needed, it should be frozen
  instead of shut down by the respective container manager.
  
- This will make "start up" of the container much faster.
+ This will make "start up" of the container much faster and will be
+ particularly useful for LXD containers that take a very long time to
+ start when fully stopped.

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

** Tags added: lxc lxd

** Description changed:

  When an LXC/LXD container is no longer needed, it should be frozen
  instead of shut down by the respective container manager.
  
  This will make "start up" of the container much faster and will be
  particularly useful for LXD containers that take a very long time to
  start when fully stopped.
+ 
+ Also of note, memory usage will remain the same since the frozen
+ container will still reside in memory.  Possibly making this a
+ configuration option of a container will allow users who want to free
+ memory when a container is not needed is necessary???

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

Title:
  LXC/LXD containers should be frozen instead of shut down when not used

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654305] [NEW] Add ability to shell into a container as a user

[Christopher Townsend]

Public bug reported:

Currently, there is no clean way to shell into a container via command
line.  The only way is to install some terminal application in the
container and then launch that.  But some users ssh into a device and
then want to access the container via the ssh session.

The proposal is to create a tool named something like "libertine-shell"
that would do this and it would enter the container as the user with the
proper bind mounts defined for the container.

** Affects: libertine
 Importance: Wishlist
 Status: Triaged

** Affects: libertine/devel
 Importance: Wishlist
 Status: Triaged

** Affects: libertine/trunk
 Importance: Wishlist
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Wishlist
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => Triaged

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Wishlist

** Changed in: libertine/trunk
   Importance: Undecided => Wishlist

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: libertine/devel
Milestone: None => 1.6

** Changed in: libertine/trunk
Milestone: None => 1.6

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

Title:
  Add ability to shell into a container as a user

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1654305/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646462] Re: lxc container download error (possibly HSTS related)

[Christopher Townsend]

I see this today on a Zesty host when trying to create containers.  I do
not see this issue on a Xenial host however.

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

Title:
  lxc container download error (possibly HSTS related)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1653973] Re: Creating an LXC type container fails after setting up an LXD type container

[Christopher Townsend]

Ok, I have figured this out and this is a problem with the current
upstream release (1.4.4) as well, so we'll need a hotfix for this.

The problem is setting the lxc logging during the LibertineLXC init
before the container creation is overriding LXC from looking for
default.conf and thus, we have an invalid lxc configuration for
container creation.

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Creating an LXC type container fails after setting up an LXD type container
+ Creating an LXC type container fails

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

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

Title:
  Creating an LXC type container fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1653973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1652424] Re: libertine-launch manpage needs to be updated to better explain its usage

[Christopher Townsend]

The whole intent of Libertine is allowing users to install and use X
graphical applications in Debian package format on their Unity 8
devices.  Given that is the goal, if a user wants a shell inside the
container to run command line applications, then our suggestion is to
install a terminal application such as Terminator or Sakura inside the
container and then run that terminal application from within Unity 8.

I'm really not sure where it's documented that libertine-launch is
supposed to be used to get command line access inside a container.
libertine-launch was only developed as a helper application for ubuntu-
app-launch to start X applications in a Libertine container (and later
to launch snap applications).

As an aside, I understand power users want more control from the command
line such as ssh'ing in to the device and then accessing a container
from the ssh session, but honestly, that is really beyond the intended
design and scope of Libertine.

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

Title:
  libertine-launch manpage needs to be updated to better explain its
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1652424/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1652424] Re: libertine-launch could be more intuitive

[Christopher Townsend]

Hello,

I'm really not sure what your intent is when using libertine-launch.
libertine-launch is really only used by ubuntu-app-launch to launch a
graphical application within the Unity 8 shell and not intended for the
command line.

If you need to run commands within a Libertine container, I suggest
using libertine-container-manager's "hidden" exec subcommand.  If you
are wanting to launch a graphical app in Unity 8 via the command line, I
suggest using ubuntu-app-launch.

Probably a good way to make this less confusing is to update the man
page to reflect what I just said:)

** Changed in: libertine
   Status: New => Triaged

** Changed in: libertine
   Importance: Undecided => Medium

** Summary changed:

- libertine-launch could be more intuitive
+ libertine-launch manpage needs to be updated to better explain its usage

** Also affects: libertine/devel
   Importance: Medium
   Status: Triaged

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  libertine-launch manpage needs to be updated to better explain its
  usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1652424/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648674] Re: xenial libertine package is uninstallable with libertine-manager-app installed

[Christopher Townsend]

This should be fixed by default with the latest release.  Marking Fix
Released, but the next release should clean up the version string used
in the Breaks/Replaces.

** Changed in: libertine (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  xenial libertine package is uninstallable with libertine-manager-app
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1648674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1590051] Re: Need way to add/remove extra bind-mounts inside the container's home directory

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Need way to add/remove extra bind-mounts inside the container's home
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1590051/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] Re: Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1649649] Re: Programs ran using proot fail on arm64 xenial chroots

[Christopher Townsend]

Some more details when running strace on proot (truncated output):

...
ptrace(PTRACE_SETREGSET, 11208, NT_PRSTATUS, [{0x2437f168, 272}]) = 0
ptrace(PTRACE_SYSCALL, 11208, NULL, SIG_0) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_TRAPPED, si_pid=11208, si_uid=32011, 
si_status=SIGTRAP, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFSTOPPED(s) && WSTOPSIG(s) == SIGTRAP} | PTRACE_EVENT_EXIT << 
16], __WALL, NULL) = 11208
ptrace(PTRACE_SYSCALL, 11208, NULL, SIG_0) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=11208, si_uid=32011, 
si_status=SIGKILL, si_utime=0, si_stime=0} ---
wait4(-1, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGKILL}], __WALL, NULL) = 11208
...

*Something* is sending the process in question SIGKILL.



** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => High

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

** Changed in: libertine/devel
     Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  Programs ran using proot fail on arm64 xenial chroots

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1649649/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648674] Re: xenial libertine package is uninstallable with libertine-manager-app installed

[Christopher Townsend]

Ok, I understand this better.  By default, the release in queue will
"just fix" this since the upstream version will be 1.4.4.

On the next release after the one in queue, I will clean up the version
there not to have the extra info added by ci-train.

** Changed in: libertine (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  xenial libertine package is uninstallable with libertine-manager-app
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1648674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580612] Re: Add support for a LXD backend to Libertine

[Christopher Townsend]

** Changed in: libertine/devel
   Status: Triaged => In Progress

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

Title:
  Add support for a LXD backend to Libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1580612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648674] Re: xenial libertine package is uninstallable with libertine-manager-app installed

[Christopher Townsend]

Hey Ken,

The binary package 'libertine' has morphed into a misnomer in that
'libertine' was just the UI part of the whole suite.  That said, we
renamed 'libertine' to 'libertine-manager-app'.  If you install
'libertine', it is now a dummy package for 'libertine-manager-app'.

I believe it is doing the right thing here.  Would you agree after I
explained this?


** Changed in: libertine (Ubuntu)
   Status: New => Incomplete

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

Title:
  xenial libertine package is uninstallable with libertine-manager-app
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1648674/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] Re: Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

** Tags added: chroot

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1580612] Re: Add support for a LXD backend to Libertine

[Christopher Townsend]

** Also affects: libertine/devel
   Importance: Low
 Assignee: Christopher Townsend (townsend)
   Status: Triaged

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Branch linked: lp:~larryprice/libertine/lxd

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Low => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
 Assignee: Christopher Townsend (townsend) => Larry Price (larryprice)

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

Title:
  Add support for a LXD backend to Libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1580612/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1590051] Re: Need way to add/remove extra bind-mounts inside the container's home directory

[Christopher Townsend]

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  Need way to add/remove extra bind-mounts inside the container's home
  directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1590051/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] Re: Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638079] Re: Move Xmir launching from ubuntu-app-launch to libertine

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Move Xmir launching from ubuntu-app-launch to libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1638079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646655] Re: unity8 provides no way or means to access information on USB stick

[Christopher Townsend]

Here are my thoughts on this...

First an foremost, particularly on the desktop, Unity 8 should have some
native way of viewing files on USB devices.  There is not a very usable
native file manager available on Unity 8 desktop, so that is problem
number 1.  Hopefully when full Gtk support is added and the ability to
easily discover Gtk apps in U8 is implemented, something like Nautilus
will just work.

The second problem, since there is not a very usable file manager, is
using a Libertine container with some X file manager.  This problem is
probably more difficult to solve because we use unprivileged LXC's for
Libertine on U8 desktop and due to how unprivileged LXC's work, access
to USB (and SD card) file systems via bind mounts, is currently very
difficult to achieve.  We've spent time trying to make that work and had
to de-prioritize it due the non-trivial nature of getting something to
work.  We are not LXC developers, so trying to get that to work is a
very tall mountain to climb:)

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

Title:
  unity8 provides no way or means to access information on USB stick

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646655/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1600286] Re: Firefox with phantom UI elements

[Christopher Townsend]

Hey Larry,

I should have updated this some time ago, but this is on Frieza, so it's
a Vivid chroot:)

** Changed in: libertine (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Firefox with phantom UI elements

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1600286/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643426] Re: package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/libertine/libertine_64.png', which is also in package liberti

[Christopher Townsend]

** Changed in: libertine (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed
  to install/upgrade: trying to overwrite
  '/usr/share/libertine/libertine_64.png', which is also in package
  libertine 1.4.2+16.10.20161005-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1643426/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643426] Re: package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/libertine/libertine_64.png', which is also in package liberti

[Christopher Townsend]

This should be fixed now.

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

Title:
  package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed
  to install/upgrade: trying to overwrite
  '/usr/share/libertine/libertine_64.png', which is also in package
  libertine 1.4.2+16.10.20161005-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1643426/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644237] Re: unity8 fails to start as guest user

[Christopher Townsend]

This has been the case since day 1 of Unity on the desktop.  See bug
#1307618.  Not sure why we never added unity8 to that bug, so let's dupe
that bug to this one.

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

Title:
  unity8 fails to start as guest user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1644237] Re: unity8 fails to start as guest user

[Christopher Townsend]

Err, I meant Unity *8* on the desktop:)

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

Title:
  unity8 fails to start as guest user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1307618] Re: Unity 8 Desktop Preview does not work in the guest session

[Christopher Townsend]

*** This bug is a duplicate of bug 1644237 ***
https://bugs.launchpad.net/bugs/1644237

** This bug has been marked a duplicate of bug 1644237
   unity8 fails to start as guest user

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

Title:
  Unity 8 Desktop Preview does not work in the guest session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1307618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1623946] Re: Integrate the Libertine UI with System Settings

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Integrate the Libertine UI with System Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1623946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632729] Re: Running applications in containers should be tracked in ContainerConfig.json

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Running applications in containers should be tracked in
  ContainerConfig.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1632729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628587] Re: All operations to start/stop a container should use libertine-lxc-manager

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1628587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637535] Re: Add support for helper apps when running in the containerless mode

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

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

Title:
  Add support for helper apps when running in the containerless mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643426] Re: package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/libertine/libertine_64.png', which is also in package liberti

[Christopher Townsend]

Hi!

Thanks for catching this and entering this bug report.  Will be fixing
soon.

** Changed in: libertine (Ubuntu)
   Status: New => In Progress

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  package libertine-manager-app 1.4.3+17.04.20161118.1-0ubuntu1 failed
  to install/upgrade: trying to overwrite
  '/usr/share/libertine/libertine_64.png', which is also in package
  libertine 1.4.2+16.10.20161005-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1643426/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642529] Re: Can't run x apps in latest rc image

[Christopher Townsend]

Thanks!  So not a libertine bug.  The image needs to include the correct
version of libertine-tools.

** Changed in: libertine
   Status: Incomplete => Invalid

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: New => Invalid

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

Title:
  Can't run x apps in latest rc image

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642529] Re: Can't run x apps in latest rc image

[Christopher Townsend]

Most definitely not an issue in Puritine itself, so marking that
invalid.

Looking at the log, it seems an older version of libertine is in this
image.  Could you provide the output of 'apt-cache policy libertine-
tools'?

The version of libertine in vivid overlay is
1.4.2+15.04.20161005-0ubuntu1.

** Changed in: puritine
   Status: New => Invalid

** Also affects: libertine
   Importance: Undecided
   Status: New

** Changed in: libertine
   Status: New => Incomplete

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

Title:
  Can't run x apps in latest rc image

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642529/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] Re: Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

** Summary changed:

- Support arm64 based chroot containers
+ Support arm64 and xenial overlay based chroot containers

** Description changed:

  Currently, creating a chroot container on arm64 based hardware fails.
+ 
+ Also, the xenial stable overlay PPA should be added when creating a
+ xenial chroot container.

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642324] [NEW] Support arm64 and xenial overlay based chroot containers

[Christopher Townsend]

Public bug reported:

Currently, creating a chroot container on arm64 based hardware fails.

Also, the xenial stable overlay PPA should be added when creating a
xenial chroot container.

** Affects: libertine
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  Support arm64 and xenial overlay based chroot containers

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1642324/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1642297] [NEW] xmir crashes immediately on arm64

[Christopher Townsend]

Public bug reported:

Using xmir on the Xenial arm64 based image on a frieza, xmir crashes
immediately upon starting.

Here is the output in the app's upstart log:

glamor EGL version: 1.4 Android META-EGL
glamor EGL extensions: EGL_KHR_get_all_proc_addresses 
EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base 
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image 
EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context 
EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable 
EGL_HYBRIS_native_buffer2 EGL_HYBRIS_WL_acquire_native_buffer 
EGL_WL_bind_wayland_display 
glamor GL version: OpenGL ES 2.0 (OpenGL ES 3.1)
glamor GL extensions: GL_EXT_debug_marker GL_ARM_rgba8 
GL_ARM_mali_shader_binary GL_OES_depth24 GL_OES_depth_texture 
GL_OES_depth_texture_cube_map GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 
GL_EXT_read_format_bgra GL_OES_compressed_paletted_texture 
GL_OES_compressed_ETC1_RGB8_texture GL_OES_standard_derivatives 
GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_texture_npot 
GL_OES_vertex_half_float GL_OES_required_internalformat 
GL_OES_vertex_array_object GL_OES_mapbuffer GL_EXT_texture_format_BGRA 
GL_EXT_texture_rg GL_EXT_texture_type_2_10_10_10_REV GL_OES_fbo_render_mipmap 
GL_OES_element_index_uint GL_EXT_shadow_samplers 
GL_OES_texture_compression_astc GL_KHR_texture_compression_astc_ldr 
GL_KHR_texture_compression_astc_hdr GL_KHR_debug GL_EXT_occlusion_query_boolean 
GL_EXT_disjoint_timer_query GL_EXT_blend_minmax GL_EXT_discard_framebuffer 
GL_OES_get_program_binary GL_OES_texture_3D GL_EXT_texture_storage 
GL_EXT_multisampled_render_to_texture GL_OES_surfaceles
 s_context GL_OES_texture
glamor GLSL version: OpenGL ES GLSL ES 3.10
(EE) 
(EE) Backtrace:
(EE) 0: Xmir (xorg_backtrace+0x58) [0x5556603490]
(EE) 
(EE) Segmentation fault at address 0x16df
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
XMir has closed unexpectedly

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: arm64 xmir

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

Title:
  xmir crashes immediately on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1642297/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1639440] Re: [desktop] apps don't start, missing logs

[Christopher Townsend]

I'm seeing this behavior too on Zesty.

@serge-hallyn,

Yes, parts of the Unity 8 stack are still relying on cgmanager.  The
future plan is to use systemd and get rid of the cgmanager dependence,
but The Future is not now:)

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

Title:
  [desktop] apps don't start, missing logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638079] [NEW] Move Xmir launching from ubuntu-app-launch to libertine

[Christopher Townsend]

Public bug reported:

Currently, Xmir launching is handled by ubuntu-app-launch, but as
agreed, it makes more since to put this functionality in the libertine
suite, particularly the new libertine-xmir-tools package.

This is also needed for snapping Xmir and its helper apps.

** Affects: libertine
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: Undecided
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Undecided
 Status: Triaged

** Affects: ubuntu-app-launch (Ubuntu)
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-app-launch (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Currently, Xmir launching is handled by ubuntu-app-launch, but as
  agreed, it makes more since to put this functionality in the libertine
  suite, particularly the new libertine-xmir-tools package.
+ 
+ This is also needed for snapping Xmir and its helper apps.

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-app-launch (Ubuntu)
   Status: New => In Progress

** Changed in: libertine/devel
   Importance: Undecided => High

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: Undecided => High

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  Move Xmir launching from ubuntu-app-launch to libertine

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1638079/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1623946] Re: Integrate the Libertine UI with System Settings

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Larry Price (larryprice)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Larry Price (larryprice)

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

Title:
  Integrate the Libertine UI with System Settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1623946/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1628587] Re: All operations to start/stop a container should use libertine-lxc-manager

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1628587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632729] Re: Running applications in containers should be tracked in ContainerConfig.json

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Running applications in containers should be tracked in
  ContainerConfig.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1632729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637535] Re: Add support for helper apps when running in the containerless mode

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: Triaged => In Progress

** Changed in: libertine (Ubuntu)
   Status: Triaged => In Progress

** Changed in: libertine/trunk
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine (Ubuntu)
 Assignee: (unassigned) => Christopher Townsend (townsend)

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

Title:
  Add support for helper apps when running in the containerless mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637579] [NEW] libertine-lxc-manager should be able to recover app/lxc running state if it dies and restarts

[Christopher Townsend]

Public bug reported:

If libertine-lxc-manager dies while apps are running in a container,
when it restarts, it should be able to recover the state of running apps
and lxc's.

** Affects: libertine
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Summary changed:

- libertine-lxc-manager should be able to recover app/lxc running state if it 
dies and restart
+ libertine-lxc-manager should be able to recover app/lxc running state if it 
dies and restarts

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  libertine-lxc-manager should be able to recover app/lxc running state
  if it dies and restarts

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637579/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637535] Re: Add support for helper apps when running in the containerless mode

[Christopher Townsend]

** Description changed:

  When running applications in containerless mode, helper apps need to be
- started as well including the Dbus session bridge, pasted, matchbox,
- etc.
+ started as well including pasted and matchbox.
  
  This is needed soon for running snap applications in a Unity 8 desktop
  session.

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

Title:
  Add support for helper apps when running in the containerless mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1637535] [NEW] Add support for helper apps when running in the containerless mode

[Christopher Townsend]

Public bug reported:

When running applications in containerless mode, helper apps need to be
started as well including the Dbus session bridge, pasted, matchbox,
etc.

This is needed soon for running snap applications in a Unity 8 desktop
session.

** Affects: libertine
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: High
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: High
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: High
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => High

** Changed in: libertine/trunk
   Importance: Undecided => High

** Changed in: libertine (Ubuntu)
   Importance: Undecided => High

** Description changed:

  When running applications in containerless mode, helper apps need to be
  started as well including the Dbus session bridge, pasted, matchbox,
  etc.
+ 
+ This is needed soon for running snap applications in a Unity 8 desktop
+ session.

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  Add support for helper apps when running in the containerless mode

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1637535/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1589636] Re: Support launching non-containerized applications

[Christopher Townsend]

** Changed in: libertine/trunk
   Status: In Progress => Fix Committed

** Changed in: libertine (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: libertine/devel
   Status: In Progress => Fix Committed

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

Title:
  Support launching non-containerized applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1589636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632729] [NEW] Running applications in containers should be tracked in ContainerConfig.json

[Christopher Townsend]

Public bug reported:

When an application is launched in a container, it should be tracked in
ContainersConfig.json.  This will ultimately be used by libertine-lxc-
manager for rebuilding state if it happens to die and is restarted.

** Affects: libertine
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/devel
 Importance: Medium
 Assignee: Christopher Townsend (townsend)
 Status: In Progress

** Affects: libertine/trunk
 Importance: Medium
 Status: Triaged

** Affects: libertine (Ubuntu)
 Importance: Medium
 Status: Triaged

** Also affects: libertine/devel
   Importance: Undecided
   Status: New

** Also affects: libertine/trunk
   Importance: Undecided
   Status: New

** Also affects: libertine (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: libertine/devel
   Status: New => In Progress

** Changed in: libertine/trunk
   Status: New => Triaged

** Changed in: libertine (Ubuntu)
   Status: New => Triaged

** Changed in: libertine/devel
   Importance: Undecided => Medium

** Changed in: libertine/trunk
   Importance: Undecided => Medium

** Changed in: libertine (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libertine/devel
 Assignee: (unassigned) => Christopher Townsend (townsend)

** Changed in: libertine/devel
Milestone: None => 1.5

** Changed in: libertine/trunk
Milestone: None => 1.5

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

Title:
  Running applications in containers should be tracked in
  ContainerConfig.json

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1632729/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1537399] Re: [Feature Request] Xmir icon generation

[Christopher Townsend]

There has been quite a bit of work in application surfacing and icons w/
the Libertine/Desktop Apps Scope.

I don't think this particular bug applies anymore, but I'll mark
Incomplete and wait for any feedback.

Also, marking the Puritine tasks invalid as it no longer provides and
desktop files and icons and solely relies on the Libertine/Desktop Apps
scope.

** Changed in: puritine
   Status: New => Invalid

** No longer affects: puritine (Ubuntu)

** Changed in: libertine
   Status: Triaged => Incomplete

** Changed in: libertine (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  [Feature Request] Xmir icon generation

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1537399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1583538] Re: [desktop] Error creating OpenGL context using Java

[Christopher Townsend]

Looks to me like Java is querying display modes and doesn't receive
anything back.  Jave doesn't handle this gracefully and crashes.

Xmir should probably at least return something meaningful back when
being queried for display modes.

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

Title:
  [desktop] Error creating OpenGL context using Java

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1583538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630807] Re: libertine crashed with SIGSEGV

[Christopher Townsend]

** Information type changed from Private to Public

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

Title:
  libertine crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libertine/+bug/1630807/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs