I believe the following changes may have fixed this particular bug:
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 protected]> Thu, 06 Nov 2014 12:32:06 +0100
Do you mind double checking? Thanks!
** Changed in: whoopsie (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1392588
Title:
whoopsie's postinst fails when systemd is running and
report_crashes=false in /etc/default/whoopsie
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1392588/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
