This bug was fixed in the package apport - 2.19.3-0ubuntu1
---
apport (2.19.3-0ubuntu1) xenial; urgency=medium
* New upstream microrelease:
- apt/dpkg: Fix source record lookup in install_packages. Thanks Brian
Murray!
- hookutils.py, attach_gsettings_schema(): Don't r
Fixed in trunk.
** Changed in: apport (Ubuntu)
Status: Triaged => 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/1516947
Title:
apport looping on an old crash dump
To manage no
** Branch linked: lp:apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516947
Title:
apport looping on an old crash dump
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Tags added: rls-x-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1516947
Title:
apport looping on an old crash dump
To manage notifications about this bug go to:
https://bugs.launchpad.n
According to Alan's strace this hangs in/loops over reading the existing
.crash file; this can only be the reading ofCrashCounter.
This reproduces easily with:
python3 -c 'import apport.fileutils;
print(apport.fileutils.get_recent_crashes(open("_usr_bin_caja.1000.crash",
"rb")))'
** Changed in: