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

Have to restart spotifyd after playing a song #178

Open
pviotti opened this issue Dec 1, 2019 · 3 comments
Open

Have to restart spotifyd after playing a song #178

pviotti opened this issue Dec 1, 2019 · 3 comments

Comments

@pviotti
Copy link

pviotti commented Dec 1, 2019

Sometimes, after playing a song, it shows the Spotify API reported an error message. So I have to restart spotifyd (systemctl --user restart spotifyd.service), after which it starts working again.
This happens only sometimes, but often enough to be inconvenient. This is the error log I get from spotifyd:

15:45:11 [DEBUG] (1) librespot_core::session: Invalidating session[0]
15:45:11 [DEBUG] (1) librespot_core::session: drop Dispatch
15:45:11 [TRACE] (1) mio::poll: [/home/myuser/.cargo/registry/src/github.com-1ecc6299db9ec823/mio-0.6.19/src/poll.rs:907] deregistering handle with poller
15:45:11 [DEBUG] (1) tokio_reactor: dropping I/O source: 5
15:45:11 [ERROR] Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer" }

I can't figure out what condition triggers it, but it looks like it's related to this spotifyd issue Spotifyd/spotifyd#156 , which in turns may be related to librespot.

I know spotify-tui is not to blame, but I'm posting this issue so that other users experiencing the same can find some information. (Maybe on spotity-tui's side, a more informative error message can be shown..?)

OS: Arch Linux
spotify-tui: 0.10.0 (AUR package from git, updated today)
spotifyd: 0.2.20

@Rigellute
Copy link
Owner

Thanks for the info @pviotti

@stevensonmt
Copy link

Think it's actually this issue with librespot: librespot-org/librespot#134

@sputnick1124
Copy link
Contributor

sputnick1124 commented Dec 13, 2019

Unfortunately the errors we get back from rspotify are lacking somewhat. Getting anything more than the HTTP error code seems to be problematic. I definitely agree that better error handling/reporting is a goal worth devoting attention to, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants