Whoopsie: privacy questions?

system: jetson nano 2gb
OS: jetpack 4.4.1

repro steps:

  1. tail -f /var/log/syslog to monitor
  2. whoopsie logged:

Nov 10 20:47:08 jetson whoopsie[4499]: [20:47:08] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Nov 10 20:47:08 jetson dbus-daemon[3781]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Nov 10 20:47:08 jetson systemd[1]: Started Network Manager Script Dispatcher Service.
Nov 10 20:47:08 jetson nm-dispatcher: req:1 ‘connectivity-change’: new request (2 scripts)
Nov 10 20:47:08 jetson nm-dispatcher: req:1 ‘connectivity-change’: start running ordered scripts…
Nov 10 20:47:08 jetson whoopsie[4499]: [20:47:08] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Nov 10 20:47:08 jetson whoopsie[4499]: [20:47:08] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Nov 10 20:47:09 jetson whoopsie[4499]: [20:47:09] online

Could someone provide privacy details on what is being sent with the crash and to where? And is there an option to disable whoopsie sending crash details? Not sure what crashed to cause whoopsie to start; logged in using ssh and not GUI.


This is an Ubuntu mechanism, and would send reports to the company which maintains Ubuntu, Canonical. I think this is mostly anonymized, but there may be some incompleteness to this, such as file names. When you manually allow this from a GUI it offers to show you all data, and it does not just submit without asking. When the data is presented it allows editing or removing items.

This is a command line way of disabling crash reports:

The gist is to edit “/etc/default/apport” to be “enabled=0”, and probably to also disable the service via “sudo systemctl disable apport”. The file edit will work even if the crash mechanism runs, the “disable” will prevent this from running automatically.

1 Like