[Bug 1756937] Re: report_crashes setting not written
Launchpad Bug Tracker
1756937 at bugs.launchpad.net
Sat Apr 7 02:29:05 UTC 2018
This bug was fixed in the package whoopsie - 0.2.62
---------------
whoopsie (0.2.62) bionic; urgency=medium
* Remove /etc/whoopsie file as its contents are not read by whoopsie.
(LP: #1756937)
-- Brian Murray <brian at ubuntu.com> Fri, 06 Apr 2018 13:38:15 -0700
** Changed in: whoopsie (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1756937
Title:
report_crashes setting not written
Status in whoopsie package in Ubuntu:
Fix Released
Status in whoopsie-preferences package in Ubuntu:
Invalid
Status in whoopsie source package in Bionic:
Fix Released
Status in whoopsie-preferences source package in Bionic:
Invalid
Bug description:
whoopsie was built with two settings, report_metrics (statistics like
popcon - currently unused) and report_crashes (for reporting crash
reports to the Error Tracker). However, only report_metrics gets
written to '/etc/whoopsie' while the setting for report_crashes is
defined by having whoopsie.disable. This complicates matters as there
are two places to look for whoopsie settings '/etc/whoopsie' and
checking for a .disable file. It'd be best if "report_crashes" was
also written to '/etc/whoopsie'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1756937/+subscriptions
More information about the foundations-bugs
mailing list