[GH-ISSUE #378] Exit code 101 #159

Closed
opened 2026-02-28 14:47:26 +03:00 by kerem · 7 comments
Owner

Originally created by @tom-doerr on GitHub (Apr 4, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/378

When I execute spt it fails to start, although it used to work with version 0.16.0 I tested different versions but the error remains the same.

➜  ~ .cargo/bin/spt -V
spotify-tui 0.17.1
➜  ~ .cargo/bin/spt   
➜  ~ echo $?          
101
➜  ~ 
➜  ~ spt -V
spotify-tui 0.16.0
➜  ~ spt
➜  ~ echo $?
101

Creating a new Client ID didn't help either.
Any ideas?

Originally created by @tom-doerr on GitHub (Apr 4, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/378 When I execute `spt` it fails to start, although it used to work with version `0.16.0` I tested different versions but the error remains the same. ``` ➜ ~ .cargo/bin/spt -V spotify-tui 0.17.1 ➜ ~ .cargo/bin/spt ➜ ~ echo $? 101 ➜ ~ ➜ ~ spt -V spotify-tui 0.16.0 ➜ ~ spt ➜ ~ echo $? 101 ``` Creating a new Client ID didn't help either. Any ideas?
kerem closed this issue 2026-02-28 14:47:26 +03:00
Author
Owner

@Rigellute commented on GitHub (Apr 6, 2020):

Hmm... not sure.

Which OS are you using?

<!-- gh-comment-id:609707035 --> @Rigellute commented on GitHub (Apr 6, 2020): Hmm... not sure. Which OS are you using?
Author
Owner

@tom-doerr commented on GitHub (Apr 6, 2020):

Linux Mint - it's based on Ubuntu 18.04.
I just remembered that it stopped working right after my computer ran out of storage, is it possible that spt tried to write to some file which resulted in that file becoming corrupted?

<!-- gh-comment-id:609901168 --> @tom-doerr commented on GitHub (Apr 6, 2020): Linux Mint - it's based on Ubuntu 18.04. I just remembered that it stopped working right after my computer ran out of storage, is it possible that spt tried to write to some file which resulted in that file becoming corrupted?
Author
Owner

@Rigellute commented on GitHub (Apr 9, 2020):

That is possible yes! On every launch, authentication is performed and might attempt to persist the auth token to the file system. It's possible that this was the cause of your exit code.

<!-- gh-comment-id:611427838 --> @Rigellute commented on GitHub (Apr 9, 2020): That is possible yes! On every launch, authentication is performed and might attempt to persist the auth token to the file system. It's possible that this was the cause of your exit code.
Author
Owner

@tom-doerr commented on GitHub (Apr 20, 2020):

Do you know where auth token is stored? I couldn't find anything on my file system.

<!-- gh-comment-id:616757334 --> @tom-doerr commented on GitHub (Apr 20, 2020): Do you know where auth token is stored? I couldn't find anything on my file system.
Author
Owner

@Rigellute commented on GitHub (Apr 21, 2020):

The auth tokens are persisted here ${HOME}/.config/spotify-tui/client.yml

<!-- gh-comment-id:617160607 --> @Rigellute commented on GitHub (Apr 21, 2020): The auth tokens are persisted here `${HOME}/.config/spotify-tui/client.yml`
Author
Owner

@tom-doerr commented on GitHub (May 2, 2020):

There were other files in that directory that seemed to be related to caching. After I deleted those and started spotify-tui, I was prompted to log into Spotify.

<!-- gh-comment-id:622992446 --> @tom-doerr commented on GitHub (May 2, 2020): There were other files in that directory that seemed to be related to caching. After I deleted those and started spotify-tui, I was prompted to log into Spotify.
Author
Owner

@Rigellute commented on GitHub (May 4, 2020):

Thanks @tom-doerr

<!-- gh-comment-id:623366878 --> @Rigellute commented on GitHub (May 4, 2020): Thanks @tom-doerr
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#159
No description provided.