tightVNC and systemd

Greetings,

I've run into a problem with tightVNC and systemd on an Ubuntu 16.04.1 LTS
system.  We're running the version from the Ubuntu repository,
tightvncserver 1.3.10.  The problem is coming from the perl script
/usr/bin/tightvncserver (which is symlinked to vncserver).

It runs fine for individual users (with the usual tweaks).  However,
when trying to start it from a systemd service file, it fails.

I've pinned it down to lines 185-186 in /usr/bin/tightvncserver:

 ($z,$z,$mode) = stat ("$vncUserDir");
 if (-d _ || !-o _ || ($vncUserDirUnderTmp && ($mode & 0777) != 0700)) {
 	die "$prog: Wrong type or access mode of $vncUserDir.\n";
 }

No matter I've included "User=foo" and "Group=foo" in the service file,
it's clearly being *interpreted* as running as root, not the user "foo".

I hope there's a simple fix for this, because I really don't want to just
abandon tightVNC because I can't run it as a started service.  (And I really
hate systemd, but that's another issue.)

Thanks in advance,
--
	Dave Ihnat
	[email protected]


___________________________________________________________
TightVNC mailing list, [email protected]
To change your subscription or to UNSUBSCRIBE, please visit
https://lists.sourceforge.net/lists/listinfo/vnc-tight-list