@Steve: I think I understand what happens.
On package upgrade, if the job is disabled, then, there is an upstart .override file written to disable it and so, that behavior shouldn't be triggered. I guess this case happens currently if you disable through ubuntu-control-center after a new installation as I discovered that there is another library (another source package), using that file: whoopsie-preferences that can read/set values in this file.
However, I see that there is another value about report_metrics that we don't use for job enablement status.
I propose to do the following on ubuntu-control-center: report crashes -> add the override and call systemctl disable if installed, change whoopsie-preferences to be aware of those files and detect usptart/systemd for current values.
This should prevent whoopsie to loop when the job is disabled and only have the current enablement state in one place (through libwhoopsie-preferences).
I can set the other changes that you described as well to fix the upstart job, just following what you see as I'm in no way an upstart expert :)
@Steve: I think I understand what happens. control- center after a new installation as I discovered that there is another library (another source package), using that file: whoopsie- preferences that can read/set values in this file.
On package upgrade, if the job is disabled, then, there is an upstart .override file written to disable it and so, that behavior shouldn't be triggered. I guess this case happens currently if you disable through ubuntu-
However, I see that there is another value about report_metrics that we don't use for job enablement status. control- center: report crashes -> add the override and call systemctl disable if installed, change whoopsie- preferences to be aware of those files and detect usptart/systemd for current values.
I propose to do the following on ubuntu-
This should prevent whoopsie to loop when the job is disabled and only have the current enablement state in one place (through libwhoopsie- preferences) .
I can set the other changes that you described as well to fix the upstart job, just following what you see as I'm in no way an upstart expert :)