Closed AlexWhitham closed 1 month ago
@AlexWhitham, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
I don't see how this is a Selenium issue. Can you please elaborate?
The Selenium webdriver won't instantiate. It works with Chrome major version 126 but not 127. As I understand it, because it is a Selenium webdriver - it is a Selenium issue, no? Also Chrome and Chrome driver instantiate correctly with no issues
Aside from the link I shared in the other issue, what else have you tried to understand the root cause? Have you tried the options I shared in the link?
I tried to set versions of Chrome and Chrome driver to ensure the problem is occurring only starting from 127. I tried 128 as well and I got the same result. I did use the options but it didn't help.
Because there is no error, if I remove the timeout it just keeps running forever, I have no way to understand what is going on.
What happens when you run that code outside of a Docker container?
Well it needs to be run in a container, but I will give it a go locally
7.682 [1724161347.414][INFO]: Launching chrome: /usr/bin/google-chrome-stable --allow-pre-commit-input --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-dev-shm-usage --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --enable-automation --enable-logging --headless --log-level=0 --no-first-run --no-sandbox --no-service-autorun --password-store=basic --remote-debugging-port=0 --test-type=webdriver --use-mock-keychain --user-data-dir=/tmp/.org.chromium.Chromium.vdJffZ --window-size=1920,1080 data:,
Can you update argument --headless
to --headless=new
?
Thank you @VietND96 just tried that, didn't help
It did work locally @diemol ... I am going to explode. I guess I need a different container setup. Thanks!
What was the issue?
Not sure yet, but I guess the container itself is the issue, since it is working locally
The issue was ENV DISPLAY=:99
🤦🏼♀️
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.
What happened?
Running in a docker container on python:3-slim. After the Chrome version changed from major 126 to 127 webdriver wouldn't instantiate. If I change the version back to 126, all goes well.
Chrome and Chrome driver versions are 127.0.6533.119
Docker container: Linux, python
How can we reproduce the issue?
Relevant log output
Operating System
Linux
Selenium version
3 and 4
What are the browser(s) and version(s) where you see this issue?
Major version 127 and up
What are the browser driver(s) and version(s) where you see this issue?
Major version 127 and up
Are you using Selenium Grid?
No response