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
[Problem]: shairport-sync crashes on play if launched as a services, but works fine otherwise #1827
Comments
Thanks for the post. This isn't exactly a crash -- Shairport Sync is exiting because it received an error 19 when trying to access the output device -- Error 19 means "No Such Device", so for some reason, the device is not accessible. You have not specified the output device in the configuration file, so it may be that Shairport Sync is trying to access whatever the default |
Thank you very much, it seems that
and the output of
Why would it work when launched manually but not when running as a service? And how would I go about setting the card in the configuration file? Thank you |
This issue has been inactive for 28 days so will be closed 7 days from now. To prevent this, please remove the "stale" label or post a comment. |
I still haven't solved this :/ |
Thanks. One of the suggestions was:
Did you happen to try that? Maybe specify |
Hey what do you know, that worked great! :D Thank you, sorry I didn't know how to fix the config file, it was smooth! |
What happened?
Just as the title says, shairport-sync works fine if launched manually from a terminal, but crashes as soon as something tries to connect when it's running as a service.
I have an external USB DAC connected to a raspberry 3, which works fine with raspotify.
The output below is before and after trying to play something; attached below is also verbose output from a sysctl run, which looks exactly the same as the one from a manual run (compared with diff).
Thank you
Relevant log output
System Information.
Configuration Information.
PulseAudio or PipeWire installed?
How did you install Shairport Sync?
Built from source
Check previous issues
The text was updated successfully, but these errors were encountered: