openassistant / oa-core

Open Assistant Core
http://openassistant.org
GNU General Public License v3.0
293 stars 77 forks source link

Does not work on Linux #42

Closed thanos-the-tank-engine closed 3 years ago

thanos-the-tank-engine commented 3 years ago

Describe the bug The software starts up and then does nothing but throw an error To Reproduce Start the software

a-theriault commented 3 years ago

It would help if there were more details (what flavor of Linux? What hardware? What's the specific error?), but...

There are a few complaints OA will make if it doesn't recognize hardware: the first is a flood of errors that spits out the minute you start the program and runs on infinite loop. You'll notice they make mention of "ear" -- that's your clue that the software isn't detecting your input hardware. Are you able to record anything on the system? Is there any specific error that "ear" is generating?

If you aren't seeing any errors on boot, that's a good sign! Next try saying the "Boot Mind" command. If you don't get an error, but also don't hear any output, first verify you can play sound in another context.

It is also a possibility that you can play sound in general, but not with Python. Something else to double-check.

Lastly, you may be using a device that has an "audio" and "video" group You may need to use usermod to add yourself to the appropriate group(s) (if you can) Again, verify you can record and play sound in general with the system you're testing on, and with the version of python you're using.

I encountered some issues running via SSH that were due to the user groups above. Try running directly on-device first as a verification step.

Lastly I've left some tips on dealing with ALSA and Raspberry Pi OS issues specifically here. If that fits your use case, check it out.

Since this was first reported in January, I should also point out this closed ticket which is now patched. It might be worth giving it another shot.

Hope this helps!

thanos-the-tank-engine commented 3 years ago

I'm sorry, this issue was due to a server outage and actually not Linux specific. I just forgot to close it