> Perhaps /etc/default/apport enabled=0/1 could be deprecated in favor of that key.
No, it can't be deprecated (because servers/cloud/Non-GNOME flavors) nor synchronized (because multiple users on one system and privilege boundary). A user gsetting can *not* be used to entirely disable the generation of crash reports in /var/crash. But it is simple and straightforward to query it in apport-gtk to suppress the upload/reporting of crash reports.
The main blocker here is that the report-technical-problems is off by default, which we don't want in Ubuntu -- it should be consistent with the system-wide "on" default, where it asks for every crash whether to upload it.
Another problem is that we already have some setting for this -- in ubuntu-system-settings "security & privacy" there are options for disabling apport error reports. This would then be redundant and preferrably get moved to use the same key?
> Perhaps /etc/default/apport enabled=0/1 could be deprecated in favor of that key.
No, it can't be deprecated (because servers/ cloud/Non- GNOME flavors) nor synchronized (because multiple users on one system and privilege boundary). A user gsetting can *not* be used to entirely disable the generation of crash reports in /var/crash. But it is simple and straightforward to query it in apport-gtk to suppress the upload/reporting of crash reports.
The main blocker here is that the report- technical- problems is off by default, which we don't want in Ubuntu -- it should be consistent with the system-wide "on" default, where it asks for every crash whether to upload it.
Another problem is that we already have some setting for this -- in ubuntu- system- settings "security & privacy" there are options for disabling apport error reports. This would then be redundant and preferrably get moved to use the same key?