[systemd] "Unit whoopsie.service failed to load" on upgrade from trusty

[N1ck 7h0m4d4k15]

This is from todays update (17 May 2014).

Preparing to unpack .../whoopsie_0.2.26_amd64.deb ...
Failed to issue method call: Unit whoopsie.service not loaded.
invoke-rc.d: initscript whoopsie, action "stop" failed.
dpkg: warning: subprocess old pre-removal script returned error exit status 5
dpkg: trying script from the new package instead ...
Failed to issue method call: Unit whoopsie.service not loaded.
dpkg: error processing archive /var/cache/apt/archives/whoopsie_0.2.26_amd64.deb (--unpack):
 subprocess new pre-removal script returned error exit status 5
Failed to issue method call: Unit whoopsie.service failed to load: No such file or directory. See system logs and 'systemctl status whoopsie.service' for details.
invoke-rc.d: initscript whoopsie, action "start" failed.
dpkg: error while cleaning up:
 subprocess installed post-installation script returned error exit status 6

systemctl status whoopsie.service

whoopsie.service
   Loaded: error (Reason: No such file or directory)
   Active: inactive (dead)

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: whoopsie 0.2.25
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
CrashReports:
 600:0:116:445941:2014-05-17 15:11:33.472012637 +0300:2014-05-17 15:11:32.800012636 +0300:/var/crash/whoopsie.0.crash
 600:0:116:426994:2014-05-17 00:01:47.482882175 +0300:2014-05-17 15:10:21.976012534 +0300:/var/crash/nvidia-prime.0.crash
CurrentDesktop: Unity
Date: Sat May 17 15:21:30 2014
InstallationDate: Installed on 2014-03-24 (53 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323)
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Martin Pitt (pitti)]

I'm afraid this is a scenario which we can't support: Booting trusty with systemd and then upgrading. One first needs to upgrade to utopic (which then has all the systemd enablement work) and *then* boot systemd. Thanks!

[N1ck 7h0m4d4k15 (nicktux)]

If utopic has this service enabled by default, this problem will not exist.
This bug was an update about this service (whoopsie package) in order to inform the developers of ubuntu/systemd, that it failed , like the nvidia-prime package (same thing). Just to inform you about the problem.

I can upgrade all the packages without a problem if I boot with Init (and not systemd) as PID 1, but this is not my purpose here. The purpose is to inform you for any kind of problem I face on systemd (I have set up a testing utopic system - upgraded from trusty in real hardware and not VirtualBox or alike) just for systemd testing purposes.