xscreensaver user systemd unit is invalid

Bug #1682380 reported by Dimitri John Ledkov on 2017-04-13
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xscreensaver (Debian)
xscreensaver (Ubuntu)

Bug Description

Apr 13 10:23:57 ottawa systemd[4959]: [/usr/lib/systemd/user/xscreensaver.service:5] Executable path is not absolute, ignoring: xscreensaver
Apr 13 10:23:57 ottawa systemd[4959]: xscreensaver.service: Service lacks both ExecStart= and ExecStop= setting. Refusing.
Apr 13 10:23:57 ottawa systemd[4959]: Reloading.

$ cat /usr/lib/systemd/user/xscreensaver.service



Instead the full path should be used in ExecStart, e.g.


ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xscreensaver 5.36-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Thu Apr 13 10:27:22 2017
InstallationDate: Installed on 2016-01-26 (443 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125)
SourcePackage: xscreensaver
UpgradeStatus: Upgraded to zesty on 2016-12-05 (128 days ago)

Dimitri John Ledkov (xnox) wrote :
Changed in xscreensaver (Ubuntu):
status: New → Confirmed
Jondice (brandon-barker) wrote :

This is still an issue in 17.04

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

Other bug subscribers

Remote bug watches

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