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

Panic on an Err value: InitialFileHeadersCorrupt #121

Closed
joerg-krause opened this issue Oct 8, 2016 · 5 comments
Closed

Panic on an Err value: InitialFileHeadersCorrupt #121

joerg-krause opened this issue Oct 8, 2016 · 5 comments

Comments

@joerg-krause
Copy link
Contributor

Sometimes, librespot panics with:

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: InitialFileHeadersCorrupt', src/libcore/result.rs:799

This issue happens if a track is loaded in the Spotify Connect Client (so I can see the cover and the track artists and song title), but is not played locally (but was played before). Then I start librespot on my embedded Linux device, connect the client with librespot and after 3 or 4 seconds the panic happens.

Note, I am using Tremor as ogg decoder.

@joerg-krause
Copy link
Contributor Author

joerg-krause commented Oct 12, 2016

Not sure why OV_EINVAL is described as InitialFileHeadersCorrupt whereas vorbis-errors describes it as:

OV_EINVAL Invalid argument value.

@herrernst
Copy link
Contributor

Hm, I've just cross-compiled the current master for Raspberry Pi and always got InitialFileHeadersCorrupt, not yet found out the cause (not using Tremor btw)

@joerg-krause
Copy link
Contributor Author

Maybe this one helps: joerg-krause@b58dc0b

@plietar
Copy link
Owner

plietar commented Dec 31, 2016

I've cherry picked @joerg-krause's commit (thanks btw).
Since I can't reproduce this I'm not too sure how to fix the root cause.

@joerg-krause
Copy link
Contributor Author

Closed due to lack of maintenance of the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants