systemd unit file uses relative rather than absolute paths

Bug #1399947 reported by Tom
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
friendly-recovery (Ubuntu)
New
Undecided
Unassigned

Bug Description

On boot, journalctl reports this error:
[/lib/systemd/system/friendly-recovery.service:14] Executable path is not absolute, ignoring: dmesg --console-off

The fix is:
sed 's#dmesg#/bin/dmesg#' /lib/systemd/system/friendly-recovery.service

Background:
Ubuntu 14.10, with systemd
friendly-recovery: 0.2.26

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: friendly-recovery 0.2.26 [modified: lib/systemd/system/friendly-recovery.service]
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Sat Dec 6 15:44:23 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-11-04 (762 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
PackageArchitecture: all
SourcePackage: friendly-recovery
UpgradeStatus: Upgraded to utopic on 2014-11-22 (14 days ago)

Revision history for this message
Tom (tom5559-deactivatedaccount) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.