[GH-ISSUE #246] Librespot crashing when Spotify app searches network and recognizes device #166

New issue

Closed

opened 2026-02-27 19:29:11 +03:00 by kerem · 0 comments

kerem commented

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

Owner

Originally created by @codethief on GitHub (Sep 7, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/246

Hi there! First of all, thanks a lot for the work you're putting into this project!

I just installed librespot for the first time and noticed that whenever I have librespot running and then open up Spotify on my phone, librespot crashes with the following error message:

INFO:librespot: librespot 9d9c311 (2018-03-11). Built on 2018-03-13. Build ID: BECir1hc
INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-gzs1.ap.spotify.com:4070"
INFO:librespot_core::session: Authenticated as "*****************" !
INFO:librespot_playback::audio_backend::alsa: Using alsa sink
INFO:librespot_core::session: Country: "**"
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: WireError(InvalidEnumValue(14))', /checkout/src/libcore/result.rs:916:5
stack backtrace:
   0:   0x8bf63f - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h280c621ec0336843
                       at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
   1:   0x8c989b - std::sys_common::backtrace::print::h5bb167d48668dac9
                       at /checkout/src/libstd/sys_common/backtrace.rs:68
                       at /checkout/src/libstd/sys_common/backtrace.rs:57
   2:   0x8b7ec7 - std::panicking::default_hook::{{closure}}::hccf3b2e1cc48596f
                       at /checkout/src/libstd/panicking.rs:381
   3:   0x8b79a3 - std::panicking::default_hook::h338b1189515ccc69
                       at /checkout/src/libstd/panicking.rs:397
   4:   0x8b8373 - std::panicking::rust_panic_with_hook::h5d950fb4a856fba5
                       at /checkout/src/libstd/panicking.rs:577
   5:   0x8b8217 - std::panicking::begin_panic::h7a5157aecf168062
                       at /checkout/src/libstd/panicking.rs:538
   6:   0x8b8143 - std::panicking::begin_panic_fmt::hc44606ee40e9a98e
                       at /checkout/src/libstd/panicking.rs:522
   7:   0x8b80eb - rust_begin_unwind
                       at /checkout/src/libstd/panicking.rs:498
   8:   0x9211a3 - core::panicking::panic_fmt::h68e7715928be641f
                       at /checkout/src/libcore/panicking.rs:71
   9:   0x537ccb - core::result::unwrap_failed::hc8e405a7d6f5e105
  10:   0x51078b - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &'a mut F>::call_once::h550fb1c59c949344
  11:   0x52f50f - <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll::h6f4042a85363f6fe
  12:   0x51a1c3 - <librespot_connect::spirc::SpircTask as futures::future::Future>::poll::h2ae68a0a355e9093
  13:   0x4a2fdf - <librespot::Main as futures::future::Future>::poll::ha34952329266c131
  14:   0x49b61f - futures::task_impl::std::set::haa73a9ee0a468b94
  15:   0x4b3f8b - tokio_core::reactor::Core::run::h8b40cb76d6ebd0af
  16:   0x4a4aa3 - librespot::main::hf84f741837bd497f
  17:   0x4b4a13 - std::rt::lang_start::{{closure}}::h369662dc239e3883
  18:   0x8b801b - std::panicking::try::do_call::h9cb586bd57bb9d3d
                       at /checkout/src/libstd/rt.rs:59
                       at /checkout/src/libstd/panicking.rs:480
  19:   0x8dec33 - __rust_maybe_catch_panic
                       at /checkout/src/libpanic_unwind/lib.rs:101
  20:   0x8bf2cb - std::rt::lang_start_internal::h104139376fdb9ead
                       at /checkout/src/libstd/panicking.rs:459
                       at /checkout/src/libstd/panic.rs:365
                       at /checkout/src/libstd/rt.rs:58
  21:   0x4a5583 - main
  22: 0x76d3c81b - __libc_start_main

I suppose it's because Spotify is searching the network and recognizing the device?

Anyway, I did read about issue #181 . There, however, the error message was slightly different (WireError(InvalidEnumValue(13)) instead of 14) and I believe the fix is already included in my build(?) (As I'm running PiMusicBox, I'm using this build which, according to the above error message, was built on March 11.)

Edit: I must have overlooked #223 when I was searching for existing bug reports. Looks like this was already fixed. Sorry about that!

Originally created by @codethief on GitHub (Sep 7, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/246 Hi there! First of all, thanks a lot for the work you're putting into this project! I just installed librespot for the first time and noticed that whenever I have librespot running and then open up Spotify on my phone, librespot crashes with the following error message: ``` INFO:librespot: librespot 9d9c311 (2018-03-11). Built on 2018-03-13. Build ID: BECir1hc INFO:librespot_core::session: Connecting to AP "gew1-accesspoint-b-gzs1.ap.spotify.com:4070" INFO:librespot_core::session: Authenticated as "*****************" ! INFO:librespot_playback::audio_backend::alsa: Using alsa sink INFO:librespot_core::session: Country: "**" thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: WireError(InvalidEnumValue(14))', /checkout/src/libcore/result.rs:916:5 stack backtrace: 0: 0x8bf63f - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h280c621ec0336843 at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49 1: 0x8c989b - std::sys_common::backtrace::print::h5bb167d48668dac9 at /checkout/src/libstd/sys_common/backtrace.rs:68 at /checkout/src/libstd/sys_common/backtrace.rs:57 2: 0x8b7ec7 - std::panicking::default_hook::{{closure}}::hccf3b2e1cc48596f at /checkout/src/libstd/panicking.rs:381 3: 0x8b79a3 - std::panicking::default_hook::h338b1189515ccc69 at /checkout/src/libstd/panicking.rs:397 4: 0x8b8373 - std::panicking::rust_panic_with_hook::h5d950fb4a856fba5 at /checkout/src/libstd/panicking.rs:577 5: 0x8b8217 - std::panicking::begin_panic::h7a5157aecf168062 at /checkout/src/libstd/panicking.rs:538 6: 0x8b8143 - std::panicking::begin_panic_fmt::hc44606ee40e9a98e at /checkout/src/libstd/panicking.rs:522 7: 0x8b80eb - rust_begin_unwind at /checkout/src/libstd/panicking.rs:498 8: 0x9211a3 - core::panicking::panic_fmt::h68e7715928be641f at /checkout/src/libcore/panicking.rs:71 9: 0x537ccb - core::result::unwrap_failed::hc8e405a7d6f5e105 10: 0x51078b - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &'a mut F>::call_once::h550fb1c59c949344 11: 0x52f50f - <futures::stream::map::Map<S, F> as futures::stream::Stream>::poll::h6f4042a85363f6fe 12: 0x51a1c3 - <librespot_connect::spirc::SpircTask as futures::future::Future>::poll::h2ae68a0a355e9093 13: 0x4a2fdf - <librespot::Main as futures::future::Future>::poll::ha34952329266c131 14: 0x49b61f - futures::task_impl::std::set::haa73a9ee0a468b94 15: 0x4b3f8b - tokio_core::reactor::Core::run::h8b40cb76d6ebd0af 16: 0x4a4aa3 - librespot::main::hf84f741837bd497f 17: 0x4b4a13 - std::rt::lang_start::{{closure}}::h369662dc239e3883 18: 0x8b801b - std::panicking::try::do_call::h9cb586bd57bb9d3d at /checkout/src/libstd/rt.rs:59 at /checkout/src/libstd/panicking.rs:480 19: 0x8dec33 - __rust_maybe_catch_panic at /checkout/src/libpanic_unwind/lib.rs:101 20: 0x8bf2cb - std::rt::lang_start_internal::h104139376fdb9ead at /checkout/src/libstd/panicking.rs:459 at /checkout/src/libstd/panic.rs:365 at /checkout/src/libstd/rt.rs:58 21: 0x4a5583 - main 22: 0x76d3c81b - __libc_start_main ``` I suppose it's because Spotify is searching the network and recognizing the device? Anyway, I *did* read about issue #181 . There, however, the error message was slightly different (`WireError(InvalidEnumValue(13))` instead of `14`) and I believe the fix is already included in my build(?) (As I'm running PiMusicBox, I'm using [this build](https://github.com/pimusicbox/pimusicbox/issues/480#issuecomment-392972884) which, according to the above error message, was built on March 11.) **Edit:** I must have overlooked #223 when I was searching for existing bug reports. Looks like this was already fixed. Sorry about that!

kerem closed this issue

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

kerem referenced this issue

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

[PR #166] [MERGED] API review #823

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#166

No description provided.

Rows
Columns