Not absolute path in friendly-recovery.service executable path

Bug #1387279 reported by Fran Diéguez on 2014-10-29
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)

Bug Description

After a bad bootup and using systemd as the init system, it shows the next error message

/lib/systemd/system/friendly-recovery.service Executable path is not abolute, ignoring: dmesg --console-off

I have checked that file and changing the line

ExecStartPre=-dmesg --console-off


ExecStartPre=-/bin/dmesg --console-off

fixes the error.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: systemd 208-8ubuntu8
Uname: Linux 3.17.1-031701-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 29 17:36:23 2014
InstallationDate: Installed on 2014-10-22 (7 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)

Fran Diéguez (frandieguez) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers