Ubuntu internal error messages and handling

Ubuntu Desktop is preinstalled with Apport, an error collection system that collects software crashes, unhandled exceptions, and others, including program bugs, and generates crash reports for debugging purposes. When an application crashes or a bug occurs, Apport warns the user through the popup window and asks the user if the crash report is submitted:

"Sorry, the application XXXX has closed unexpectedly."
"Sorry, the application xxxx was closed unexpectedly. ”
"Sorry, Ubuntu XX. XX had experienced an internal error. "
"Sorry, Ubuntu XX. An internal error occurred in XX. ”
"System program problem detected."
"A system program problem was detected. ”

The reality is not that Ubuntu is prone to internal errors, but once the program crashes, it generates a. crash file that logs the program crash information and saves it in the directory:
/var/crash/
As long as you do not process, each boot will prompt you to have errors. In other words: the error is not necessarily something wrong, but there have been errors did not deal with.

Solution Solutions
(1) Temporarily close Apport error report
To temporarily turn off Apport, use the command
sudo service apport stop
Note: Apport will continue to open after restarting the Ubuntu system

(2) Permanently close apport Error report
To permanently close apport, edit/etc/default/apport, modify the following parameters
Enabled=0
After restarting the Ubuntu system, the Apport will automatically turn off
If you no longer use apport, you can completely remove the service
sudo apt-get purge apport

(3) Simple processing: Delete. crash file
To the/var/crash/directory to see the crash file, if it is not a big problem (usually not a big problem), delete the directory of the crash file, and then no longer report errors.

Ubuntu internal error messages and handling