Geckodriver executable needs to be in path linux

‘geckodriver’ executable needs to be in PATH #84

Comments

tXambe commented Jun 14, 2019 •

When execute PhoneInfoga I got this error:

[+] Scan URL: https://www.411.com/phone/3-666-666-666
Would you like to use an additional format for this number ? (y/N) N
[i] —- Web pages footprints —-
[i] Searching for footprints on web pages. (limit=10)
Traceback (most recent call last):
File «/root/.local/lib/python3.7/site-packages/selenium/webdriver/common/service.py», line 76, in start
stdin=PIPE)
File «/usr/lib/python3.7/subprocess.py», line 775, in init
restore_signals, start_new_session)
File «/usr/lib/python3.7/subprocess.py», line 1522, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: ‘geckodriver’: ‘geckodriver’

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «phoneinfoga.py», line 95, in
main()
File «phoneinfoga.py», line 71, in main
scanNumber(args.number)
File «phoneinfoga.py», line 38, in scanNumber
osintScan(number)
File «/opt/OSINT/PhoneInfoga/scanners/footprints.py», line 173, in osintScan
for result in search(req, stop=10):
File «/opt/OSINT/PhoneInfoga/lib/googlesearch.py», line 35, in search
browser = webdriver.Firefox()
File «/root/.local/lib/python3.7/site-packages/selenium/webdriver/firefox/webdriver.py», line 164, in init
self.service.start()
File «/root/.local/lib/python3.7/site-packages/selenium/webdriver/common/service.py», line 83, in start
os.path.basename(self.path), self.start_error_message)
selenium.common.exceptions.WebDriverException: Message: ‘geckodriver’ executable needs to be in PATH.

A greeting and thanks

The text was updated successfully, but these errors were encountered:

sundowndev commented Jun 14, 2019 •

It seems you didn’t installed geckodriver properly. See this comment on stackoverflow.

1. Are you using Docker ?
2. What command did you run ?
3. What is your OS ?
4. Do you have the latest version of Firefox installed ?
5. What is the output of geckodriver —version ?

C8be commented Jun 29, 2019

I have the same Problem and

1. I don’t use Docker
2. I ran the command python3 phoneinfoga.py -n %Number%
3. Ubuntu 16.04 LTS
4. Yes I updated Firefox
   5 and it says geckodriver: command not found

mashsajid commented Jul 6, 2019 •

This will fix the problem for Linux Users
wget https://github.com/mozilla/geckodriver/releases/download/v0.23.0/geckodriver-v0.23.0-linux64.tar.gz
sudo sh -c ‘tar -x geckodriver -zf geckodriver-v0.23.0-linux64.tar.gz -O > /usr/bin/geckodriver’
sudo chmod +x /usr/bin/geckodriver
rm geckodriver-v0.23.0-linux64.tar.gz

sundowndev commented Jul 16, 2019

Feel free to add further details, considering this as resolved.

popduck07 commented Jul 19, 2019

hey sundown, I’m relatively new to all this and I read the previous thread. I’m having the same issue, can you dumb it down for me? I’m using kali linux and I ran the command: «python3 phoneinfoga.py -n «(+X) XXXXXXXXXX». After I had responded with ‘n’ when it asked me about custom format it outputted:

Traceback (most recent call last):
File «/usr/local/lib/python3.7/dist-packages/selenium/webdriver/common/service.py», line 76, in start
stdin=PIPE)
File «/usr/lib/python3.7/subprocess.py», line 775, in init
restore_signals, start_new_session)
File «/usr/lib/python3.7/subprocess.py», line 1522, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: ‘geckodriver’: ‘geckodriver’

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File «phoneinfoga.py», line 95, in
main()
File «phoneinfoga.py», line 71, in main
scanNumber(args.number)
File «phoneinfoga.py», line 38, in scanNumber
osintScan(number)
File «/root/PhoneInfoga/scanners/footprints.py», line 173, in osintScan
for result in search(req, stop=10):
File «/root/PhoneInfoga/lib/googlesearch.py», line 35, in search
browser = webdriver.Firefox()
File «/usr/local/lib/python3.7/dist-packages/selenium/webdriver/firefox/webdriver.py», line 164, in init
self.service.start()
File «/usr/local/lib/python3.7/dist-packages/selenium/webdriver/common/service.py», line 83, in start
os.path.basename(self.path), self.start_error_message)
selenium.common.exceptions.WebDriverException: Message: ‘geckodriver’ executable needs to be in PATH.

how do I properly install the geckodriver? when I typed «pip install geckodriver» it outputted

Источник

geckodriver executable needs to be in path

I have read previous questions asked on this topic and tried to follow the suggestions but I continue to get errors. On terminal, I ran

When I run the following Python code

I still get the following error

5 Answers 5

you may downgrade your selenium by

pip install selenium==2.53.6

This has solved my issue

First we know that gekodriver is the driver engine of Firefox,and we know that driver.Firefox() is used to open Firefox browser, and it will call the gekodriver engine ,so we need to give the gekodirver a executable permission. so we download the latest gekodriver uncompress the tar packge ,and put gekodriver at the /usr/bin/ ok,that’s my answer and i have tested.

Homebrew is the most popular package manager for Mac OS X, you will need install XCode on your mac and it will be then accesible from your terminal.

You can follow this tutorial if required

I just downloaded the latest version geckodriver (I have win7) from here and added that exe-file in python directory (which already in PATH)

export path works only in the terminal you have entered the command. If you try to run the script from a different terminal, you will get the same error.

Not the answer you’re looking for? Browse other questions tagged python or ask your own question.

Linked

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

site design / logo © 2021 Stack Exchange Inc; user contributions licensed under cc by-sa. rev 2021.10.8.40416

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Firefox до 46 версии поставляется с поддержкой WebDriver. Geckodriver требуется для Firefox выше 47+ версии. Нужно установить geckodriver отдельно от браузера.

Скачать geckodriver для Linux, Windows и Mac

Зайдите на github страницу с релизами чтобы выбрать нужный вам файл для скачивания в зависимости от вашей операционной системы и версии браузера Firefox.

На текущий момент, актуальная версия geckodriver является v0.26.0.

Установка geckodriver под Ubuntu, Windows и Mac

Ниже мы приводим примеры более «правильной» установки драйвера, но есть и более быстрый способ. Примените данный метод в двух случаях.

1. Вам нужны разные версии geckodriver.
2. У вас не получилось ничего из того, что мы предлагаем ниже под каждую операционную систему.

Инструкция установки

1. Заходим на сайт https://github.com/mozilla/geckodriver/releases/
2. Скачиваем архив под вашу операционную систему
3. Распаковываем файл и запоминаем где находится файл geckodriver или geckodriver.exe (Windows)

Если у вас Linux дистрибутив или Mac, вам нужно дать файлу geckodriver нужные права на выполнения. Открываем терминал и вводим команды одна за другой.

Теперь, когда вы будете запускать код в Python, вы должны указать Selenium на этот файл.

Для Windows

Минусы такого подхода

1. Нужно помнить где у вас лежит geckodriver;
2. Нужно не забывать указывать в конструктор класса webdriver.Firefox путь к драйверу.

Установка geckodriver в Ubuntu, Debian и ArchLinux

Выбираем (в зависимости от архитектуры процессора x32 или x64) нужный tar архив. В моем случае будет файл geckodriver-v0.26.0-linux64.tar.gz у меня Ubuntu 18.04.3 LTS.

Вытаскиваем файл из архива.

Даем нужные права драйверу.

Отправляем драйвер в папку где его будет искать Selenium.

Установка geckodriver в Mac OS

Пожалуй, самая простая установка в Mac. Выполняем в терминале:

Проблема такого подхода в том, что может быть старая версия. Для новой версии смотрите на страницу github с релизами и скачиваем архив geckodriver-v0.26.0-macos.tar.gz.

Заходим через терминал в папку где будет лежать архив и сам драйвер.

Даем драйверу права на выполнения.

/.bashrc» с помощью VIM или NANO.

Добавляем в конец файла следующие строки. ВНИМАНИЕ! Заменяем «/your/path/» указывая реальный путь к geckodriver файлу.

Возможно вы не поймете как выйти из VIM. Такое бывает.

1. Нажимаем клавишу ESC
2. Вводим символы :wq
3. Enter

Теперь у вас будет последняя версия geckodriver на вашем новеньком маке.

Установка geckodriver в Windows

Windows пользователи возможно не слышали о таким виде архивов как tar.gz это нормально. Скачиваем и устанавливаем программу 7-Zip.

Программа для распаковки tar.gz в Windows: http://www.7-zip.org/

Полная инструкция по установки geckodriver в Windows показана в видео. Смотрим с 40 секунды и повторяем. Помните что не нужно скачивать именно ту версию, что указана в видео. По указанной ссылке с github последняя версия 0.19.1 когда в самом видео 12-я версия. Скачивайте самую новую версию, возможно когда вы сейчас читаете эту статью уже вышла новая версия — скачиваем её.

Скрипт теста ниже откроет веб-сайт в новом окне Firefox.

Источник

«‘geckodriver’ executable needs to be in PATH» error in 1.11.2 #139

Comments

bavaria95 commented Nov 17, 2017

After update of pytest-selenium to 1.11.2 (0773c93 to be more precise) my selenium tests stopped working (using Firefox).
I started to receive WebDriverException: Message: ‘geckodriver’ executable needs to be in PATH. error.
Debugging has shown that capabilities now are getting set to <'acceptInsecureCerts': True, 'browserName': 'firefox', 'marionette': True>, instead of <'browserName': 'firefox'>, which was the case before the update (now it takes them from selenium’s DesiredCapabilities )

The text was updated successfully, but these errors were encountered:

bavaria95 commented Nov 17, 2017

Setting marionette capability as a pytest argument (to empty string, due to the fact that it considers all passed arguments as strings and python will consider empty string as False) helped me:
—capability marionette »

davehunt commented Nov 17, 2017

This was in fact a bug before, as the default has been to use Marionette since Selenium 3 was released, and meant that you would have inconsistent behaviour between local browsers and those running against a remote server. To use the plugin against old Firefox versions with the legacy driver, you can either set the marionette capability to an empty string on the command line, which evaluates as Falsy (as you have), or you can set it to False using the capabilities fixture:

My recommendation would be to run your tests against a modern version of Firefox, which requires the geckodriver binary to be available in your path. There’s some documentation on this here.

bavaria95 commented Nov 17, 2017

@davehunt
Selenium is running as a separate docker container, thus it’s remote)

davehunt commented Nov 17, 2017

@bavaria95 then it would depend on the version of Selenium running. Marionette has been enabled by default since 3.0. The official docker images from Selenium also come with geckodriver binary installed.

david-caro commented Nov 17, 2017

@davehunt hi, a collegue of @bavaria95 here, so we are running pytest-selenium on a container, and selenium on another, but for some reason it’s looking for the binary on the pytest-selenium container instead of trying to connect to the selenium one (as it did before, and as it does when settting marionette to False ).
Maybe there’s something else we have to specify to force it to connect to the remote selenium?

davehunt commented Nov 17, 2017

@david-caro okay, that does sound like a bug.. let me take a look

davehunt commented Nov 17, 2017

@bavaria95 @david-caro could you provide a full traceback? I can’t see why pytest-selenium or selenium would be looking for geckodriver when specifying a remote driver, and a trace would help me to identify what code is failing.

bavaria95 commented Nov 17, 2017

davehunt commented Nov 17, 2017

Okay, you have selenium.webdriver.firefox.webdriver.WebDriver where you should have selenium.webdriver.remote.webdriver.WebDriver .. What are you command line options? Could you also provide the pytest header from the console?

davehunt commented Nov 17, 2017

bavaria95 commented Nov 17, 2017

py.test —driver Remote —host selenium —port 4444 —capability browserName firefox —html=selenium-report.html tests/acceptance

davehunt commented Nov 17, 2017

hmm.. there’s clearly something odd because driver: Firefox in the pytest header should be driver: Remote based on those command line arguments. I’ll keep digging.

davehunt commented Nov 17, 2017

@bavaria95 is this something I can attempt to replicate? I’ve cloned https://github.com/inspirehep/inspire-next/ and was able to run the tests using:

The tests ran, with the following pytest header showing the correct driver:

The first time I ran I had tests failing due to elements not being found, and another time I had connection timeouts. I did not see the geckodriver issue, however I did when I ran docker-compose -f docker-compose.test.yml run —rm visible-acceptance , which specified a driver of Firefox.

davehunt commented Nov 17, 2017

I just following the instructions again (I think I missed the docker-compose -f docker-compose.deps.yml run —rm assets step originally, and the ‘acceptance’ tests are now passing for me.

bavaria95 commented Nov 20, 2017

@davehunt
Okay, there is my bad, actually in the code I was using —driver Firefox . And it makes sense why it doesn’t work (after changing to —driver Remote it works without setting up marionette to False).
Buuut, the question is, how was it working before with the same driver? Right now I made some tests with my older image (before library update) and my new image (after library update).
Looks like:

davehunt commented Nov 20, 2017

This was because before version 1.11.2 the capabilities were empty by default, meaning the marionette capability was not present and legacy Firefox was used. This was fixed so that the appropriate defaults were set according to the Selenium client, and therefore marionette and modern Firefox are used. See 0773c93#diff-88a7aec9c2361f634a0f93e317ffa663R44 for the specific change.

I’d suggest this is a welcome issue to discover, as it suggests your tests are running on an old version of Firefox, which most likely does not represent your user base. It should be trivial to update Firefox and install geckodriver onto this image to resolve you current issue.

Also note that when using —driver Firefox the —host and —port arguments are no necessary, and might add confusion. Please let me know if there’s anything else I can help with.

bavaria95 commented Nov 20, 2017 •

Great, thanks. I think this one can be closed then.
@david-caro, perhaps we can try upgrading firefox version for tests, right?

davehunt commented Nov 20, 2017

In case it’s helpful, here’s where the official Selenium images install Firefox and geckodriver: https://github.com/SeleniumHQ/docker-selenium/blob/master/NodeFirefox/Dockerfile#L10-L35

davehunt commented Nov 28, 2017

Closing this, as it seems to not be an issue with the plugin.

You can’t perform that action at this time.

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.

Источник