All my ducks seem to be in order and the correct configs in the right place. But i keep getting this message. As you can see the file exists. It is not empty, but systemctl cannot find it. Any help would be very very appreciated.

•fedora 40 xfce spin •kernel 6.9.9.200 •fucking chromebook

  • qaz@lemmy.world
    link
    fedilink
    arrow-up
    32
    arrow-down
    1
    ·
    edit-2
    4 months ago

    Why are you creating a system service for a user application? It will run Spotify as root unless you override the user. Did you know you can add your own services for your user at ~/.config/systemd/user/?

    Anyway, your method to add the service seems correct (create a file and reload the daemon), so I suspect it might refuse to load the file due to a syntax error in the service. Also perhaps compare the file permissions with the other files in the systemd folder.

      • Ghoelian@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        11
        arrow-down
        1
        ·
        4 months ago

        If you just want it to auto-start at login, you could create a symlink from the .desktop file to ~/.config/autostart.

        Something like ln ~/.local/applications/spotify.desktop ~/.config/autostart (or ln /usr/share/applications/spotify.desktop ~/.config/autostart if that’s where it installed to).

        I believe most DE’s will pick this up automatically.

        • Decq@lemmy.world
          link
          fedilink
          arrow-up
          13
          arrow-down
          1
          ·
          4 months ago

          Spotifyd is a Spotify daemon, not an user application. It makes perfect sense to run as a service. Though personally I would run it as a user service instead of a system service.

          • Ghoelian@lemmy.dbzer0.com
            link
            fedilink
            arrow-up
            5
            ·
            edit-2
            4 months ago

            Ahh I thought they were just making a service for the normal spotify application, yeah in that case it makes sense to use a service. Didn’t know spotifyd is something else

        • qaz@lemmy.world
          link
          fedilink
          arrow-up
          7
          arrow-down
          1
          ·
          edit-2
          4 months ago

          KDE also has an easy GUI to configure this. It’s called autostart in the settings app.

    • furikuri@programming.dev
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      Additionally if you’re looking for it to start on boot without logging in, you might find the loginctl enable-linger command to be of use. Maybe along with a Restart=on-failure policy in the service file if this is for a headless unit or something