mirror of
https://github.com/Rigellute/spotify-tui.git
synced 2026-04-26 16:15:55 +03:00
[GH-ISSUE #102] Application just closes when I am not using the PC #59
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#59
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 @Bios-Marcel on GitHub (Oct 23, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/102
I usually leave the client open all day. As soon as i take my lunch break, I leave my PC and leave
sptopen. However, I do stop playback on my Spotify Connect device, which is my phone, which is the only active Spotify Connect device. When I come back,spthas exited without printing an error or anything.@Rigellute commented on GitHub (Oct 23, 2019):
This sounds like an app crash. There's currently an issue with
tui-rsthat prevents the error message being printed (https://github.com/fdehau/tui-rs/issues/177).Need to investigate this crash - will see if I can reproduce.
@Bios-Marcel commented on GitHub (Oct 23, 2019):
Is there a logfile or anything?
@jfaltis commented on GitHub (Oct 29, 2019):
@Bios-Marcel I added the output of a backtrace recently when running spotify-tui in Debug mode (https://github.com/Rigellute/spotify-tui/pull/111). Could you follow these instructions (https://github.com/Rigellute/spotify-tui#development) and reproduce this crash?
@Bios-Marcel commented on GitHub (Oct 29, 2019):
Will do tmr if I find time
@Bios-Marcel commented on GitHub (Oct 30, 2019):
I am assuming this is related to sleep or standby? Couldn't such errors just be ignored and display something like "Connected severed. .. trying to reconnect."?
@Bios-Marcel commented on GitHub (Nov 1, 2019):
Similar to the last one I'd say. Maybe it should just be okay if a call fails and there's no need to just kill the app.
@Rigellute commented on GitHub (Nov 1, 2019):
Ah yes, I've seen this last error error before. The panic is from
rspotify. Looks like we might need to listen for network connectivity and not attempt to make the network request when offline.@NyanKiyoshi commented on GitHub (Aug 14, 2020):
rspotifyor something else is visibly trying to open the web-browser but crashes when unable to (in this case, it's in a container, so no such thing is provided to it).Strace shows this: