[GH-ISSUE #80] thread 'main' panicked at 'called Result::unwrap() on an Err value: Error #67

Closed
opened 2026-02-27 19:28:38 +03:00 by kerem · 5 comments
Owner

Originally created by @sashahilton00 on GitHub (Jan 29, 2018).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/80

Issue by krooarbo
Saturday Aug 26, 2017 at 08:38 GMT
Originally opened as https://github.com/plietar/librespot/issues/238


Hi,

First of all sorry for my english.
Yesterday libresport is working, but today not working. There isnt any changes on the system.

RUST_BACKTRACE=1 librespot --backend alsa -n raspotify --username $MYUSER --password $MYPASS
INFO:librespot: librespot ddfc28f (2017-08-04). Built on 2017-08-07. Build ID: N5RcEuis
thread 'main' panicked at 'called Result::unwrap() on an Err value: Error { repr: Os { code: 19, message: "No such device" } }', /checkout/src/libcore/result.rs:860
stack backtrace:
0:
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13: __libc_start_main

Please help!
Thanks in advance!

Br,

Originally created by @sashahilton00 on GitHub (Jan 29, 2018). Original GitHub issue: https://github.com/librespot-org/librespot/issues/80 <a href="https://github.com/krooarbo"><img src="https://avatars2.githubusercontent.com/u/31365711?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [krooarbo](https://github.com/krooarbo)** _Saturday Aug 26, 2017 at 08:38 GMT_ _Originally opened as https://github.com/plietar/librespot/issues/238_ ---- Hi, First of all sorry for my english. Yesterday libresport is working, but today not working. There isnt any changes on the system. RUST_BACKTRACE=1 librespot --backend alsa -n raspotify --username $MYUSER --password $MYPASS INFO:librespot: librespot ddfc28f (2017-08-04). Built on 2017-08-07. Build ID: N5RcEuis thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 19, message: "No such device" } }', /checkout/src/libcore/result.rs:860 stack backtrace: 0: <unknown> 1: <unknown> 2: <unknown> 3: <unknown> 4: <unknown> 5: <unknown> 6: <unknown> 7: <unknown> 8: <unknown> 9: <unknown> 10: <unknown> 11: <unknown> 12: <unknown> 13: __libc_start_main Please help! Thanks in advance! Br,
kerem 2026-02-27 19:28:38 +03:00
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by krooarbo
Saturday Aug 26, 2017 at 08:39 GMT


0-12 is <unknown>

<!-- gh-comment-id:361276073 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/krooarbo"><img src="https://avatars2.githubusercontent.com/u/31365711?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [krooarbo](https://github.com/krooarbo)** _Saturday Aug 26, 2017 at 08:39 GMT_ ---- 0-12 is \<unknown\>
Author
Owner

@sashahilton00 commented on GitHub (Jan 29, 2018):

Comment by chimpy
Tuesday Sep 12, 2017 at 22:18 GMT


I have the same error.

<!-- gh-comment-id:361276096 --> @sashahilton00 commented on GitHub (Jan 29, 2018): <a href="https://github.com/chimpy"><img src="https://avatars3.githubusercontent.com/u/380577?v=4" align="left" width="48" height="48" hspace="10"></img></a> **Comment by [chimpy](https://github.com/chimpy)** _Tuesday Sep 12, 2017 at 22:18 GMT_ ---- I have the same error.
Author
Owner

@ComlOnline commented on GitHub (Jan 29, 2018):

@krooarbo @chimpy Do you still have this with the latest raspotify released today?

<!-- gh-comment-id:361334357 --> @ComlOnline commented on GitHub (Jan 29, 2018): @krooarbo @chimpy Do you still have this with the latest raspotify released today?
Author
Owner

@chimpy commented on GitHub (Jan 29, 2018):

Hey, I’m not sure what was causing this but I have been happily using Raspotify for a while now :) It must have been an error in my config.

On 29 Jan 2018, at 19:10, Colm notifications@github.com wrote:

@krooarbo @chimpy Do you still have this with the latest raspotify released today?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

<!-- gh-comment-id:361360065 --> @chimpy commented on GitHub (Jan 29, 2018): Hey, I’m not sure what was causing this but I have been happily using Raspotify for a while now :) It must have been an error in my config. > On 29 Jan 2018, at 19:10, Colm <notifications@github.com> wrote: > > @krooarbo @chimpy Do you still have this with the latest raspotify released today? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. >
Author
Owner

@ComlOnline commented on GitHub (Jan 29, 2018):

In that case Ill close it and just reopen it if @krooarbo is still having issues.

<!-- gh-comment-id:361366880 --> @ComlOnline commented on GitHub (Jan 29, 2018): In that case Ill close it and just reopen it if @krooarbo is still having issues.
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#67
No description provided.