Indeed, your last comment is relevant, I can now reproduce the problem
in a Wayland session. The same test runs fine in an X11 session.
** Summary changed:
- chromedriver doesn't work with the snap package, without --headless
+ [snap] chromedriver doesn't work without --headless under Wayland
This is interesting information!
I have the chromium and chromium-chromedriver packages installed via
apt. I wonder if that is why my example (headless) can work without
overriding executable_path? chromium-chromedriver ships a
/usr/bin/chromedriver that's a shell script that exec's
That minimal example doesn't run here in a clean 20.04 VM with the
chromium snap. However if I apply this minimal modification to the
script, it succeeds, with and without the headless switch:
-driver = webdriver.Chrome(options=options)
+driver_path = "/snap/bin/chromium.chromedriver"
Here's my minimal example:
#!/usr/bin/env python3
import time
import sys
from selenium import webdriver
options = webdriver.chrome.options.Options()
if '--headless' in sys.argv:
options.add_argument("headless")
driver = webdriver.Chrome(options=options)
driver.get("https://ubuntu.com;)
I am able to successfully run the chromium snap's (admittedly very
basic) tests without headless mode. The tests are at
https://git.launchpad.net/~chromium-team/chromium-browser/+git/snap-
from-source/tree/tests?h=stable.
Marius, could you maybe share a minimal reproducer that fails, so I can
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
6 matches
Mail list logo
