Open binbard opened 1 year ago
At the moment, Hetty relies on the default executable finding logic in the chromedp package (ref).
When using WSL, I suspect that when this code is executed, it's only looking for known executable paths for windows, and /usr/bin/google-chrome
is not checked/used.
As a workaround, a possible fix might be to create a symlink chrome
somewhere in a directory that's in your $PATH
, and point it to /usr/bin/google-chrome
.
In a future version of Hetty I might support explicitly setting the chrome executable path, but for now please look into the workaround mentioned above.
im getting the same thing on kali linuc, what should i do?
im getting the same thing on kali linuc, what should i do?
I suggest creating a symlink from /usr/local/bin/chrome
to the executable path of your Chrome installation (the path differs per distro/system, so you best find out yourself).
Describe the bug
2023/01/18 13:45:07 INFO [main] Hetty (v0.7.0) is running on :8080 ... 2023/01/18 13:45:07 INFO [main] Get started at http://localhost:8080 2023/01/18 13:45:07 INFO [main] Chrome executable not found.
To Reproduce
Steps to reproduce the behavior:
Error: INFO [main] Chrome executable not found
Expected behavior Chrome executable should be launched with hetty
Screenshots
Desktop (please complete the following information):
Additional context Even before I tried adding CHROME_EXECUTABLE and adding /usr/bin/google-chrome to path manually, no success