I am trying to start a systemd service for a specific user (service name/goal is not relevant). I do that because I need to have a per user process of an application running at startup.

Here is what I achieved so far:

But when I reboot the service does not seem to start and there is nothing to be seen in journalctl for said service. But the status said that the service is enabled:

~ $ systemctl --user status transmission-daemon

● custom.service - Custom Daemon
Loaded: loaded (/etc/systemd/user/custom.service; enabled; vendor preset: enabled)

Active: inactive (dead)

Also I can run it manually with no issue by running

~ $ systemctl --user start custom.service

As anyone any idea what I did wrong?

3 Answers 3


I dont know if this is your case but I could solve it with the answer of https://unix.stackexchange.com/questions/251211/why-doesnt-my-systemd-user-unit-start-at-boot

The problem was I had WantedBy=multi-user.target and had to change it to WantedBy=default.target and it worked.

Another thing, I have my service file in ~/.config/systemd/user

  • 1
    I had to do this, but also run systemctl --user enable <myservice>, see unix.stackexchange.com/questions/251211/… Commented Oct 27, 2018 at 19:32
  • Awesome, this made my systemd user unit starr at boot too! It was really annoying. Commented Oct 3, 2022 at 17:02
  • I have the same problem and I already have WantedBy=default.target
    – alercelik
    Commented Nov 10, 2023 at 7:07

The only thing necessary, from what I've seen, is to enable the service:

~ $ systemctl --user enable custom.service

and you said you've done that.

One way to check whether the start happened on reboot is to verify that there are no errors. You do that using the journalctl command:

~ $ journalctl --user -u custom.service

Note: the -u option stands for unit.

If nothing appears in there, you may have an invalid dependency, that is, the "wants" for user is default.target. In your .service file it should look like so:


Other targets are not likely to work and the auto-start will fail. That being said, the user has the targets listed by:

~ $ systemctl --user list-units --type=target

That does not include the multiuser, xsession, etc.

Finally, the X11 environment should be ready once the service starts, but I'm not 100% sure about that. In my .service file I also have an Environment= definition that goes like this:


I had problems where the service could not open an X-Window. With that small addition, it worked as expected.

One last thing, the User=... and Group=... parameters can't be used in a user service. Since it is specific to a user, you can't hope to use a specific user to run that application. Plus multiple users could be logged in the same computer and each need their own version of the service running in parallel. So other options may not be available to a user service. I would suggest you comment out most and then add one at a time to see what works and what doesn't in your situation. These errors, though, are the ones you'll see in the journal, so it should be relatively easy to fix once you bypass the few other steps.

Post Scriptum

The path where you want to save a User Service is:


unless you want the service accessible to all users on that computer in which case you use:


See this archlinux page for other details.

Note that I do not think that was your problem (wrong location) although it could have been. I have had difficulties before when I placed systemd files in the wrong place.

  • While you can put systemd files into /usr/lib/systemd, that is highly discouraged unless you are building your own distro. This directory is for the systemd units that ship with your distribution. Your own global changes should go into /etc/systemd instead, or into /usr/local/lib/systemd if you really want. There are more possible locations, a total of 16 where user systemd unit files can go, and 10 where system unit files can go. Each with its own purpose. freedesktop.org/software/systemd/man/systemd.unit.html for details. Commented Aug 11, 2021 at 5:26
  • 1
    When I create a Debian package, I put the <name>.service file in my project/debian/... folder and either get ./lib/systemd/system/<name>.service (global) or ./usr/lib/systemd/user/<name>.service (user specific). So I use the Debian scheme, which may not 100% follow the systemd manual. But I think that works great for my packages. Commented Aug 11, 2021 at 16:56

As you mentioned transmission-daemon, your other procedure seems good. I bet your service file has some problems. Because I created service files easily except for transmission-daemon.

Configs of each service file are somehow case by case. Of course If there is a service generator like podman generate systemd then, use it.

This is my transmission service file. If you have a mount file for it, then add it to After. e.g After=network-online.target mountfilename.mount

Description=Transmission BitTorrent Daemon

ExecStart=/usr/local/bin/transmission-daemon --config-dir /path/to/config/transmission-daemon -f --log-error
ExecReload=/bin/kill -s HUP $MAINPID


This is for $ systemctl enable transmission-daemon, not --user option.

WantedBy=multi-user.target is because of my setting. I recommend WantedBy=default.target too.

For systemctl --user enable,

Description=Transmission BitTorrent Daemon

ExecStart=/usr/local/bin/transmission-daemon --config-dir /path/to/config/transmission-daemon -f --log-error
ExecReload=/bin/kill -s HUP $MAINPID


But in this case, you can't put the service file /etc/systemd/user. Put it into ~/.config/systemd/user/. and enable it.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .