This bug was fixed in the package sysvinit - 2.88dsf-53.2ubuntu10 --------------- sysvinit (2.88dsf-53.2ubuntu10) vivid; urgency=medium
* invoke-rc.d: There are two cases when "systemctl is-enabled" fails: Either the unit exists and is disabled, or if the unit doesn't exist (or only in a generator output dir). In the latter case we do not want to prevent the startup of a unit. (LP: #1429035) -- Martin Pitt <martin.p...@ubuntu.com> Fri, 06 Mar 2015 10:55:49 +0100 ** Changed in: sysvinit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1429035 Title: invoke-rc.d doesn't start freshly installed services which only have an init.d script Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit package in Debian: New Bug description: On a fresh and minimal vivid installation running systemd, install apache2. It won't be running after starting: $ sudo sh -x /usr/sbin/invoke-rc.d apache2 start + systemctl --quiet is-system-running + sctl_args=--job-mode=ignore-dependencies + systemctl --quiet is-enabled apache2.service + [ start = start ] + exit 0 That's because of our patch in invoke-rc.d to not start disabled systemd services. But this fails here as after a fresh installation the sysv-generator didn't run yet, so there is no apache2.service. Even after reboot, is-enabled & friends don't take generated units into account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1429035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp