[GH-ISSUE #413] Error in src/libcore/result.rs:1165:5 #266

Closed
opened 2026-02-27 19:29:43 +03:00 by kerem · 7 comments
Owner

Originally created by @murphy85 on GitHub (Dec 18, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/413

I have build a Docker image, but the startup after rebuild is failing for some days now. The image loads the master branch and compiles the files. I guess there are some breaking changes in latest commit?!

[2019-12-18T16:20:15Z INFO librespot] librespot UNKNOWN (UNKNOWN). Built on 2019-12-18. Build ID: VimBUOCD
thread 'main' panicked at 'called Result::unwrap() on an Err value: ParseIntError { kind: InvalidDigit }', src/libcore/result.rs:1165:5
stack backtrace:
0: 0x5465dd08 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd388416be068aba
1: 0x54677ccc - core::fmt::write::hb8a0f8de322e23aa
2: 0x5465ba68 - std::io::Write::write_fmt::hc86616c02fa2c37b
3: 0x54647dbc - std::panicking::default_hook::{{closure}}::h5352f19540010e0b
4: 0x54647a44 - std::panicking::default_hook::h4d4a552a2f757720
5: 0x546484b0 - std::panicking::rust_panic_with_hook::hc8912f099044b27b
6: 0x546480b0 - std::panicking::continue_panic_fmt::hfa73573fa425363c
7: 0x54647fa8 - rust_begin_unwind
8: 0x54673b70 - core::panicking::panic_fmt::hf7ca96f7c38266d6
9: 0x54676f4c - core::result::unwrap_failed::hfe4e93cbd3983e61
10: 0x54178428 - librespot::main::h9a2ebd2f561fa29e
11: 0x54179554 - std::rt::lang_start::{{closure}}::h25f588374e523cfb
12: 0x54647f2c - std::panicking::try::do_call::h17c83e4cc139bf43
13: 0x5465fdb0 - __rust_maybe_catch_panic
14: 0x5464e6f4 - std::rt::lang_start_internal::hbef9a63b8883f1c9
15: 0x54178cc8 - main

Originally created by @murphy85 on GitHub (Dec 18, 2019). Original GitHub issue: https://github.com/librespot-org/librespot/issues/413 I have build a [Docker image](https://github.com/murphy85/docker-librespot-alsa), but the startup after rebuild is failing for some days now. The image loads the master branch and compiles the files. I guess there are some breaking changes in latest commit?! [2019-12-18T16:20:15Z INFO librespot] librespot UNKNOWN (UNKNOWN). Built on 2019-12-18. Build ID: VimBUOCD thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }', src/libcore/result.rs:1165:5 stack backtrace: 0: 0x5465dd08 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbd388416be068aba 1: 0x54677ccc - core::fmt::write::hb8a0f8de322e23aa 2: 0x5465ba68 - std::io::Write::write_fmt::hc86616c02fa2c37b 3: 0x54647dbc - std::panicking::default_hook::{{closure}}::h5352f19540010e0b 4: 0x54647a44 - std::panicking::default_hook::h4d4a552a2f757720 5: 0x546484b0 - std::panicking::rust_panic_with_hook::hc8912f099044b27b 6: 0x546480b0 - std::panicking::continue_panic_fmt::hfa73573fa425363c 7: 0x54647fa8 - rust_begin_unwind 8: 0x54673b70 - core::panicking::panic_fmt::hf7ca96f7c38266d6 9: 0x54676f4c - core::result::unwrap_failed::hfe4e93cbd3983e61 10: 0x54178428 - librespot::main::h9a2ebd2f561fa29e 11: 0x54179554 - std::rt::lang_start::{{closure}}::h25f588374e523cfb 12: 0x54647f2c - std::panicking::try::do_call::h17c83e4cc139bf43 13: 0x5465fdb0 - __rust_maybe_catch_panic 14: 0x5464e6f4 - std::rt::lang_start_internal::hbef9a63b8883f1c9 15: 0x54178cc8 - main
kerem closed this issue 2026-02-27 19:29:44 +03:00
Author
Owner

@HEnquist commented on GitHub (Dec 23, 2019):

The master branch hasn't changed in the last ~2 months and the latest commits have mostly been minor things. All new stuff now goes to the "dev" branch first. When was your last successful build? Have you tried checking out an older version, or the "dev" branch? Does it work if you build without docker?

<!-- gh-comment-id:568565098 --> @HEnquist commented on GitHub (Dec 23, 2019): The master branch hasn't changed in the last ~2 months and the latest commits have mostly been minor things. All new stuff now goes to the "dev" branch first. When was your last successful build? Have you tried checking out an older version, or the "dev" branch? Does it work if you build without docker?
Author
Owner

@ashthespy commented on GitHub (Dec 30, 2019):

ParseIntError { kind: InvalidDigit }

Looks like you have passed in a non digit --initial-volume

<!-- gh-comment-id:569742136 --> @ashthespy commented on GitHub (Dec 30, 2019): >`ParseIntError { kind: InvalidDigit }` Looks like you have passed in a non digit `--initial-volume`
Author
Owner

@HEnquist commented on GitHub (Dec 30, 2019):

That's probably it. The example in the readme (https://github.com/murphy85/docker-librespot-alsa/blob/master/README.md) doesn't set the volume environment variable, so --initial-volume "$SPOTIFY_INITIAL_VOLUME" will just become --initial-volume "".

<!-- gh-comment-id:569755926 --> @HEnquist commented on GitHub (Dec 30, 2019): That's probably it. The example in the readme (https://github.com/murphy85/docker-librespot-alsa/blob/master/README.md) doesn't set the volume environment variable, so `--initial-volume "$SPOTIFY_INITIAL_VOLUME"` will just become `--initial-volume ""`.
Author
Owner

@ashthespy commented on GitHub (Dec 30, 2019):

According to the Dockerfile, SPOTIFY_INITIAL_VOLUME is set to 75.
@murphy85 FWIW, I managed to build your image and get it to run, but given I am on Windos couldn't test actual playback.

PS: You seem to be loading quite a few non required packages for the alsa backend(portaudio-dev, protobuf-dev)
PSS: You probably need to load alsa-lib before you build librespot, my first build failed because of this methinks.

<!-- gh-comment-id:569776223 --> @ashthespy commented on GitHub (Dec 30, 2019): According to the [Dockerfile](https://github.com/murphy85/docker-librespot-alsa/blob/b2c9bd79f4105049af47a59281dabd11d2ba0df4/Dockerfile#L20), `SPOTIFY_INITIAL_VOLUME` is set to 75. @murphy85 FWIW, I managed to build your image and get it to run, but given I am on Windos couldn't test actual playback. PS: You seem to be loading quite a few non required packages for the alsa backend(`portaudio-dev`, `protobuf-dev`) PSS: You probably need to load `alsa-lib` before you build `librespot`, my first build failed because of this methinks.
Author
Owner

@HEnquist commented on GitHub (Dec 30, 2019):

Oh you're right, it is set. I read too quickly and didn't see that, sorry.

<!-- gh-comment-id:569799292 --> @HEnquist commented on GitHub (Dec 30, 2019): Oh you're right, it is set. I read too quickly and didn't see that, sorry.
Author
Owner

@murphy85 commented on GitHub (Dec 31, 2019):

Thank you for your comments! I'm on vacation and will check for maybe missing library and the initial volume after 13th of January. But I'm pretty sure that the cargo build loads all necessary dependencies on build, like alsa-lib if the feature is set.

<!-- gh-comment-id:569930665 --> @murphy85 commented on GitHub (Dec 31, 2019): Thank you for your comments! I'm on vacation and will check for maybe missing library and the initial volume after 13th of January. But I'm pretty sure that the cargo build loads all necessary dependencies on build, like alsa-lib if the feature is set.
Author
Owner

@murphy85 commented on GitHub (Jan 13, 2020):

I'm sorry, it was my fault. I accidentally mixed up the order of commands in Dockerfile locally

<!-- gh-comment-id:573819025 --> @murphy85 commented on GitHub (Jan 13, 2020): I'm sorry, it was my fault. I accidentally mixed up the order of commands in Dockerfile locally
Sign in to join this conversation.
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#266
No description provided.