upgrade of whoopsie fails due to report_crashes=false
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
whoopsie (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Cheers,
I'm using systemd and have set report_
The systemctl service
$ systemctl status whoopsie.service
whoopsie.service - crash report submission daemon
Loaded: loaded (/lib/systemd/
Active: failed (Result: start-limit) since Fr 2015-02-27 13:52:53 CET; 7s ago
Process: 22882 ExecStartPre=
fails as one would expect; but having these kind of startup requirements in the systemd service is probably a bad idea, especially as it leaves the package unconfigured:
$ sudo dpkg --configure --pending
Setting up whoopsie (0.2.39ubuntu0.2) ...
Job for whoopsie.service failed. See 'systemctl status whoopsie.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript whoopsie, action "start" failed.
dpkg: error processing package whoopsie (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
whoopsie
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: whoopsie 0.2.39ubuntu0.2
ProcVersionSign
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CrashReports: 640:0:111:
CurrentDesktop: GNOME
Date: Fri Feb 27 13:54:04 2015
InstallationDate: Installed on 2013-05-06 (661 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
RelatedPackageV
SourcePackage: whoopsie
UpgradeStatus: Upgraded to utopic on 2014-10-23 (126 days ago)
modified.
[General]
report_
mtime.conffile.