Skip to content
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

spicetify auto and spicetify apply commands wrongfully (re)start Spotify into login screen #3262

Closed
2 tasks done
MariusAlbrecht opened this issue Jan 3, 2025 · 2 comments
Closed
2 tasks done
Labels
πŸ› bug Something isn't working

Comments

@MariusAlbrecht
Copy link

MariusAlbrecht commented Jan 3, 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.50.335.g5e2860a8 (installed via flatpak)
- Spicetify version: 2.38.7
- OS: Ubuntu 24.10

πŸ“ Description

the spicetify auto and spicetify apply commands (re)start Spotify into the login screen even though I am logged in when manually starting Spotify. The spotify_path config is set to reflect flatpak's directory structure

To reproduce:

either

  1. close spotify
  2. do spicetify auto
  3. see error

or

  1. start spotify
  2. do spicetify apply
  3. see error

πŸ“Έ Screenshots

No response

@MariusAlbrecht MariusAlbrecht added the πŸ› bug Something isn't working label Jan 3, 2025
@rxri
Copy link
Member

rxri commented Jan 3, 2025

It cannot "restart" to login screen. This is because the prefs file or the spotify data is gone between the kill and start. Spicetify only launches Spotify binary.
src: https://github.com/spicetify/cli/blob/main/src/cmd/restart.go

@rxri rxri closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2025
@rxri
Copy link
Member

rxri commented Jan 3, 2025

It's probably flatpak related when you launch the binary directly instead of flatpak run .... Though I haven't seen this issue in the wild, and we did not change the behavior of restart for a long time...

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