selenium: [🐛 Bug]: Selenium 4.21.0 as a grid node/standalone for web cannot find edge binary

What happened?

Using 4.21.0 when starting an edge browser session it shows “cannot find msedge binary”. On the exact same system with the exact same browser/msedgedriver version using a different version of selenium the issue does not present it self.

Does not make a difference when passing in “binary” parameter for the “goog:chromeOption” dictionary in the stereotype field.

Also makes no difference if passing in the option via desired capabilities (python).

[server] role = “standalone”

[node] detect-drivers = false

[[node.driver-configuration]] display-name = “msedge” max-sessions = 8 stereotype = ‘{“browserName”: “msedge”, “platformName”:“linux”}’

Actually I checked a few versions, 20,19, all broken. So I went back to the old reliable 4.5.3 and it starts to work again.

How can we reproduce the issue?

Launch selenium 4.21.0 configured for edge browser on linux. Try to run a test against the server.

Relevant log output

16:22:15.132 WARN [SeleniumSpanExporter$1.lambda$export$1] - org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 500. Message: unknown error: cannot find msedge binary

Operating System

Ubuntu

Selenium version

4.21.0

What are the browser(s) and version(s) where you see this issue?

Edge 125.0.2535.51

What are the browser driver(s) and version(s) where you see this issue?

msedgedriver 125.0.2535.51

Are you using Selenium Grid?

No

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

That fixed the problem. Thank you!