First issues on new image #106
Replies: 5 comments 7 replies
-
Thanks for this! I converted this one to a discussion thread, so we can discuss the different aspect further and from that create one liner bug reports/issue that we can attach to the "fix for release" list. Will go through the different aspect into detail later today. |
Beta Was this translation helpful? Give feedback.
-
Next test: Rpi4 8G First boot is awesome. Boots quick, voice setup starts, Volume is LOUD!! It didn't seem to be like that on the Rpi3 image.
I finish the setup, Ask to choose TTS...NO VOICE
The rest seems to work just fine, reboot went smooth, loaded the homescreen well, but NO SOUND and NO MIC. |
Beta Was this translation helpful? Give feedback.
-
Yeah, indeed setting the volume to 50% on first boot is a known re-introduced bug. I will vcreate a ticket for it. Sound issues: Hope to get to that this evening as it is the biggest showstopper bug at the moment. Thanks for testing! Trying to get another test image in your hands soon. |
Beta Was this translation helpful? Give feedback.
-
Does this image use HolmesV and not ovos-core? |
Beta Was this translation helpful? Give feedback.
-
Tracking down some TTS issues. It seems that the phrases are generated and put into the /tmp/TTS directory, but not read after that. The directory ~/.local/share/Mycroft//en-us/ is totally empty |
Beta Was this translation helpful? Give feedback.
-
This is the new image, Rpi3b.
Everything booted, the WiFi setup worked well...after I found a Pi that the WiFi worked.
It even talked to me telling me that I need to set it up!! That was a first on any of these that I have tried.
Setup went well, I setup WiFi on my phone, selected "Local Backend", and "Mimic2" as tts, because that is what the setup voice was and that is the first that I have heard a voice at all.
After the reboot, things looked good, but no voice, and no mic. I have not looked into anything that I am stating here, just what happened as I started things.
I decided I would mess with the audio later, as that has been an issue with everything...always seems to be with anything linux.
So I dug into
~/.config/mycroft/mycroft.conf
.I changed my location, because although the geolocate works with the IP, it is still 60 miles away from me.
I performed
sudo systemctl restart mycroft
When everything started back, It showed that I needed to choose a backend again. I went through this once before, but don't remember what I was testing. I am assuming that this is something to do with skill-ovos-setup?
When I look at
~/.config/mycroft/mycroft.cong
again, all that was there was a list of blacklisted skills. Also, there is something wrong there. There is a whole bunch of duplicate entries there.Nothing with the "tts" or "server" or anything
This is where I'm at now, going to blacklist the setup skill, and redo my mycroft.conf file and go from there.
These are logs since first boot
logs.zip
Will post more later
Beta Was this translation helpful? Give feedback.
All reactions