-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
CatAI crashes when quitting a browser or when starting CatAI when a browser is already open. #29
Comments
You can disable the open in browser feature vis environment variable, check the config. |
Disarmed and this issue vanished. Also CatAI really doesn't like TTY
launch, make the program ignore the x server so it can launch in TTY mode
(If I press CRTL+F1 to enter TTY)
…On Tue, Jul 11, 2023 at 1:11 AM Ido S. ***@***.***> wrote:
You can disable the open in browser feature vis environment variable,
check the config.
I will try to see if there is a workaround to prevent CatAI from crashing
after failing to open the browser.
—
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOSUENKCNNX7MG7IFXYBLJTXPTVABANCNFSM6AAAAAA2FPFBN4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Supposed to work on the latest version, is the problem fixed?
|
Updated. Now it's completely broken.
catai@1.0.2 start
node src/index.js --production true --ui catai
Segmentation fault (core dumped)
I updated to Linux Mint 21.2
|
Trying to run catai update works, but yields same result. fatal runtime error: Rust cannot catch foreign exceptions |
Reinstalling does this |
I did upgrade the node-llama version (this is the binding to the model) |
That isn’t helpful. The problem is now CatAI keeps having a segmentation fault and dumping its core. See previous messages for help with debugging.On Jul 19, 2023, at 3:53 AM, Ido S. ***@***.***> wrote:
I did upgrade the node-llama version (this is the binding to the model)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
CatAI now uses a custom lib - develop by the CatAI team. |
The install failed, mainly as you didn't specify sudo. Even after that small blunder and having to upgrade NodeJS from 18 to 20 using insane command line nonsense, it bloody works now. |
Please refer to the troubleshooting before opening an issue. You might find the solution there.
Describe the bug
CatAI really doesn't like having the browser be open when you start it. If you attempt to start CatAI with the browser open, it prints this out to the terminal
..................../home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/node_modules/openurl/openurl.js:39
throw error;
^
Error: Gtk-Message: 00:49:11.085: Failed to load module "xapp-gtk3-module"
[2:2:0711/004911.245184:ERROR:nacl_fork_delegate_linux.cc(313)] Bad NaCl helper startup ack (0 bytes)
Gtk-Message: 00:49:11.272: Failed to load module "xapp-gtk3-module"
Node.js v18.16.0
at file:///home/thesystemguy/.nvm/versions/node/v20.2.0/lib/node_modules/catai/scripts/cli.js:69:27
exit code: 1
A reinstallation nor reboot does not fix this issue. This issue cropped up after Google Chrome broke and Firefox assumed itself as the default browser and I changed the settings.
Screenshots
n/a
Desktop (please complete the following information):
OS: Linux Mint 21.1 Cinnamon, Linux 5.15.0-76-generic
Browser: Google Chrome
CatAI version 0.3.12
Node.js version v18.16.0
CPU: AMD Ryzen 5 5600H with Radeon Graphics
RAM: 30.7 GiB (512 MiB reserved to graphics chipset)
The text was updated successfully, but these errors were encountered: