libertine-container-manager crashed with json.decoder.JSONDecodeError in decode(): Extra data: line 15 column 1 (char 333)

Bug #1630364 reported by tajreed
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libertine (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: libertine-tools 1.4.1+16.10.20160914-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Sat Oct 1 15:12:35 2016
ExecutablePath: /usr/bin/libertine-container-manager
InstallationDate: Installed on 2016-08-07 (57 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160806)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/libertine-container-manager fix-integrity
ProcEnviron:
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
PythonArgs: ['/usr/bin/libertine-container-manager', 'fix-integrity']
SourcePackage: libertine
Title: libertine-container-manager crashed with json.decoder.JSONDecodeError in decode(): Extra data: line 15 column 1 (char 333)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Related branches

Revision history for this message
tajreed (tajreed-charter) wrote :
tags: removed: need-duplicate-check
Changed in libertine (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Larry Price (larryprice) wrote :

This should be fixed incidentally by the libertine-service branch. The issue was calling flock while writing to the database, but not while reading. This meant that there was a chance the file would be manipulated while we are trying to do a read.

Changed in libertine (Ubuntu):
status: New → Fix Committed
information type: Private → Public
Changed in libertine (Ubuntu):
status: Fix Committed → 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.