Linux

48008 readers

1194 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Cannot start spotifyd.service (i.imgur.com)

submitted 4 months ago by HotsauceHurricane@lemmy.one to c/linux@lemmy.ml

35 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] qaz@lemmy.world 31 points 4 months ago* (last edited 4 months ago) (2 children)

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.

[–] HotsauceHurricane@lemmy.one 6 points 4 months ago (1 children)

Ill give it a look tomorrow when i sart my nonsense up again.

[–] Ghoelian@lemmy.dbzer0.com 10 points 4 months ago (2 children)

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 12 points 4 months ago (1 children)

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 5 points 4 months ago* (last edited 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 6 points 4 months ago* (last edited 4 months ago)

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

[–] furikuri@programming.dev 3 points 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