-
Notifications
You must be signed in to change notification settings - Fork 446
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
Exception in Controller::worker() #61
Comments
Are you sure that client and server are both on 0.7? |
You are completely right, the updated didnt work. Thanks a lot. |
@deisi @badaix have the same issue, fresh installation raspberry Arch linux and x64 Manjaro(Arch distribution) both have 0.10.0-2 version builded from aur
and
clients on android(two smartphones works ok) server runned on x64 works with clients on androids and client on x64 machine gives the same issue. Any ideas what i've faced? |
uff, I currently have a broken rpi and cant test. In any case, I will change back to debian, because I hat too much trouble with Arch on ARM. So no, Idear sry. |
I get exactly the same problem with 2 freshly install Snapcast 0.11.1 installed from Arch AUR:
|
hey how you start the client? From systemd? If it works, you might have the same problem as I just described in #229 If this is the problem It would be interesting to hear if you are using pulseaudio as well. |
Ok, further testing with two clients both running Arch (same dist on the server too):
So, it seems it is linked in some way to #229. |
I am having this issue with 0.11.1 without pulseaudio. Update: here is the command: |
I also encountered this problem with exactly the same log, use @christf 's fix and it works. |
Hello menghan and christf, I have the same problem, what is the code you use to get this working? |
@atze09 sorry for the late response. The fix command: |
Since last update ( I think I jumped from v 0.4.1 but im not 100% sure) to 0.7.0 my raspberry client cant connect any more. On the client I see:
In the systemd logs and on the server I get:
I also run a client instance on the same machine as the server. This client does work without error message.
For wat its worth, I use Arch Linux on both machines (client raspberry pi, server x86) and the packages are compiled from source.
The text was updated successfully, but these errors were encountered: