libertine-launch crashed with AttributeError in finish_application(): 'NoneType' object has no attribute 'pid'

Bug #1666177 reported by dinamic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
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

ubuntu 17.04 unity8 deb session

libertine-launch crashed with AttributeError in finish_application(): 'NoneType' object has no attribute 'pid'

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: libertine-tools 1.6+17.04.20170209-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Mon Feb 20 12:26:37 2017
ExecutablePath: /usr/bin/libertine-launch
InstallationDate: Installed on 2016-12-12 (69 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/libertine-launch --id=zesty geany
PythonArgs: ['/usr/bin/libertine-launch', '--id=zesty', 'geany']
SourcePackage: libertine
Title: libertine-launch crashed with AttributeError in finish_application(): 'NoneType' object has no attribute 'pid'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
dinamic (dinamic6661) wrote :
tags: removed: need-duplicate-check
Changed in libertine (Ubuntu):
importance: Undecided → Medium
Revision history for this message
dinamic (dinamic6661) wrote :

same with 0.10+17.04.20170215.1-0ubuntu1

information type: Private → Public
Changed in libertine (Ubuntu):
status: New → Triaged
Revision history for this message
Libertine CI Bot (libertine-ci-bot) wrote :

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

Changed in libertine:
status: Triaged → Fix Committed
Changed in libertine (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Christopher Townsend (townsend)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libertine - 1.7+17.04.20170308-0ubuntu1

---------------
libertine (1.7+17.04.20170308-0ubuntu1) zesty; urgency=medium

  [ Chris Townsend ]
  * Fix libertined such that it can probe for currently running X apps and
    rebuild application running state. (LP: #1637579)
  * Gracefully handle the case where an application does not start.
    (LP: #1666177)
  * Kill the libertined service during the libertined package removal and
    upgrades (LP: #1667368)
  * Refactor package operation details into container operation details.
  * Allowing specifying multiple packages to be installed or removed.
    (LP: #1665647)
  * Show the current container state in the 'Status' section of the
    Container Info page in the UI. (LP: #1667726)
  * Add ability to configure stopping or freezing a container from within
    the UI. (LP: #1667717)
  * Bump version to 1.7.

  [ Larry Price ]
  * Prevent rewriting existing data in ContainersConfig. (LP: #1659115)
  * Prevent staging libertine files when installing dependencies and fix
    deprecations for the snap.
  * Use AdaptivePageLayout instead of PageStack for app navigation.
    (LP: #1550365) (LP: #1659076)
  * Refactor ContainersConfig handling from the GUI.
  * Prevent removing container from the database when destroy fails.
  * Various fixes for getting the confined snap working with libertined.
  * Remove /Progress objects from d-bus connection during cleanup.
  * LXD container status will override d-bus result during destroy only.
  * Implement GUI for adding and removing bind-mounts in containers.
  * Use a decorator to refresh the database during any libertined operations
    involving ContainersConfig.
  * Fix any broken symlinks in the local lxd rootfs during update and package
    installation. (LP: #1659646)
  * Update the default container type to lxd. (LP: #1665645)
  * Properly remove bind-mounted files in local rootfs during lxd destroy.
  * Add container hostname to /etc/hosts in lxd containers.
  * Add a force option for destroying running containers.

 -- Christopher Townsend <email address hidden> Wed, 08 Mar 2017 14:53:46 +0000

Changed in libertine (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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