Closed noraj closed 2 years ago
Workaround:
sudo mkdir /usr/lib/chromium-browser
sudo ln -s /usr/lib/chromium/chromedriver /usr/lib/chromium-browser/chromedriver
There is an option to configure the location in the UI, but the UI won't load on the first place if the driver loading fails...
The same problem affects Burp on Windows where creating /usr/lib/chromium-browser directory is not possible. Please change it so there will be no loading of chromedriver on start, but after selecting the driver.
I have the same problem on MasOS Monterey (12.x) - I can't write to /usr/lib
because of the System Integrity Protection
So, basically this plugin is unusable on MacOS
I opened this issue the 7 Nov 2019 but the project has not been updated since 30 Oct 2019 so I guess it is abandoned.
The login looks for chromedriver in
/usr/lib/chromium-browser/chromedriver
as if it was the standard way. On ArchLinux and others distro it is located at/usr/lib/chromium
.Maybe you should look for several standard path before raising an error.