/usr/lib/x86_64-linux-gnu/libertine/update-puritine-containers: FileNotFoundError: /usr/lib/x86_64-linux-gnu/libertine/update-puritine-containers@156

Bug #1606505 reported by errors.ubuntu.com bug bridge
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Unassigned
Libertine
Status tracked in Devel
Devel
Fix Released
Medium
Christopher Townsend
Trunk
Fix Released
Medium
Christopher Townsend
libertine (Ubuntu)
Fix Released
Medium
Christopher Townsend

Bug Description

The Ubuntu Error Tracker has been receiving reports about a problem regarding libertine. This problem was most recently seen with version 1.3+16.10.20160721.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/14dfd883a1cc083b2b6370670cc54f1c0d8ef9e8 contains more details.

Tags: xenial yakkety

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libertine (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Crashes on Yakkety desktop

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

and 16.04 according to errors.u.c
Started with libertine 1.3+16.10.20160721.2-0ubuntu1

Changed in canonical-devices-system-image:
status: New → Confirmed
Changed in libertine (Ubuntu):
importance: Undecided → High
Revision history for this message
Christopher Townsend (townsend) wrote :

The crash doesn't really affect anything and is noise, but needs fixing nonetheless. Setting to Medium.

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

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

Changed in libertine:
status: In Progress → Fix Committed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Setting to High, it slows everything down on desktop when apport does its job.

Changed in canonical-devices-system-image:
importance: Undecided → High
milestone: none → 13
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Changed in canonical-devices-system-image:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.3.1+16.10.20160812.3-0ubuntu1

---------------
libertine (1.3.1+16.10.20160812.3-0ubuntu1) yakkety; urgency=medium

  [ Brandon Schaefer ]
  * Update our dbus session socket path to allow for the new session bus
    address while still supporting the older way.

  [ Chris Townsend ]
  * Fix crash where /run/user/$UID/dbus-session doesn't exist when the
    update-puritine-containers click hook runs. (LP: #1606505)
  * Only install the puritine click hook stuff in the python3-libertine-chroot
    package since puritine is only a chroot and remove the unused puritine
    framework.
  * Bump version to 1.3.1.

  [ Larry Price ]
  * Enforce click requirements for container ID. (LP: #1607819)
  * Extend desktop file search to recurse directories. (LP: #1608556)
  * Remove unused dependency on pam. (LP: #1579821)
  * Create bind-mount directories based on information from xdg-user-dir,
    and only mount on container startup. (LP: #1610123)

 -- Christopher Townsend <email address hidden> Fri, 12 Aug 2016 18:58:42 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
summary: - /usr/lib/x86_64-linux-gnu/libertine/update-puritine-
- containers:FileNotFoundError:/usr/lib/x86_64-linux-gnu/libertine/update-
- puritine-containers@156
+ /usr/lib/x86_64-linux-gnu/libertine/update-puritine-containers:
+ FileNotFoundError: /usr/lib/x86_64-linux-gnu/libertine/update-puritine-
+ containers@156
Changed in canonical-devices-system-image:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.