Hi,
When 18.02 came out, I updated my dev environment (arch linux). That went well. I had to re-register my environment with home.mycroft.ai again, but whatever. It was talking to me, I could load skills, etc. In the last couple weeks I’ve been working on my own skill, and somewhere along there (possibly in the last few days), it stopped speaking or making any noise. I am always in the debug view (start-mycroft.sh debug), so I can see it responding, but I don’t hear anything. I don’t see anything pop up in pavucontrol either (no audio stream), so it’s not getting to my sound card. Given the error messages I see at the beginning, it looks like it can’t find the card:
ALSA lib pcm_dsnoop.c:638:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2501:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
connect(2) call to /dev/shm/jack-1000/default/jack_0 failed (err=No such file or directory)
attempt to connect to server failed
20:23:12.717 - mycroft.client.speech.listener:create_wake_word_recognizer:239 - INFO - creating wake word engine
20:23:12.718 - mycroft.client.speech.hotword_factory:create_hotword:268 - INFO - creating hey mycroft
20:23:12.753 - mycroft.client.speech.listener:create_wakeup_recognizer:257 - INFO - creating stand up word engine
20:23:12.754 - mycroft.client.speech.hotword_factory:create_hotword:268 - INFO - creating wake up
FWIW, I don’t think the mic is working either, but I don’t care about that right now. I’m just typing commands to it.
What’s weird is that this worked not long ago (last couple weeks). I have updated the system since then (it’s arch), and I always do a git pull before I start working on my skill in the evening, but switching my mycroft-core repo from the dev branch to the master one (which I think is more stable) doesn’t change anything.
When I started debugging it tonight, I went to mycroft-core/mimic and did a ./mimic -t “hello world” and got alsa errors, similar to the above. In particular, this one:
ALSA lib pcm_dmix.c:1099:(snd_pcm_dmix_open) unable to open slave
I had to install pulseaudio-alsa, and then the mimic command would work. It’s odd that I didn’t need to do this/have this package installed a week ago (or whenever). It’s like mycroft was using pulse properly before, and now is falling back to alsa and failing. I also used dev_setup.sh to recheckout and rebuild mimic. It worked fine after the recompile as well.
start-mycroft.sh audiotest records nothing, but it does successfully play it back. When I put another wave file that is actual sound in the expected file’s location, and I hack up the python file so it doesn’t record over it, it plays the file as expected, no issues
This makes me think mycroft should work fine, but no go.
Other things that use pulse and/or alsa work fine, FWIW. It’s not just my skill that has no sound… it’s any skill or fallback. In fact, I removed my skill completely and it still had issues, so it’s not like my skill is somehow messing up the sound card access.
I haven’t destroyed my dev environment and built it completely new, but I think that may be my next step, unless anyone has any ideas…?
Thanks!
