Does Zorin have automatic error reporting

General Help
1

You know the thing...where errors get automatically bundled up and reported back to the Zorin mothership so that coders can work on resolution/upgrades/etc

Does Zorin have this function? If yes, where would one find it to turn it ON? Or is it already ON out there lurking (i.e., no action needed)?

2

There is something installed called whoopsie but this isn't from Zorin; it is from Ubuntu what is for reporting Crashes. If You don't want that, You can uninstall it with sudo apt purge whoopsie

3

Actually I do want it and want to make sure it is ON.
What command would I use to verify that it is loaded and working?

4

I think it is on by default ... but I'm sure to 100%. I think it is a Background Process but You can run it in the Foreground with the Command whoopsie -f

5

Tried that, got this (?):

$ sudo whoopsie -f
[06:18:26] Could not get crash database location.

This worked though...looks inactive

$ systemctl status whoopsie
○ whoopsie.service - crash report submission

  • Loaded: loaded (/lib/systemd/system/whoopsie.service; static)*

  • Active: inactive (dead)*

TriggeredBy: ● whoopsie.path

So did this...

$ sudo apt install whoopsie
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
whoopsie is already the newest version (0.2.77).
The following packages were automatically installed and are no longer required:

  • libfwupdplugin5 libgcab-1.0-0 libsmbios-c2*
    Use 'sudo apt autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
6

Try it with sudo systemctl start whoopsie.service

1 Like
7

dads@dads-110-016:~$ sudo systemctl start whoopsie.service
[sudo] password for dads:
dads@dads-110-016:~$ systemctl status whoopsie
○ whoopsie.service - crash report submission
Loaded: loaded (/lib/systemd/system/whoopsie.service; static)
Active: inactive (dead) since Wed 2026-02-04 13:56:18 EST; 11s ago
TriggeredBy: ● whoopsie.path
Process: 14314 ExecStart=/usr/bin/whoopsie -f --no-polling (code=exited, st>
Main PID: 14314 (code=exited, status=0/SUCCESS)
CPU: 12ms

Feb 04 13:56:18 dads-110-016 systemd[1]: Started crash report submission.
Feb 04 13:56:18 dads-110-016 whoopsie[14314]: [13:56:18] Using lock path: /var/>
Feb 04 13:56:18 dads-110-016 systemd[1]: whoopsie.service: Deactivated successf>
lines 1-11/11 (END)

8

If there is nothing to report... it's not going to keep running nonstop...

1 Like
9

Makes sense...thanks.
I think everything is running fine...I'll consider this one closed. :grin:

1 Like
10

You were not satisfied until you tested it to be sure.
That is Scientific.
:wink: