This has been asked many times in some form or another but none of the advice seems to have helped.
I want to run syndaemon after I login to the GUI, but I always have to start it manually
$ systemctl --user status syndaemon.service ● syndaemon.service - Syndaemon Service Loaded: loaded (/home/tastywheat/.config/systemd/user/syndaemon.service; enabled; vendor preset: enabled) Active: inactive (dead) $ systemctl --user start syndaemon.service $ systemctl --user status syndaemon.service ● syndaemon.service - Syndaemon Service Loaded: loaded (/home/tastywheat/.config/systemd/user/syndaemon.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2021-04-11 00:33:54 CDT; 3s ago Main PID: 5032 (syndaemon) CGroup: / └─5032 /usr/bin/syndaemon -i 0.8 -R -t -k It doesn't appear that there was any attempt to start the service either (it only shows here because I started it manually).
$ grep -ir syndaemon /var/log/syslog Apr 11 00:33:54 xtrnmntr systemd[1068]: Started Syndaemon Service. I also followed advice regarding the use of loginctl enable-linger.
$ find /var/lib/systemd/linger/ /var/lib/systemd/linger/ /var/lib/systemd/linger/tastywheat And I tried an alternative method of modifying logind.conf.
$ grep -ir tastywheat /etc/systemd/logind.conf KillExcludeUsers=tastywheat Also my user-service, in case that's at fault:
$ cat ~/.config/systemd/user/syndaemon.service [Unit] Description=Syndaemon Service [Service] ExecStart=/usr/bin/syndaemon -i 0.8 -R -t -k [Install] WantedBy=default.target I guess I don't mind if I have to move this service into /etc/systemd but I didn't want to have to use sudo every time I tweaked this or some other user service.
