[GH-ISSUE #898] spt suddenly doesn't start up #385

New issue

Open

opened 2026-02-28 14:48:50 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:48:50 +03:00

Owner

Originally created by @tommyalatalo on GitHub (Oct 1, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/898

Today spt completely stopped starting up for some unknown reason.
I can run spt --version and it will output 0.25.0. But running just spt does nothing, there is no output, no error or any other information, the terminal just contiues on the next line as if the spt command was just a no-op command.

Is there any way to print some kind of debug information? The --help information doesn't specify any debugging flags like --verbose or similar. All I can see now is that the command exits with error code 101.

I'm on Arch Linux 5.14.8-arch1-1, and I had spt working just yesterday, don't really know what happened to it now.

Originally created by @tommyalatalo on GitHub (Oct 1, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/898 Today spt completely stopped starting up for some unknown reason. I can run `spt --version` and it will output `0.25.0`. But running just `spt` does nothing, there is no output, no error or any other information, the terminal just contiues on the next line as if the `spt` command was just a no-op command. Is there any way to print some kind of debug information? The `--help` information doesn't specify any debugging flags like `--verbose` or similar. All I can see now is that the command exits with error code `101`. I'm on Arch Linux 5.14.8-arch1-1, and I had spt working just yesterday, don't really know what happened to it now.

kerem commented

2026-02-28 14:48:51 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 4, 2021):

Hmm... strange. Unfortunately we don't have any helpful debugging setup. I'm looking to address this by using tracing to write logs to a file.

Perhaps the token cache is corrupted. Try removing the file ~/.config/spotify-tui/.spotify_token_cache.json

Or if you prefer

rm ~/.config/spotify-tui/.spotify_token_cache.json

And then start up again.

If that doesn't help, you could also try complete re-init by removing the config directory ~/.config/spotify-tui/ and starting up again. You'll need your client id/secret again.

Do you have any spotify-tui config? Edit the theme or keybinds?

@Rigellute commented on GitHub (Oct 4, 2021): Hmm... strange. Unfortunately we don't have any helpful debugging setup. I'm looking to address this by using `tracing` to write logs to a file. Perhaps the token cache is corrupted. Try removing the file `~/.config/spotify-tui/.spotify_token_cache.json` Or if you prefer ``` rm ~/.config/spotify-tui/.spotify_token_cache.json ``` And then start up again. If that doesn't help, you could also try complete re-init by removing the config directory `~/.config/spotify-tui/` and starting up again. You'll need your client id/secret again. Do you have any spotify-tui config? Edit the theme or keybinds?

kerem commented

2026-02-28 14:48:51 +03:00

Author

Owner

@azinsharaf commented on GitHub (Feb 23, 2022):

removing the config file fixed it for me.

@azinsharaf commented on GitHub (Feb 23, 2022): removing the config file fixed it for me.