Failed to start Notification regarding a crash report

[Jan-Philipp Litza]

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.

[Ubuntu Foundations Team Bug Bot (crichton)]

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.]

[Robert (rspier)]

I've tried the patch, and it fixes the problem for me.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[James Lim (jimjh)]

I have reviewed the bug description, and it's accurate.
I have reviewed the patch, and can confirm that I have also separately arrived at the same solution.

[James Lim (jimjh)]

I started noticing this issue after upgrading to Ubuntu 20.10 and disabling Livepatch.