Ubuntu 24 - X11 display failed! Will use regular xvfb!

[alepodj]

Hello

Currently having an interesting issue running on of the examples "as is" but with my own url: examples/cdp_mode/raw_res_sb.py

I seem to be unable to get Chrome to open with the following errors:

start error

X11 display failed! Will use regular xvfb!

...

File "/home/<user>/Documents/Dev/inventory/venv/lib/python3.12/site-packages/selenium/webdriver/remote/errorhandler.py", line 232, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.SessionNotCreatedException: Message: session not created: cannot connect to chrome at 127.0.0.1:9222
from chrome not reachable
...

From previous posts ive also followed up on having all X11 requirements install which i seem to have based on the outcome of all commands found in the links provided

Additionally, even when using xvfb=False it doesnt give the X11 error but it failed with the same traceback error.

I honestly dont need chrome to show up, just need to get a given event.response from the site, but neither of the modes above seem to be working for me

Thanks in advance 🙏

[mdmintz]

For the X11 display failed!, that's a duplicate of #3060 and #2982.

Check the following to find out if your Linux distribution is missing X11 display dependencies:

• https://askubuntu.com/questions/1006753/how-to-check-if-the-x11-display-manager-is-installed
• https://stackoverflow.com/a/30120178/7058266
• https://askubuntu.com/questions/213678/how-to-install-x11-xorg

---

For the other error, that's a duplicate of #3370 (comment).

Message: session not created: cannot connect to chrome at 127.0.0.1:9222 from chrome not reachable

That usually means Chrome is not in the default location for the OS being used, so you must set it manually with binary_location. Eg: binary_location="/usr/bin/google-chrome". Figure out where Chrome is located, and then set it. Note that on Linux, you'll need to use either google-chrome-stable or google-chrome (but NOT chromium).

Other possible reasons may include port conflicts if multithreading, or missing Linux permissions.

Note that the point of xvfb is so that you don't have to use headless Chrome, which is detectable.

[alepodj]

Lifesaver!

It was: binary_location="/usr/bin/google-chrome-stable"