This bug was fixed in the package apport - 2.20.3-0ubuntu8.3
---------------
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium
* Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
with apt key ring. Thanks to Dimitri John Ledkov for the patch.
(LP: #1651623)
* Disable report.test_add_gdb_info_abort_glib test case for now, as the
glib assertion message is broken under current Ubuntu (LP: #1689344)
* data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
every report. (LP: #1673557)
-- Brian Murray <br...@ubuntu.com> Wed, 10 May 2017 18:10:32 -0700
--
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/1673557
Title:
/proc/cpuinfo should be collected
Status in apport package in Ubuntu:
Fix Released
Status in whoopsie package in Ubuntu:
Fix Released
Status in apport source package in Trusty:
Fix Released
Status in whoopsie source package in Trusty:
Fix Released
Status in apport source package in Xenial:
Fix Released
Status in whoopsie source package in Xenial:
Fix Released
Status in apport source package in Yakkety:
Fix Released
Status in whoopsie source package in Yakkety:
Fix Released
Bug description:
[Impact]
While some apport reports contain ProcCpuinfo not all of them do and it would
be useful to determine how many users can only run the i386 version of Ubuntu.
Additionally, the existing implementation gathers information about every
processor which is quite lengthy - something smaller would be better.
[Test Case]
1. Run ubuntu-bug 2vcard
2. Observe there is no report key ProcCpuinfoMinimal
With the version of apport from -proposed you will have
ProcCpuinfoMinimal which will contain information about your
processor.
To verify the whoopsie change you'll want to do the following:
1) sudo service whoopsie stop
2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f
3) kill -11 a process (but not the whoopsie one!)
4) confirm sending the report
5) Find the OOPS ID in the whoopsie output
6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID
7) Verify ProcCpuinfoMinimal appears in the OOPS
[Regression Potential]
This exists in Zesty, and Artful and there have been no issues collecting the
information. Even if there are errors in the general ubuntu hook, which was
modified for this SRU, apport will continue collecting information for the
report and just add a traceback to the report about the hook error.
The general Ubuntu hook, possibly add_kernel_info() could be used,
should be modified such that the contents of /proc/cpuinfo are
gathered.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
