[GH-ISSUE #763] spt won't open after disk full #309

New issue

Closed

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

kerem commented

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

Owner

Originally created by @Giraffaman on GitHub (Mar 9, 2021).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/763

I'm using spotify-tui 0.23.0-1 (installed from AUR) with spotifyd on Manjaro 5.10.19-1. Today I managed to end up with 0B free on my /home partition which seemed to stop some applications from working (e.g. Signal which couldn't write logs anymore).
After freeing up about 20GB of space I restarted my machine any everything went back to normal, except now spt does not open anymore - I can still run spt play --url and also control spotifyd over the network, but spotify-tui does not get displayed anymore.

I tried to:

ensure internet connection was active
redirect sdterr to a log which yields nothing
re-create spotify-tui's client.yml by renaming the file, then running spt to configure again
uninstall spotify-tui, spotifyd and removing/renaming config files
reinstall the above and configure spotifyd.service, re-create spotify API key and configured spt again
deleted ~/.cache since I wasn't sure what to do anymore

Is there any way I can make spotify-tui write something like debug logs, or is there any other location where I should look for potentially corrupted files?

Originally created by @Giraffaman on GitHub (Mar 9, 2021). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/763 I'm using spotify-tui 0.23.0-1 (installed from AUR) with spotifyd on Manjaro 5.10.19-1. Today I managed to end up with 0B free on my /home partition which seemed to stop some applications from working (e.g. Signal which couldn't write logs anymore). After freeing up about 20GB of space I restarted my machine any everything went back to normal, except now spt does not open anymore - I can still run spt play --url <url> and also control spotifyd over the network, but spotify-tui does not get displayed anymore. I tried to: * ensure internet connection was active * redirect sdterr to a log which yields nothing * re-create spotify-tui's client.yml by renaming the file, then running spt to configure again * uninstall spotify-tui, spotifyd and removing/renaming config files * reinstall the above and configure spotifyd.service, re-create spotify API key and configured spt again * deleted ~/.cache since I wasn't sure what to do anymore Is there any way I can make spotify-tui write something like debug logs, or is there any other location where I should look for potentially corrupted files?

kerem closed this issue

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

kerem commented

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

Author

Owner

@Giraffaman commented on GitHub (Mar 9, 2021):

I found that I can still open and use spotify tui as another user and also as root - in both cases I get the config menu at first run and am redirected to the spotify-tui authentication url (the step where it opens a browser to locahost:8888).

However, that step never happens when I try to run spt with my normal user - not even after completely re-installing.

For the moment my workaround is to open spt as root using sudo, but I still do not understand what is keeping spt from displaying its UI.

@Giraffaman commented on GitHub (Mar 9, 2021): I found that I can still open and use spotify tui as another user and also as root - in both cases I get the config menu at first run and am redirected to the spotify-tui authentication url (the step where it opens a browser to locahost:8888). However, that step never happens when I try to run spt with my normal user - not even after completely re-installing. For the moment my workaround is to open spt as root using sudo, but I still do not understand what is keeping spt from displaying its UI.

kerem commented

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

Author

Owner

@Giraffaman commented on GitHub (Mar 10, 2021):

it turns out I still had a (now invalid) spotify_token_cache.json in ~/.config/spotify-tui/ - I moved that file out of the folder, launched spt again and this time was directed to open a browser for authentication at localhost:8888. I am now once again able to use spotify-tui as before.

@Giraffaman commented on GitHub (Mar 10, 2021): it turns out I still had a (now invalid) spotify_token_cache.json in ~/.config/spotify-tui/ - I moved that file out of the folder, launched spt again and this time was directed to open a browser for authentication at localhost:8888. I am now once again able to use spotify-tui as before.

kerem referenced this issue

2026-02-28 14:53:13 +03:00

[PR #309] [MERGED] docs: add jtagcat as a contributor #747