mirror of
https://github.com/jpochyla/psst.git
synced 2026-04-27 15:35:56 +03:00
[GH-ISSUE #10] Hangs after connection is lost #8
Labels
No labels
api
bug
build
documentation
duplicate
enhancement
good first issue
help wanted
idea
invalid
linux
lowprio
macos
pull-request
upstream
windows
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/psst#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thvdveld on GitHub (Jan 4, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/10
After connection is lost and reset, the player hangs (running with WiFi).
This is the output:
After this, nothing happens, unless selecting a new song.
@thvdveld commented on GitHub (Jan 4, 2021):
This now seems to happen after every song. I recall having the same issue when I was using spotify-tui and I think the problem was the client couldn't handle a connection reset (https://github.com/Rigellute/spotify-tui/issues/178 and https://github.com/librespot-org/librespot/issues/134).
@jpochyla commented on GitHub (Jan 4, 2021):
I think this is a bug unrelated to Spotify connection, caused by
d136d3bd. I'm on it!@jpochyla commented on GitHub (Jan 4, 2021):
Should be fixed in
da88499a. Leaving this issue open as network resiliency is on the roadmap.@thvdveld commented on GitHub (Jan 4, 2021):
It has been working now with no issues for 2 hours! 🎉 Nice work and thanks for the fast fixes!
@kirillrogovoy commented on GitHub (Aug 28, 2022):
I have this problem on macOS 12.3.1 and the latest Psst.
Only that in my case, it hangs until I restart the app. I can still browse the catalog, but the playback is dead.
@conartist6 commented on GitHub (Dec 31, 2022):
All issues related to this problem are "closed as completed" which seems misleading, and makes it more difficult to find https://github.com/librespot-org/librespot/discussions/609. Once a user does find it they need to read the entire thread to figure out if the problem still exists. It definitely seems to.