touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #119340
[Bug 1382233] Re: whoopsie does not upload UnreportableReason field in crash reports
This bug was fixed in the package whoopsie - 0.2.49.1
---------------
whoopsie (0.2.49.1) wily-proposed; urgency=medium
* src/whoopsie.c: Move UnreportableReason from fields we don't send to
errors to fields we do, that way we know apport's opinion of the crash.
(LP: #1382233)
-- Brian Murray <brian@xxxxxxxxxx> Mon, 09 Nov 2015 13:09:34 -0800
** Changed in: whoopsie (Ubuntu Wily)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1382233
Title:
whoopsie does not upload UnreportableReason field in crash reports
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie-daisy source package in Precise:
Fix Committed
Status in whoopsie source package in Trusty:
Fix Released
Status in whoopsie source package in Vivid:
Fix Released
Status in whoopsie source package in Wily:
Fix Released
Bug description:
Test Case
---------
1) Edit a .crash file to have an UnreportableReason key and value e.g.
UnreportableReason: Your system is weird.
2) sudo service whoopsie stop
3) start whoopsie pointing to errors.staging.ubuntu.com e.g.
sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com APPORT_REPORT_DIR=/var/crash/ whoopsie -f
4) Put said .crash file in /var/crash/
5) Put a corresponding .upload file in /var/crash/
6) Observe whoopsie uploading the .crash file from the whoopsie log
[16:51:13] Reported OOPS ID 4ea43136-880e-11e5-828e-fa163e1893a8
7) go to errors.staging.ubuntu.com/oops/$OOPS_ID
8) verify the UnreportableReason appears there e.g.:
https://errors.staging.ubuntu.com/oops/4ea43136-880e-11e5-828e-fa163e1893a8
In src/whoopsie.c we can see the following:
/* We would only want this to see how many bugs would otherwise go
* unreported: */
"UnreportableReason",
The comment isn't exactly true. apport uses the UnreportableReason
key to include the following information:
"You have some obsolete package versions installed."
It'd be useful if this information was sent to the Error Tracker so
that we can decide not to ask for a core dump from these crash
reports. The "obsolete package versions" check is done by checking to
see if the most recent available version of the package is installed,
so if someone does not have -updates enabled then that pocket is not
checked and "obsolete package versions" will not be present. This is
desirable because the retracers will check to see if the package
version is available from any pocket.
So if we send UnreportableReason to the Error Tracker we can stop
asking for core dumps and retracing crashes that will fail to retrace.
However, the value for UnreportableReason is translated so this may
not end up helping much.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1382233/+subscriptions
References