Skip to content

Spicetify breaks on multi user systems sharing the same spotify installation (/opt/spotify/Apps) #3356

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
zjeffer opened this issue Mar 23, 2025 · 10 comments
Closed
2 tasks done
Labels
🐛 bug Something isn't working

Comments

@zjeffer
Copy link

zjeffer commented Mar 23, 2025

🔍 Have you checked Spicetify.app page for your issue?

  • I have checked the FAQ

🔍 Is there already an issue for your problem?

  • I have checked older issues, open and closed

ℹ Environment / Computer Info

- Spotify version: `1.2.59.514`
- Spicetify version: `2.39.5`
- Arch Linux
- Hyprland
- Spotify and spicetify-cli were both installed through the AUR.

📝 Description

I have 2 users: one for work and one personal user. My work user is also in my personal user's group, so it has access to all group-accessible files.
I have followed the wiki's instructions to set the correct permissons in /opt/spotify/Apps, but these seem to get overwritten to 700 by spicetify at some point? This causes spicetify commands to not work for user 1 if I ran them before on user 2. Spotify also launches with a blank screen for the other user, I assume because it doesn't have access to the Apps folder.

How do other people manage this kind of setup? I'd like to be able to share the same config between both users without having to run any spicetify commands every time I login to the other user.


After running spicetify backup apply with user 1:

Image

@zjeffer zjeffer added the 🐛 bug Something isn't working label Mar 23, 2025
@rxri
Copy link
Member

rxri commented Mar 23, 2025

Please install spotify per-user then, and not system-wide. This is not something we should manage in our code.

@rxri rxri closed this as not planned Won't fix, can't repro, duplicate, stale Mar 23, 2025
@zjeffer
Copy link
Author

zjeffer commented Mar 23, 2025

Can't spicetify manage it by not changing the permissions of /opt/spotify/Apps? Why does it do that?

@rxri
Copy link
Member

rxri commented Mar 23, 2025

you can chmod/change perms manually to 770 or something. this is kinda something that shouldn't be by default bc it can create another sort of issues. One spicetify installation for multiple users is not supported.

@zjeffer
Copy link
Author

zjeffer commented Mar 23, 2025

That indeed works. I don't see why spicetify currently sets it 700 when applying, though? Why not 750, so that it can at least be read by other users of the same group?

I'd rather not manage Spotify on a per-user basis, I like doing everything through my system package manager.

@rxri
Copy link
Member

rxri commented Mar 23, 2025

That indeed works. I don't see why spicetify currently sets it 700 when applying, though? Why not 750, so that it can at least be read by other users of the same group?

To be honest, I don't know. khanhas must have made it this way for some reason or another.
https://github.com/spicetify/cli/blob/main/src/utils/utils.go#L90

@rxri
Copy link
Member

rxri commented Mar 23, 2025

we could change it to 750 ig?

@zjeffer
Copy link
Author

zjeffer commented Mar 23, 2025

Do you mind if I make a PR where I change all these to 750?

@rxri
Copy link
Member

rxri commented Mar 23, 2025

feel free

@zjeffer
Copy link
Author

zjeffer commented Mar 23, 2025

Actually to make backup work too, it should be 770 (because it has to be writable). I'll look into this

@rxri
Copy link
Member

rxri commented Mar 23, 2025

Actually to make backup work too, it should be 770 (because it has to be writable). I'll look into this

ummm, yeah well, you would need to check for folder name then i guess because we set 700 to everything

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants