touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #11384
[Bug 1355546] Re: incomplete crash files getting uploaded to the error tracker
I'd tracked the update-manager case down to the following in
apport/ui.py:
try:
report.add_package_info(package)
except ValueError:
# this happens if we are collecting information on an uninstalled
# package
if not ignore_uninstalled:
raise
except SystemError as e:
report['UnreportableReason'] = excstr(e)
return
We are returning from thread_collect_info() before we've written the
collected information to the report. Removing the return works but then
'UnreportableReason' was changed to 'This package does not seem to be
installed correctly'. I think this issue with /etc/apt/sources.list is
likely a separate bug (than the menulibre examples in the description),
so I'll open a separate bug for it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1355546
Title:
incomplete crash files getting uploaded to the error tracker
Status in “apport” package in Ubuntu:
New
Bug description:
Looking at some crash reports in the Ubuntu Error Tracker, I saw a
couple that there were odd because they were missing the DistroRelease
data.
https://errors.ubuntu.com/oops/b6579caa-1f91-11e4-b37e-fa163e75317b
That error was reported at 2014-08-09 06:52:21 (b6579caa-1f91-11e4
-b37e-fa163e75317b) inserted into OOPS CF. Shortly, afterwards
(2014-08-09 06:52:34 (bd8b1dbc-1f91-11e4-9deb-fa163e22e467) inserted
into OOPS CF) an OOPS from the same user was reported.
https://errors.ubuntu.com/oops/bd8b1dbc-1f91-11e4-9deb-fa163e22e467
The second OOPS has all the data collected including Dependencies, and
DistroRelease. whoopsie should only upload the .crash file if there
is a .upload file so it seems likely that apport created the .upload
file prematurely. Although, for that to be the case then apport would
have to modify the .upload file again such that whoopsie noticed it.
Regardless, there is something odd going on.
I found a second example too:
https://errors.ubuntu.com/oops/ce4805be-1f20-11e4-a536-fa163e4aaad4
https://errors.ubuntu.com/oops/d5761f42-1f20-11e4-9c34-fa163e707a72
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1355546/+subscriptions
References