is it safe to remove apport?
Do I break anything if I
sudo apt-get purge apport
I have my secret business plan for world domination and who knows what's in a core dump?
I've seen Ubuntu (in particular dconf
) recreate config settings. I know how to disable it but can't trust it to remain disabled. Hence my question.
Yea Yea I know know my different distro ... but I'd like to use Ubuntu if I can.
uninstall purge apport
add a comment |
Do I break anything if I
sudo apt-get purge apport
I have my secret business plan for world domination and who knows what's in a core dump?
I've seen Ubuntu (in particular dconf
) recreate config settings. I know how to disable it but can't trust it to remain disabled. Hence my question.
Yea Yea I know know my different distro ... but I'd like to use Ubuntu if I can.
uninstall purge apport
1
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:
– SDsolar
May 1 '18 at 17:59
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41
add a comment |
Do I break anything if I
sudo apt-get purge apport
I have my secret business plan for world domination and who knows what's in a core dump?
I've seen Ubuntu (in particular dconf
) recreate config settings. I know how to disable it but can't trust it to remain disabled. Hence my question.
Yea Yea I know know my different distro ... but I'd like to use Ubuntu if I can.
uninstall purge apport
Do I break anything if I
sudo apt-get purge apport
I have my secret business plan for world domination and who knows what's in a core dump?
I've seen Ubuntu (in particular dconf
) recreate config settings. I know how to disable it but can't trust it to remain disabled. Hence my question.
Yea Yea I know know my different distro ... but I'd like to use Ubuntu if I can.
uninstall purge apport
uninstall purge apport
asked May 19 '12 at 16:40
geckogecko
5941522
5941522
1
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:
– SDsolar
May 1 '18 at 17:59
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41
add a comment |
1
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:
– SDsolar
May 1 '18 at 17:59
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41
1
1
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:
sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:– SDsolar
May 1 '18 at 17:59
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:
sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:– SDsolar
May 1 '18 at 17:59
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41
add a comment |
2 Answers
2
active
oldest
votes
Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data.
Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons:
Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.
This is mitigated by the fact that it presents you what will be sent to the bug tracker, and that all crash report bugs are private by default, limited to the Ubuntu bug triaging team. We can reasonably expect developers and technically savvy users, who run the development release, to be aware of this and judge whether it is appropriate to file a crash report. But we shouldn't assume that every Ubuntu user of stable releases is able to do so.
During the development release we already collect thousands of crash reports, much more than we can ever fix. Continuing to collect those for stable releases is not really useful, since
- The most important crashes have already been discovered in the development release.
- The less important ones are not suitable for getting fixed in stable releases (see https://wiki.ubuntu.com/StableReleaseUpdates
- Asking users to send crash reports to us is insincere, since we can't possibly answer and deal with all of them.
Data collection from apport takes a nontrivial amount of CPU and I/O resources, which slow down the computer and don't allow you to restart the crashed program for several seconds.
If apport is currently active you can disable it by editing...
sudo nano /etc/default/apport
and follow the comments:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Set it to 0.
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 andenabled
is definitely set to 1
– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
add a comment |
It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy.
Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport
. Change enabled=1
to enabled=0
. (1
means it's enabled. 0
means it's disabled.) Then reboot (or manually stop the service) to apply the change. See the Apport documentation, and especially the section on current versions of Ubuntu, for more details.
Apport does not use gconf
or dconf
for setting whether or not it is enabled. It is a system service, and whether or not it runs (i.e., whether or not it intercepts crashes, creates crash dumps, and makes it possible for the user to submit them to Launchpad or other web services) is not determined by any user's per-user settings.
If you do remove Apport, you will lose the ability to use it to report non-crash bugs (with Help > Report a Bug) or running ubuntu-bug
. If then you or another administrator decides to reinstall it for this purpose, then depending on how you removed it and what system you are running when you reinstall it, it might then become enabled for intercepting crashes and creating/submitting core dumps.
So if you're vigilant (or even if you're not), disabling Apport should be quite sufficient. If you're not vigilant, then uninstalling Apport might actually make it more likely to intercept and submit crash data in the future (as described above), if you reinstall it for its other functionality and forget to check if the crash reporting service is enabled.
If you do decide to remove Apport, you can check first to see if doing so would break everything, by simulating its removal:
apt-get -s remove apport
That will show you what other packages would be removed as a consequence. Then, to actually remove it:
sudo apt-get remove apport
Please note that you probably do not want to purge
it, since if you remove it you'll want to keep the apport
configuration file in /etc/default
that has enabled=0
. (Just know that this doesn't necessarily guarantee that the crash reporting service will never be enabled upon reinstallation, in any future version.)
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output ofcat /etc/default/apport
?
– Eliah Kagan
May 19 '12 at 17:01
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f139424%2fis-it-safe-to-remove-apport%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data.
Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons:
Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.
This is mitigated by the fact that it presents you what will be sent to the bug tracker, and that all crash report bugs are private by default, limited to the Ubuntu bug triaging team. We can reasonably expect developers and technically savvy users, who run the development release, to be aware of this and judge whether it is appropriate to file a crash report. But we shouldn't assume that every Ubuntu user of stable releases is able to do so.
During the development release we already collect thousands of crash reports, much more than we can ever fix. Continuing to collect those for stable releases is not really useful, since
- The most important crashes have already been discovered in the development release.
- The less important ones are not suitable for getting fixed in stable releases (see https://wiki.ubuntu.com/StableReleaseUpdates
- Asking users to send crash reports to us is insincere, since we can't possibly answer and deal with all of them.
Data collection from apport takes a nontrivial amount of CPU and I/O resources, which slow down the computer and don't allow you to restart the crashed program for several seconds.
If apport is currently active you can disable it by editing...
sudo nano /etc/default/apport
and follow the comments:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Set it to 0.
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 andenabled
is definitely set to 1
– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
add a comment |
Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data.
Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons:
Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.
This is mitigated by the fact that it presents you what will be sent to the bug tracker, and that all crash report bugs are private by default, limited to the Ubuntu bug triaging team. We can reasonably expect developers and technically savvy users, who run the development release, to be aware of this and judge whether it is appropriate to file a crash report. But we shouldn't assume that every Ubuntu user of stable releases is able to do so.
During the development release we already collect thousands of crash reports, much more than we can ever fix. Continuing to collect those for stable releases is not really useful, since
- The most important crashes have already been discovered in the development release.
- The less important ones are not suitable for getting fixed in stable releases (see https://wiki.ubuntu.com/StableReleaseUpdates
- Asking users to send crash reports to us is insincere, since we can't possibly answer and deal with all of them.
Data collection from apport takes a nontrivial amount of CPU and I/O resources, which slow down the computer and don't allow you to restart the crashed program for several seconds.
If apport is currently active you can disable it by editing...
sudo nano /etc/default/apport
and follow the comments:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Set it to 0.
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 andenabled
is definitely set to 1
– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
add a comment |
Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data.
Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons:
Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.
This is mitigated by the fact that it presents you what will be sent to the bug tracker, and that all crash report bugs are private by default, limited to the Ubuntu bug triaging team. We can reasonably expect developers and technically savvy users, who run the development release, to be aware of this and judge whether it is appropriate to file a crash report. But we shouldn't assume that every Ubuntu user of stable releases is able to do so.
During the development release we already collect thousands of crash reports, much more than we can ever fix. Continuing to collect those for stable releases is not really useful, since
- The most important crashes have already been discovered in the development release.
- The less important ones are not suitable for getting fixed in stable releases (see https://wiki.ubuntu.com/StableReleaseUpdates
- Asking users to send crash reports to us is insincere, since we can't possibly answer and deal with all of them.
Data collection from apport takes a nontrivial amount of CPU and I/O resources, which slow down the computer and don't allow you to restart the crashed program for several seconds.
If apport is currently active you can disable it by editing...
sudo nano /etc/default/apport
and follow the comments:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Set it to 0.
Yes, you can remove apport but unless you actually agree(d) on apport sending information it will never send any data.
Even better: The automatic crash interception component of apport is disabled by default in stable releases for a number of reasons:
Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material.
This is mitigated by the fact that it presents you what will be sent to the bug tracker, and that all crash report bugs are private by default, limited to the Ubuntu bug triaging team. We can reasonably expect developers and technically savvy users, who run the development release, to be aware of this and judge whether it is appropriate to file a crash report. But we shouldn't assume that every Ubuntu user of stable releases is able to do so.
During the development release we already collect thousands of crash reports, much more than we can ever fix. Continuing to collect those for stable releases is not really useful, since
- The most important crashes have already been discovered in the development release.
- The less important ones are not suitable for getting fixed in stable releases (see https://wiki.ubuntu.com/StableReleaseUpdates
- Asking users to send crash reports to us is insincere, since we can't possibly answer and deal with all of them.
Data collection from apport takes a nontrivial amount of CPU and I/O resources, which slow down the computer and don't allow you to restart the crashed program for several seconds.
If apport is currently active you can disable it by editing...
sudo nano /etc/default/apport
and follow the comments:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1
Set it to 0.
edited May 19 '12 at 17:06
answered May 19 '12 at 16:51
RinzwindRinzwind
209k28402537
209k28402537
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 andenabled
is definitely set to 1
– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
add a comment |
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 andenabled
is definitely set to 1
– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
Ok thanks for info, very helpful. So basically turn it off, then remove it, but leaving the config file, and never connect the machine to the internet ... seems OK, thanks for help.
– gecko
May 19 '12 at 19:02
2
2
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
How do you get "and never connect the machine to the internet" from Rinzwind's answer?
– user25656
May 20 '12 at 3:16
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
Why never connect to the internet!? All you need to do is turn it off. You do not even need to delete apport.
– Rinzwind
May 20 '12 at 6:31
FWIW we are on 14.04 and
enabled
is definitely set to 1– Frew Schmidt
Mar 12 '18 at 21:09
FWIW we are on 14.04 and
enabled
is definitely set to 1– Frew Schmidt
Mar 12 '18 at 21:09
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
Refer to this answer for an updated solution (for Ubuntu 16.04+) .
– whoan
Apr 14 '18 at 1:46
add a comment |
It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy.
Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport
. Change enabled=1
to enabled=0
. (1
means it's enabled. 0
means it's disabled.) Then reboot (or manually stop the service) to apply the change. See the Apport documentation, and especially the section on current versions of Ubuntu, for more details.
Apport does not use gconf
or dconf
for setting whether or not it is enabled. It is a system service, and whether or not it runs (i.e., whether or not it intercepts crashes, creates crash dumps, and makes it possible for the user to submit them to Launchpad or other web services) is not determined by any user's per-user settings.
If you do remove Apport, you will lose the ability to use it to report non-crash bugs (with Help > Report a Bug) or running ubuntu-bug
. If then you or another administrator decides to reinstall it for this purpose, then depending on how you removed it and what system you are running when you reinstall it, it might then become enabled for intercepting crashes and creating/submitting core dumps.
So if you're vigilant (or even if you're not), disabling Apport should be quite sufficient. If you're not vigilant, then uninstalling Apport might actually make it more likely to intercept and submit crash data in the future (as described above), if you reinstall it for its other functionality and forget to check if the crash reporting service is enabled.
If you do decide to remove Apport, you can check first to see if doing so would break everything, by simulating its removal:
apt-get -s remove apport
That will show you what other packages would be removed as a consequence. Then, to actually remove it:
sudo apt-get remove apport
Please note that you probably do not want to purge
it, since if you remove it you'll want to keep the apport
configuration file in /etc/default
that has enabled=0
. (Just know that this doesn't necessarily guarantee that the crash reporting service will never be enabled upon reinstallation, in any future version.)
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output ofcat /etc/default/apport
?
– Eliah Kagan
May 19 '12 at 17:01
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
add a comment |
It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy.
Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport
. Change enabled=1
to enabled=0
. (1
means it's enabled. 0
means it's disabled.) Then reboot (or manually stop the service) to apply the change. See the Apport documentation, and especially the section on current versions of Ubuntu, for more details.
Apport does not use gconf
or dconf
for setting whether or not it is enabled. It is a system service, and whether or not it runs (i.e., whether or not it intercepts crashes, creates crash dumps, and makes it possible for the user to submit them to Launchpad or other web services) is not determined by any user's per-user settings.
If you do remove Apport, you will lose the ability to use it to report non-crash bugs (with Help > Report a Bug) or running ubuntu-bug
. If then you or another administrator decides to reinstall it for this purpose, then depending on how you removed it and what system you are running when you reinstall it, it might then become enabled for intercepting crashes and creating/submitting core dumps.
So if you're vigilant (or even if you're not), disabling Apport should be quite sufficient. If you're not vigilant, then uninstalling Apport might actually make it more likely to intercept and submit crash data in the future (as described above), if you reinstall it for its other functionality and forget to check if the crash reporting service is enabled.
If you do decide to remove Apport, you can check first to see if doing so would break everything, by simulating its removal:
apt-get -s remove apport
That will show you what other packages would be removed as a consequence. Then, to actually remove it:
sudo apt-get remove apport
Please note that you probably do not want to purge
it, since if you remove it you'll want to keep the apport
configuration file in /etc/default
that has enabled=0
. (Just know that this doesn't necessarily guarantee that the crash reporting service will never be enabled upon reinstallation, in any future version.)
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output ofcat /etc/default/apport
?
– Eliah Kagan
May 19 '12 at 17:01
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
add a comment |
It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy.
Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport
. Change enabled=1
to enabled=0
. (1
means it's enabled. 0
means it's disabled.) Then reboot (or manually stop the service) to apply the change. See the Apport documentation, and especially the section on current versions of Ubuntu, for more details.
Apport does not use gconf
or dconf
for setting whether or not it is enabled. It is a system service, and whether or not it runs (i.e., whether or not it intercepts crashes, creates crash dumps, and makes it possible for the user to submit them to Launchpad or other web services) is not determined by any user's per-user settings.
If you do remove Apport, you will lose the ability to use it to report non-crash bugs (with Help > Report a Bug) or running ubuntu-bug
. If then you or another administrator decides to reinstall it for this purpose, then depending on how you removed it and what system you are running when you reinstall it, it might then become enabled for intercepting crashes and creating/submitting core dumps.
So if you're vigilant (or even if you're not), disabling Apport should be quite sufficient. If you're not vigilant, then uninstalling Apport might actually make it more likely to intercept and submit crash data in the future (as described above), if you reinstall it for its other functionality and forget to check if the crash reporting service is enabled.
If you do decide to remove Apport, you can check first to see if doing so would break everything, by simulating its removal:
apt-get -s remove apport
That will show you what other packages would be removed as a consequence. Then, to actually remove it:
sudo apt-get remove apport
Please note that you probably do not want to purge
it, since if you remove it you'll want to keep the apport
configuration file in /etc/default
that has enabled=0
. (Just know that this doesn't necessarily guarantee that the crash reporting service will never be enabled upon reinstallation, in any future version.)
It is probably safe to remove Apport, but doing so is completely unnecessary for protecting your privacy.
Apport's core dump interception is disabled by default on stable versions of Ubuntu. To completely disable Apport, edit /etc/default/apport
. Change enabled=1
to enabled=0
. (1
means it's enabled. 0
means it's disabled.) Then reboot (or manually stop the service) to apply the change. See the Apport documentation, and especially the section on current versions of Ubuntu, for more details.
Apport does not use gconf
or dconf
for setting whether or not it is enabled. It is a system service, and whether or not it runs (i.e., whether or not it intercepts crashes, creates crash dumps, and makes it possible for the user to submit them to Launchpad or other web services) is not determined by any user's per-user settings.
If you do remove Apport, you will lose the ability to use it to report non-crash bugs (with Help > Report a Bug) or running ubuntu-bug
. If then you or another administrator decides to reinstall it for this purpose, then depending on how you removed it and what system you are running when you reinstall it, it might then become enabled for intercepting crashes and creating/submitting core dumps.
So if you're vigilant (or even if you're not), disabling Apport should be quite sufficient. If you're not vigilant, then uninstalling Apport might actually make it more likely to intercept and submit crash data in the future (as described above), if you reinstall it for its other functionality and forget to check if the crash reporting service is enabled.
If you do decide to remove Apport, you can check first to see if doing so would break everything, by simulating its removal:
apt-get -s remove apport
That will show you what other packages would be removed as a consequence. Then, to actually remove it:
sudo apt-get remove apport
Please note that you probably do not want to purge
it, since if you remove it you'll want to keep the apport
configuration file in /etc/default
that has enabled=0
. (Just know that this doesn't necessarily guarantee that the crash reporting service will never be enabled upon reinstallation, in any future version.)
edited Nov 13 '14 at 19:38
Josh Kelley
231214
231214
answered May 19 '12 at 16:51
Eliah KaganEliah Kagan
83.1k22229369
83.1k22229369
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output ofcat /etc/default/apport
?
– Eliah Kagan
May 19 '12 at 17:01
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
add a comment |
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output ofcat /etc/default/apport
?
– Eliah Kagan
May 19 '12 at 17:01
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
I still get the "Something broke: send crash report (Y/N)" still coming up on this system, which is 12.04 and installed from a release ISO. I do not actually upgrade this one machine for security reasons (which sounds odd since it means i also miss security patches .. I am ok with this as it doesn't really have a proper net connection). Should I format and reload the system?
– gecko
May 19 '12 at 16:59
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output of
cat /etc/default/apport
?– Eliah Kagan
May 19 '12 at 17:01
@gecko If you had previously overridden the default and enabled Apport (rather than it being enabled by default because you installed a beta or late alpha system), then it may not be disabled when your system goes from beta to release. In any case, are you saying that Apport is coming up even though it is disabled in the configuration file? What is the output of
cat /etc/default/apport
?– Eliah Kagan
May 19 '12 at 17:01
1
1
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
@Eliah: thanks for pointing out how to disable apport. After my recent upgrade to 12.04, I began getting queries: "send crash report?" As far as I know, though, I am running the "stable" ubuntu, so I'm not sure why /etc/default/apport was in the "enabled" state. I've now set enabled=0... thanks for the tip!
– George McNinch
May 24 '12 at 18:55
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f139424%2fis-it-safe-to-remove-apport%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
5 years later, how did the secret business plan for world domination work out so far? ;)
– Christopher K.
Jun 27 '17 at 8:35
LOL from May 2018 (v16.04). This is funny. By the way, be sure to add this step:
sudo rm /etc/cron.daily/apport
and also check out this other bit of data leakage: askubuntu.com/questions/84831/… and this one which is new in 18.04: askubuntu.com/questions/1027532/…:– SDsolar
May 1 '18 at 17:59
Personally I prefer (# sudo apport stop). Shortcut could be made to it, also. After all safety is a multi-directional process. Thus, the question needs consideration. I have the same issue on my Ubuntu 16.04.
– chris
Feb 4 at 13:41