You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
cat /proc/cpuinfo
cat /etc/os-release
Paste your Board and OS details here.
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/No
2. Is the issue related to assistant installation ?
Yes/No
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
Another issue got closed automaticly..
I just want to let you know something and don't know where to put.
You'll get a Segmentation fault error, if you don't use a UTF-8 encoded charset for your system.
In my case gassist always crashed after same answers. I used en_US.iso 8859-1 and after a answer from google which is containing a 😉 or 🔮 it crashed. I've only got a segmentation error.
I reinstalled raspian and whyever used UTF-8 as encodig and gassist worked and after seeing the emojis the problem was clear....
Hopefully it's useful for someone.
The text was updated successfully, but these errors were encountered:
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
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/No
2. Is the issue related to assistant installation ?
Yes/No
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
Another issue got closed automaticly..
I just want to let you know something and don't know where to put.
You'll get a Segmentation fault error, if you don't use a UTF-8 encoded charset for your system.
In my case gassist always crashed after same answers. I used en_US.iso 8859-1 and after a answer from google which is containing a 😉 or 🔮 it crashed. I've only got a segmentation error.
I reinstalled raspian and whyever used UTF-8 as encodig and gassist worked and after seeing the emojis the problem was clear....
Hopefully it's useful for someone.
The text was updated successfully, but these errors were encountered: