[Bug 1871308] Re: Failed to start Notification regarding a crash report

[Ubuntu Foundations Team Bug Bot]

The attachment "update-notifier-crash.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1871308

Title:
  Failed to start Notification regarding a crash report

Status in update-notifier package in Ubuntu:
  New

Bug description:
  journalctl has these nasty messages when the whoopsie service is
  disabled:

  systemd[3290]: Starting Notification regarding a crash report...
  update-notifier-crash[38295]: /usr/bin/whoopsie
  systemd[3290]: update-notifier-crash.service: Main process exited, code=exited, status=1/FAILURE
  systemd[3290]: update-notifier-crash.service: Failed with result 'exit-code'.
  systemd[3290]: Failed to start Notification regarding a crash report.

  It is caused by /usr/lib/update-notifier/update-notifier-crash having
  `set -e` at the top but then doing checks like `systemctl -q is-
  enabled whoopsie` outside of an `if`. A simple fix that also silences
  the line with "/usr/bin/whoopsie" is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1871308/+subscriptions