Hello Brian, or anyone else affected, Accepted whoopsie into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/whoopsie/0.2.24.6ubuntu4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: whoopsie (Ubuntu Trusty) Status: New => Fix Committed ** Changed in: apport (Ubuntu Trusty) Status: New => Fix Committed -- 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 Committed Status in whoopsie source package in Trusty: Fix Committed Status in apport source package in Xenial: Fix Committed Status in whoopsie source package in Xenial: Fix Committed Status in apport source package in Yakkety: Fix Committed Status in whoopsie source package in Yakkety: Fix Committed 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
