mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #950] How to handle spotifyd restarting #415
Labels
No labels
bug
enhancement
good first issue
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-tui#415
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 @stevensonmt on GitHub (Feb 16, 2022).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/950
I have an issue when listening for longer periods that the spotifyd connection gets reset but because it happens silently systemd does not see it as a failure and does not restart the service. This leads to spotify-tui returning an error that no backend is running (I forget the actual text of the error). I'm trying to solve this by simply having spotifyd restart periodically via
WatchdogSec=1200s. When the service restarts spotify-tui does not seem to reconnect automatically. Playback fails silently as the current track just pauses and keeps trying to play the next 3 seconds over and over until I manually select a track.Is there a better way to handle the silent failure of spotifyd or a way to handle the spotifyd service restarting such that playback is either not interrupted or if interrupted restarts the current track automatically?