systemd is in degraded state if whoopsie is disabled

Bug #1390014 reported by Didier Roche on 2014-11-06
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie (Ubuntu)
Undecided
Didier Roche

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/whoopsie
- in the preinst, systemctl disable whoopsie if the current version has report_crashes=false

Didier Roche (didrocks) on 2014-11-06
Changed in whoopsie (Ubuntu):
status: New → Triaged
Launchpad Janitor (janitor) wrote :

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/default/whoopsie: (LP: #1390014)
    - 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/whoopsie.
  * Use systemd debhelper sequence now.
 -- Didier Roche <email address hidden> Thu, 06 Nov 2014 12:32:06 +0100

Changed in whoopsie (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers