I've tracked this 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 that any information gathered by apport should be written to the report and we shouldn't return so early from collecting info.
With the Error Tracker we've made a design decision to send reports that are "unreportable" to Launchpad and it seems like this, the case of /etc/apt/source.list being unreadable, is one of the crashes we'd want reported.
I've tracked this down to the following in apport/ui.py:
try:
report. add_package_ info(package)
report[ 'UnreportableRe ason'] = excstr(e)
except ValueError:
# this happens if we are collecting information on an uninstalled
# package
if not ignore_uninstalled:
raise
except SystemError as 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 'UnreportableRe ason' was changed to 'This package does not seem to be installed correctly'. I think that any information gathered by apport should be written to the report and we shouldn't return so early from collecting info.
With the Error Tracker we've made a design decision to send reports that are "unreportable" to Launchpad and it seems like this, the case of /etc/apt/ source. list being unreadable, is one of the crashes we'd want reported.