-
-
Notifications
You must be signed in to change notification settings - Fork 304
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
'mock' error #987
Comments
Exact same issue while installing the assistant using /home/pi/GassistPi/scripts/gassist-installer.sh it stucks at mock error as described above. |
Same here - manually installed python 3.7 to fulfill criteria and set as default, but no change.
#update: not happening with latest raspbian version instead of "stretch", but running into other dep-issues though |
yeah, I have tried that with no luck... I was able to install gassistapi like a year ago but no luck so far now |
Bump up the python version to 3.6 Follow the instructions here. |
Still getting the same error after following above link |
@divijbajaj5 Please post the error. And mention what steps you followed and in what order. Bumping the python version will solve the issue. Open a terminal and type |
Enter the modelid that was generated in the actions console: bivoiceai-mysmartspeaker-rvsr51 Hit:1 http://archive.raspberrypi.org/debian stretch InRelease ===========================Checking OS Compatability========================= ===========You are running the installer on Stretch========== ===========Your board supports Ok-Google Hotword. You can also trigger the assistant using custom-wakeword========== ===========GPIO pins can be used with the assistant========== ==========Changing particulars in service files========== ==========Changing particulars in service files for Ok-Google hotword========== |
python3 --version |
it worked for me, I did reboot after following procedure in the link provided. I have latest strech image fully updated and clean |
I have succesfully installed it. Thank You! |
Will leave this issue open for others. |
@adas4190 Can you please trace the exact steps you followed to solve the error after a clean build of the raspbian stretch? |
@shivasiddharth env lib shows 2 folders python 3.5 and python 3.6. So do I have to remove older version of python? @adas4190 I followed all the steps mentioned in the link. Please tell what exactly to be done? |
I did nothing more than in the link. Don't worry about other python versions, once you add alias it will use 3.6 version. Just follow the procedure and try to install Gassistpi again and you should be ok |
I did clean install, update system and follow procedure to update python (in the link provided ). Voila 😊 |
Enter the modelid that was generated in the actions console: bivoiceai-mysmartspeaker-rvsr51 Hit:1 http://archive.raspberrypi.org/debian stretch InRelease ===========================Checking OS Compatability========================= ===========You are running the installer on Stretch========== ===========Your board supports Ok-Google Hotword. You can also trigger the assistant using custom-wakeword========== ===========GPIO pins can be used with the assistant========== ==========Changing particulars in service files========== ==========Changing particulars in service files for Ok-Google hotword========== @shivasiddharth and @adas4190 Couldn't find any luck. Despite doing same steps. Please see what to do |
Hold on dont break your head. I am just in the processing of releasing the assistant for buster. |
IMPORTANT NOTICE
If you do not complete the template below it is likely that your issue will not be addressed. When providing information about your issue please be as extensive as possible so that it can be solved by as little as possible responses.
FAILURE TO COMPLETE THE REQUESTED INFORMATION WILL RESULT IN YOUR ISSUE BEING CLOSED
Board and OS details:
Open a terminal and run
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 38.40
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4
Hardware : BCM2835
Revision : a020d3
Serial : 00000000b2702ac6
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
Describe the bug:
Did you go through or search the issues section to check if your issue was already discussed (either currently open issues or closed issues).
Yes
2. Is the issue related to assistant installation ?
Yes
If answer to question 2 is Yes, then paste the contents of the terminal below.
If answer to question 2 is No, then proceed further.
3. Does the assistant service start normally?
Yes/No
4. Is the assistant service restarting automatically?
Yes/No
If answer to question 4 is Yes, then paste the contents of the terminal below.
If answer to question 4 is No, then proceed further.
Manually start the assistant. For guidelines to start the assistant manually refer this
Paste the command below, that crashed the assistant
Paste the contents of the terminal below
Attach the log file named Gassistpi.log
Log file can be found in /tmp/ directory
no log found
The text was updated successfully, but these errors were encountered: