systemd is in degraded state if whoopsie is disabled
Bug #1390014 reported by
Didier Roche-Tolomelli
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| whoopsie (Ubuntu) |
Fix Released
|
Undecided
|
Didier Roche-Tolomelli | ||
Bug Description
The ExecStartPre, grepping if whoopsie is enabled returns 1
Consequence:
the service doesn't start (as expected) but systemd is reported a degraded state.
What to do:
- drop the value from the conffile in /etc/default/
- in the preinst, systemctl disable whoopsie if the current version has report_
| Changed in whoopsie (Ubuntu): | |
| status: | New → Triaged |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in whoopsie (Ubuntu): | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
This bug was fixed in the package whoopsie - 0.2.42
---------------
whoopsie (0.2.42) vivid; urgency=medium
* Disable whoopsie in systemd if the sysadmin set it as disabled in
/etc/
- remove report_crashes key from the conffile
- if was set to false, generate an upstart override and disable it
with systemctl
- remove the condition in the upstart job, just use the override
* Add Environment= to units instead of executing a shell script to set
the daemon env.
* Ship an init script file and handle upstart/init startup being disabled
depending on /etc/default/
* Use systemd debhelper sequence now.
-- Didier Roche <email address hidden> Thu, 06 Nov 2014 12:32:06 +0100