Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

thread 'main' panicked at 'called Result::unwrap() #786

Closed
shakakibara12 opened this issue Jan 20, 2021 · 11 comments
Closed

thread 'main' panicked at 'called Result::unwrap() #786

shakakibara12 opened this issue Jan 20, 2021 · 11 comments
Labels
wontfix Issues that will not be fixed under any circumstances

Comments

@shakakibara12
Copy link

shakakibara12 commented Jan 20, 2021

hello please help me, i am getting this error message

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { inner: ErrorInner { kind: NumberInvalid, line: Some(2), col: 11, at: Some(49), message: "", key: [] } }', src/config.rs:477:67 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

this is my current config

 [global]
 username = username
 password = password
 backend = pulseaudio
 device_name = Manjaro
 bitrate = 160
 cache_path = home/user/.cache/spotifyd
 no_audio_cache = true
 initial_volume = 90
 volume_normalisation = true
 normalisation_pregain = -10
 device_type = computer
@viktor-grunwaldt
Copy link

I have the exact same error, running Manjaro with 5.10 linux.

@coccovax
Copy link

Same error running on archlinuxarm on Raspberry PI3 B+

@robinvd
Copy link
Contributor

robinvd commented Jan 21, 2021

please see the pinned issue #765. Im working on a better error message that is not as confusing as this at #789. Please see if this error message would be helpful

@coccovax
Copy link

thanks @robinvd
I updated configuration file with new syntax, but now I have another error message:

value: Os { code: 20, kind: Other, message: "Not a directory" }', /build/.cargo/registry/src/github.aaakk.us.kg-1285ae84e5963aae/librespot-core-0.1.1/src/cache.rs:31:49

that I think it's about cache, but cache_path value is set as a string and is valid path.

@robinvd
Copy link
Contributor

robinvd commented Jan 21, 2021

glad it helped!

as for the new error, there was a similar issue, see #772 (comment), but that was with an invalid path, you could try just commeting it out.

Ill add that panic to my todo list for better error messages haha

@JojiiOfficial
Copy link
Member

A valid path to a directory or file? Is it relative or absolute? Does it work with cache commented out?

jackson15j added a commit to jackson15j/dot_files that referenced this issue Jan 26, 2021
Was hitting issue: Spotifyd/spotifyd#786 (real issue:
Spotifyd/spotifyd#765), but updating to the latest
configuration file
changes (https://spotifyd.github.io/spotifyd/config/File.html) fixed my
`spotifyd` service from running.
@robinvd
Copy link
Contributor

robinvd commented Mar 3, 2021

@spoergsmaal which of the 2 issues are you having?

@JojiiOfficial
Copy link
Member

@spoergsmaal
Could you send the config files line 49 (or even better 45-55)?

@stale
Copy link

stale bot commented Jun 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Issues that will not be fixed under any circumstances label Jun 2, 2021
@stale stale bot closed this as completed Jun 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix Issues that will not be fixed under any circumstances
Projects
None yet
Development

No branches or pull requests

6 participants
@coccovax @JojiiOfficial @robinvd @viktor-grunwaldt @shakakibara12 and others