starred/spotify-tui

Fork 0

mirror of https://github.com/Rigellute/spotify-tui.git synced 2026-04-27 00:25:53 +03:00

[GH-ISSUE #66] thread '<unnamed>' panicked at 'called `Result::unwrap()` #43

New issue

Closed

opened 2026-02-28 14:46:34 +03:00 by kerem · 13 comments

kerem commented

2026-02-28 14:46:34 +03:00

Owner

Originally created by @tamert on GitHub (Oct 15, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/66

thread '' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:999:5
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace.

Originally created by @tamert on GitHub (Oct 15, 2019). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/66 thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:999:5 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

kerem closed this issue

2026-02-28 14:46:34 +03:00

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@haitech commented on GitHub (Oct 15, 2019):

Getting similar error.
Seems like the http-server is not running?

On osx 10.14.4, installed with brew

 ~  spt
Opened https://accounts.spotify.com/authorize?scope=playlist-read-private%20user-library-modify%20user-library-read%20user-modify-playback-state%20user-read-currently-playing%20user-read-playback-state%20user-read-private%20user-read-recently-played&client_id=XYZ&response_type=code&state=XYZ&redirect_uri=http:%2F%2Flocalhost:8888%2Fcallback& in your browser
Enter the URL you were redirected to:
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:999:5
stack backtrace:
   0: std::panicking::default_hook::{{closure}}
   1: std::panicking::default_hook
   2: std::panicking::rust_panic_with_hook
   3: std::panicking::continue_panic_fmt
   4: rust_begin_unwind
   5: core::panicking::panic_fmt
   6: core::result::unwrap_failed
   7: spt::redirect_uri::redirect_uri_web_server
   8: __rust_maybe_catch_panic
   9: core::ops::function::FnOnce::call_once{{vtable.shim}}
  10: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
  11: std::sys::unix::thread::Thread::new::thread_start
  12: _pthread_body
  13: _pthread_start

Spotify auth failed

@haitech commented on GitHub (Oct 15, 2019): Getting similar error. Seems like the http-server is not running? On osx 10.14.4, installed with brew ``` ~ spt Opened https://accounts.spotify.com/authorize?scope=playlist-read-private%20user-library-modify%20user-library-read%20user-modify-playback-state%20user-read-currently-playing%20user-read-playback-state%20user-read-private%20user-read-recently-played&client_id=XYZ&response_type=code&state=XYZ&redirect_uri=http:%2F%2Flocalhost:8888%2Fcallback& in your browser Enter the URL you were redirected to: thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/libcore/result.rs:999:5 stack backtrace: 0: std::panicking::default_hook::{{closure}} 1: std::panicking::default_hook 2: std::panicking::rust_panic_with_hook 3: std::panicking::continue_panic_fmt 4: rust_begin_unwind 5: core::panicking::panic_fmt 6: core::result::unwrap_failed 7: spt::redirect_uri::redirect_uri_web_server 8: __rust_maybe_catch_panic 9: core::ops::function::FnOnce::call_once{{vtable.shim}} 10: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once 11: std::sys::unix::thread::Thread::new::thread_start 12: _pthread_body 13: _pthread_start Spotify auth failed ```

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@haitech commented on GitHub (Oct 15, 2019):

Got it to work with running sudo spt. And then after spt (without sudo) worked.

@haitech commented on GitHub (Oct 15, 2019): Got it to work with running `sudo spt`. And then after `spt` (without sudo) worked.

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@tamert commented on GitHub (Oct 15, 2019):

i am waiting for a very long time but not response

@tamert commented on GitHub (Oct 15, 2019): i am waiting for a very long time but not response

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@tamert commented on GitHub (Oct 15, 2019):

@tamert commented on GitHub (Oct 15, 2019): ![Screen Shot 2019-10-15 at 12 35 22](https://user-images.githubusercontent.com/1997933/66820022-964fb280-ef48-11e9-8baa-1796b00ad522.png)

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@tigrato commented on GitHub (Oct 15, 2019):

@tamert copy the url and paste into the terminal

@tigrato commented on GitHub (Oct 15, 2019): @tamert copy the url and paste into the terminal

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):

Sorry about this. Something must be going wrong with the local webserver on first set up.

Will investigate.

@Rigellute commented on GitHub (Oct 15, 2019): Sorry about this. Something must be going wrong with the local webserver on first set up. Will investigate.

kerem commented

2026-02-28 14:46:35 +03:00

Author

Owner

@tamert commented on GitHub (Oct 15, 2019):

@tamert copy the url and paste into the terminal

:) yes i see now .. i was couldnt see because i just focus error

@tamert commented on GitHub (Oct 15, 2019): > @tamert copy the url and paste into the terminal :) yes i see now .. i was couldnt see because i just focus error

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):

Did you install via brew and running on macOS?

Or are you on linux and installed via cargo?

@Rigellute commented on GitHub (Oct 15, 2019): Did you install via `brew` and running on macOS? Or are you on linux and installed via `cargo`?

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@abusch commented on GitHub (Oct 15, 2019):

Seeing this as well on Linux (Arch), spt installed via cargo. It opens up a web browser, then panics with the error above.

@abusch commented on GitHub (Oct 15, 2019): Seeing this as well on Linux (Arch), `spt` installed via `cargo`. It opens up a web browser, then panics with the error above.

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):

I know the issue, will create fix shortly.

@Rigellute commented on GitHub (Oct 15, 2019): I know the issue, will create fix shortly.

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):

Apologies once again, the fix is here github.com/Rigellute/spotify-tui@ca79472fa2 and is released to brew and cargo, you can now update.

@Rigellute commented on GitHub (Oct 15, 2019): Apologies once again, the fix is here https://github.com/Rigellute/spotify-tui/commit/ca79472fa253025152c76c0b53dce9437fc18fd2 and is released to brew and cargo, you can now update.

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):

Looks like this is only fixed for macOS, reopening.

@Rigellute commented on GitHub (Oct 15, 2019): Looks like this is only fixed for macOS, reopening.

kerem commented

2026-02-28 14:46:36 +03:00

Author

Owner

@Rigellute commented on GitHub (Oct 15, 2019):