mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #204] Crashes when connecting from the Spotify client #139
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#139
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 @alesny on GitHub (Apr 21, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/204
librespot version:
03de235(2018-04-12)Each connect from the official Spotify client ends with the following crash:
Apr 21 11:01:03 music librespot[606]: INFO:librespot_playback::audio_backend::alsa: Using alsa sink
Apr 21 11:01:06 music librespot[606]: thread 'main' panicked at 'called
Result::unwrap()on anErrvalue: SpotifyIdError', libcore/result.rs:945:5Apr 21 11:01:06 music librespot[606]: stack backtrace:
Apr 21 11:01:06 music librespot[606]: 0: 0x99105b -
Apr 21 11:01:06 music librespot[606]: 1: 0x98adb7 -
Apr 21 11:01:06 music librespot[606]: 2: 0x98facb -
Apr 21 11:01:06 music librespot[606]: 3: 0x98f6af -
Apr 21 11:01:06 music librespot[606]: 4: 0x98ff6f -
Apr 21 11:01:06 music librespot[606]: 5: 0x98fdd3 -
Apr 21 11:01:06 music librespot[606]: 6: 0x98fd57 -
Apr 21 11:01:06 music librespot[606]: 7: 0x98fcef -
Apr 21 11:01:06 music librespot[606]: 8: 0x9ddb7f -
Apr 21 11:01:06 music librespot[606]: 9: 0x50dcaf -
Apr 21 11:01:06 music librespot[606]: 10: 0x4f2333 -
Apr 21 11:01:06 music librespot[606]: 11: 0x4f0d23 -
Apr 21 11:01:06 music librespot[606]: 12: 0x4d447b -
Apr 21 11:01:06 music librespot[606]: 13: 0x4cdbf7 -
Apr 21 11:01:06 music librespot[606]: 14: 0x4c4c0b -
Apr 21 11:01:06 music librespot[606]: 15: 0x4cdf63 -
Apr 21 11:01:06 music librespot[606]: 16: 0x4b8bc3 -
Apr 21 11:01:06 music librespot[606]: 17: 0x4bb2e7 -
Apr 21 11:01:06 music librespot[606]: 18: 0x4b8603 -
Apr 21 11:01:06 music librespot[606]: 19: 0x4b886f -
Apr 21 11:01:06 music librespot[606]: 20: 0x4b663f -
Apr 21 11:01:06 music librespot[606]: 21: 0x4b2143 -
Apr 21 11:01:06 music librespot[606]: 22: 0x4d622b -
Apr 21 11:01:06 music librespot[606]: 23: 0x4c37fb -
Apr 21 11:01:06 music librespot[606]: 24: 0x98fc27 -
Apr 21 11:01:06 music librespot[606]: 25: 0x99f39b -
Apr 21 11:01:06 music librespot[606]: 26: 0x990397 -
Apr 21 11:01:06 music librespot[606]: 27: 0x4d6e13 - main
Apr 21 11:01:06 music librespot[606]: 28: 0xb6d08677 - __libc_start_main
Apr 21 11:01:06 music systemd[1]: raspotify.service: Main process exited, code=exited, status=101/n/a
Apr 21 11:01:06 music systemd[1]: raspotify.service: Unit entered failed state.
Apr 21 11:01:06 music systemd[1]: raspotify.service: Failed with result 'exit-code'.
Apr 21 11:01:16 music systemd[1]: raspotify.service: Service hold-off time over, scheduling restart.
Apr 21 11:01:16 music systemd[1]: Stopped Raspotify.
Apr 21 11:01:16 music systemd[1]: Starting Raspotify...
Apr 21 11:01:16 music systemd[1]: Started Raspotify.
Apr 21 11:01:17 music librespot[623]: INFO:librespot: librespot (raspotify)
03de235(2018-04-12). Built on 2018-04-20. Build ID: j42hUaKh@sashahilton00 commented on GitHub (Apr 23, 2018):
Unfortunately there isn't much we can do about this as the raspotify binary is stripped, thus we can't see what's causing the error. @dtcooper is there any chance you could avoid stripping raspotify binaries, or is it an operational requirement?
@l3d00m commented on GitHub (May 5, 2018):
You may not have seen it @sashahilton00, but he disabled it in his recent build:
github.com/dtcooper/raspotify@0fa44d0526So this shouldn't be an issue here anymore in the future
@sashahilton00 commented on GitHub (May 5, 2018):
Thanks for letting me know
On 5 May 2018 at 16:15:44, l3d00m (notifications@github.com) wrote:
@ash-vd commented on GitHub (May 5, 2018):
I got the same error, did a fresh pull from git with a fresh build.
INFO:librespot_core::session: Country: "NL" thread '<unnamed>' panicked at 'calledResult::unwrap()on anErrvalue: Os { code: 2, kind: NotFound, message: "No such file or directory" }', libcore/result.rs:945:5 stack backtrace: 0: 0x562e3d6a4553 - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h09c1ee131a74b1c4 at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 1: 0x562e3d69e644 - std::sys_common::backtrace::_print::h47a337b62b6d5e9e at libstd/sys_common/backtrace.rs:71 2: 0x562e3d6a303d - std::panicking::default_hook::{{closure}}::h945a649c9017832e at libstd/sys_common/backtrace.rs:59 at libstd/panicking.rs:380 3: 0x562e3d6a2d42 - std::panicking::default_hook::hcc534c2d30fbcda3 at libstd/panicking.rs:396 4: 0x562e3d6a34b0 - std::panicking::rust_panic_with_hook::h09a7a3a353dc2f38 at libstd/panicking.rs:576 5: 0x562e3d6a336e - std::panicking::begin_panic::h8327f16bde15df70 at libstd/panicking.rs:537 6: 0x562e3d6a3269 - std::panicking::begin_panic_fmt::h42ff1d37404632d6 at libstd/panicking.rs:521 7: 0x562e3d6a31f2 - rust_begin_unwind at libstd/panicking.rs:497 8: 0x562e3d6ed360 - core::panicking::panic_fmt::h0bd854df201d1baf at libcore/panicking.rs:71 9: 0x562e3d27c9f8 - core::result::unwrap_failed::h5a09cf05b18a98d3 10: 0x562e3d29f095 - <librespot_playback::audio_backend::pipe::StdoutSink as librespot_playback::audio_backend::Open>::open::h9bfda9875bf4b9fa 11: 0x562e3d29014e - librespot_playback::audio_backend::mk_sink::h824474c1db1d88e0 12: 0x562e3d2024a3 - std::sys_common::backtrace::__rust_begin_short_backtrace::heb3aa9b6b596e9b9 13: 0x562e3d1f6d08 - std::panicking::try::do_call::he087878015e93967 14: 0x562e3d6b203e - __rust_maybe_catch_panic at libpanic_unwind/lib.rs:102 15: 0x562e3d1f972d - <F as alloc::boxed::FnBox<A>>::call_box::h7fbc5ef2078e0c1b 16: 0x562e3d6a9efb - std::sys::unix::thread::Thread::new::thread_start::h711c51a13a158afa at /checkout/src/liballoc/boxed.rs:798 at libstd/sys_common/thread.rs:24 at libstd/sys/unix/thread.rs:90 17: 0x7f87536127fb - start_thread 18: 0x7f875333fb5e - clone 19: 0x0 - <unknown>@User65k commented on GitHub (Jun 4, 2018):
Hi, I also get an error when I connect a spotify client to a fresh build (using
cargo build --release --features "alsa-backend")librespot -n test --backend pipelibrespot -n test --backend alsaALSA and Pipe backend each end up with:
@l3d00m commented on GitHub (Jun 4, 2018):
The fix was added on 18-5-2018, your build is from 15-5-2018 (see log)
@User65k commented on GitHub (Jun 4, 2018):
nice to know and good to hear.
fix confirmed 😍
awesome project! 👍
@ComlOnline commented on GitHub (Jun 4, 2018):
Closing this issue as its fixed. Thanks