starred/librespot

Fork 0

mirror of https://github.com/librespot-org/librespot.git synced 2026-04-27 08:15:50 +03:00

[GH-ISSUE #241] ERROR does not kill process #163

New issue

Closed

opened 2026-02-27 19:29:10 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 19:29:10 +03:00

Owner

Originally created by @Northo on GitHub (Jul 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/241

I get
ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer"
but the process does not exit, so systemd does not restart it.

In the spotify client librespot will sometimes show up, sometimes not. If I select the speaker after the ERROR (if it shows in the client), the speaker eventually disappears from the client, and I have to manually restart the process on the server.

This might be a duplicate of #226, but this is not a panic, therefore I leave that decision up to someone who knos more than me.

Raspberry Pi 2 model B, running Arch Linux

Originally created by @Northo on GitHub (Jul 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/241 I get `ERROR:librespot_core::session: Os { code: 104, kind: ConnectionReset, message: "Connection reset by peer"` but the process does not exit, so systemd does not restart it. In the spotify client librespot will sometimes show up, sometimes not. If I select the speaker after the ERROR (if it shows in the client), the speaker eventually disappears from the client, and I have to manually restart the process on the server. This might be a duplicate of #226, but this is not a panic, therefore I leave that decision up to someone who knos more than me. Raspberry Pi 2 model B, running Arch Linux

kerem closed this issue

2026-02-27 19:29:11 +03:00

kerem commented

2026-02-27 19:29:11 +03:00

Author

Owner

@michalfita commented on GitHub (Aug 15, 2018):

Yes, this is still a problem.

@michalfita commented on GitHub (Aug 15, 2018): Yes, this is still a problem.

kerem commented

2026-02-27 19:29:11 +03:00

Author

Owner

@michalfita commented on GitHub (Oct 23, 2018):

@wfraser You seem to be very fluent in all this multiprocess/multithreading task - could you try to solve this issue? Reproduction requires disconnection of broadband during playing - should be easy to reproduce on virtual machine.

@michalfita commented on GitHub (Oct 23, 2018): @wfraser You seem to be very fluent in all this multiprocess/multithreading task - could you try to solve this issue? Reproduction requires disconnection of broadband during playing - should be easy to reproduce on virtual machine.

kerem commented

2026-02-27 19:29:11 +03:00

Author

Owner

@sashahilton00 commented on GitHub (Nov 3, 2018):

This is a well known bug, currently being tracked at https://github.com/librespot-org/librespot/issues/134. The problem is that it requires a significant rewrite of parts of librespot, and hence hasn't been fixed. Anyone is welcome to give it a go, in the meantime, closing this in favour of aforementioned issue.

@sashahilton00 commented on GitHub (Nov 3, 2018): This is a well known bug, currently being tracked at https://github.com/librespot-org/librespot/issues/134. The problem is that it requires a significant rewrite of parts of librespot, and hence hasn't been fixed. Anyone is welcome to give it a go, in the meantime, closing this in favour of aforementioned issue.

kerem referenced this issue

2026-02-27 20:00:05 +03:00

[PR #163] [CLOSED] Rustfmt syntax correction #820

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/librespot#163

No description provided.

Rows
Columns