** 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) =>
** 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: (u
** 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: (u
** 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.
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
** 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
** 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:
** 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.
** 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.
** 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.
** 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.
** 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
** 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.
** 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
** 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.
** 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.
** 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
** 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.
** 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
** 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.
** 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.
** 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
** 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
** 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.
** 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.
** 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
** 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
** 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.
** 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
** 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
** 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.
** 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.
** 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.
** 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.
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
** 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
@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'
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
** 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 =>
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:
ess
** 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 cont
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
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
** 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
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.
** 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
** 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
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
** 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/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: (u
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.
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
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
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
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
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
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
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
** 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
** 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
** 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
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)
** 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
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
** 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:
** 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
** 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.
** 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: (u
** 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
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
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.
** 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
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
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.
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:
*** 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.
** 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
** 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
** 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
** 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
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) => Ch
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
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.
** 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
+
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
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
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
: 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
** 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) =>
** 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: (u
** 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: (u
** 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: (u
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
** 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
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
** 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
: 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
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
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
** 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:
201 - 300 of 2989 matches
Mail list logo
