By default, Ubuntu Desktop and Server editions both run a background daemon known as whoopsie. This service is intrinsically tied to the Apport crash reporting system. Whenever an application crashes, segfaults, or runs out of memory, Apport generates a massive core dump file, and whoopsie immediately attempts to transmit that crash data back to Canonical’s servers in the background.
While Canonical uses this telemetry data to identify widespread bugs in the operating system, it is an unacceptable privacy violation for enterprise environments. A core dump of a crashed application can contain extremely sensitive information, including API keys, passwords, proprietary source code, or unencrypted database queries that happened to be residing in RAM at the exact millisecond the crash occurred. If you are operating a production server handling confidential data, you cannot allow a background daemon to silently upload memory dumps to the internet. To guarantee absolute data sovereignty, you must completely disable the Whoopsie daemon.
Disabling Whoopsie via Configuration File
The most reliable way to disable the crash reporter is to modify its core configuration file, ensuring the daemon simply refuses to start.
- Open a Terminal session (or connect to your server via SSH).
- Open the primary whoopsie configuration file in a text editor with root privileges:
sudo nano /etc/default/whoopsie - Look for the line that reads:
report_crashes=true - Change the value to false so it looks exactly like this:
report_crashes=false - Save the file (Ctrl + O, then Enter) and exit the text editor (Ctrl + X).
Halting the Active Daemon
Now that the configuration is locked down, you must forcefully terminate the currently running instance of the daemon.
- Stop the running service via systemd:
sudo systemctl stop whoopsie - Permanently disable the service so it cannot be triggered during the next boot sequence:
sudo systemctl disable whoopsie - (Optional but recommended): Mask the service to prevent any other software updates from accidentally re-enabling it in the future:
sudo systemctl mask whoopsie
Your Ubuntu server is now entirely silent. If a database or web server process crashes, the core dump will remain safely isolated on your local hard drive, and no memory telemetry will ever be transmitted to Canonical.