-
Notifications
You must be signed in to change notification settings - Fork 40
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
Trouble running assistant.py #64
Comments
I'm on the same boat as you. As far as I understand, it's because the google-assistant-library for Python has been deprecated and replaced with the google-assistant-service, which has removed the hotword functionality which this module relies on, but I could be wrong. If I'm not wrong, however, I hear it's a convoluted process involving downgrading Raspbian's glibc to a version that works with the deprecated google-assistant-library, which should make the library work once more but could break at any minute since the library has been deprecated anyways, meaning this is just a hacky temporary solution. I have no idea how to downgrade glibc, though, so I think this is a dead end for now. Either this module finds a workaround to the hotword problem or google updates their SDK to include hotword functionality again (Hands-free activation in here: https://developers.google.com/assistant/sdk/overview.html#features ). |
My assistant.py works, it shows pubnub subscription completed and hello from python!! but google assistant wont work. |
My understanding is the 1.0.1 library is not compatible with Buster, and causes segmentation fault. This worked for me:
My understanding is the 1.0.1 library is not compatible with Buster. This worked for me. |
After i run the code in the environment it have this bugs and I couldnt find way to solve it
What means by segmentation fault and how to solve it???
The text was updated successfully, but these errors were encountered: