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

Does not play any tracks in any playlist #864

Closed
nloyola opened this issue Jul 14, 2022 · 12 comments
Closed

Does not play any tracks in any playlist #864

nloyola opened this issue Jul 14, 2022 · 12 comments
Labels
bug Something isn't working

Comments

@nloyola
Copy link

nloyola commented Jul 14, 2022

Describe the bug
ncspot does not play any tracks in any playlist. When I select a playlist, it highlights each track and then goes to the next one without playing anything. This repeats until the last track in the playlist.

To Reproduce
Steps to reproduce the behavior:

  1. select a playlist

Expected behavior
I would like to hear the songs in the playlist.

System (please complete the following information):

  • OS: Linux, Debian 11
  • Terminal: Alacritty
  • Version: 0.9.8
  • Installed from: cargo

Backtrace/Debug log
None

Additional context
I've cleared the ncspot cache, but still does not play any tracks.

@nloyola nloyola added the bug Something isn't working label Jul 14, 2022
@ElotonSotilas
Copy link

Have you updated to the latest version? I don't see any problems. I use 0.10 on Arch and it works fantastically.

@nloyola
Copy link
Author

nloyola commented Jul 14, 2022

Still happens with ncspot version 0.10.0

It only started happening yesterday.

@hrkfdn
Copy link
Owner

hrkfdn commented Jul 14, 2022

Hmm, without a debug log it'll be very hard to diagnose this problem, but my guess is it's related to your sound setup.

@nloyola
Copy link
Author

nloyola commented Jul 14, 2022

I see this in the log:

[2022-07-14][22:30:44] [librespot_playback::player] [INFO] Loading <Hunted by a Freak> with Spotify URI <spotify:track:3LD4GOl1YpyrTDriiRLqhs>
[2022-07-14][22:30:44] [librespot_audio::fetch] [DEBUG] Downloading file dea57323a31450ef1a7ad4dc3960a922aaee5e18
[2022-07-14][22:30:44] [librespot_core::channel] [ERROR] channel error: 2 1
[2022-07-14][22:30:44] [librespot_playback::player] [ERROR] Unable to load encrypted file: ChannelError
[2022-07-14][22:30:44] [librespot_playback::player] [WARN] Skipping to next track, unable to load track <SpotifyId { id: 164574622760030272839095534886330221370, audio_type: Track }>: ()

If this is not enough, I can post the whole debug log.

Thanks

@nloyola
Copy link
Author

nloyola commented Jul 14, 2022

Is it related to this issue?

librespot-org/librespot#972

@hrkfdn
Copy link
Owner

hrkfdn commented Jul 14, 2022

Yeah, I think that may be it

@Bettehem
Copy link
Contributor

I started having this problem too. Adding 104.199.65.124 ap-gew4.spotify.com to /etc/hosts as instructed in the librespot issue solved the problem.

@nloyola
Copy link
Author

nloyola commented Jul 15, 2022

Thanks @Bettehem, the problem goes away with the change to /etc/hosts.

@uffer
Copy link

uffer commented Jul 17, 2022

changing the /etc/hosts file did the trick. It was not only a problem in Denmark but in The Netherlands as well.

@hrkfdn
Copy link
Owner

hrkfdn commented Jul 18, 2022

Cool, closing this one then. Maybe we should add it to the documentation at some point 🤔 it keeps coming up more and more often.

@eyenx
Copy link

eyenx commented Jul 22, 2022

Switzerland here. Same issue. Same solution. /etc/hosts entry did the trick

@hrkfdn
Copy link
Owner

hrkfdn commented Jul 27, 2022

Looks like the workaround will be incorporated in librespot soon: librespot-org/librespot#1026

hrkfdn added a commit that referenced this issue Jul 31, 2022
Contains:

> Blacklist ap-gew4 and ap-gue1 access points that cause channel errors

This should make the manual fix in /etc/hosts that some users had to apply obsolete.

Fixes #864
Fixes #867
Fixes #883

.. among others.
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

6 participants