[🐛 Bug]: Selenium 4.11.x not working with Chronium. #12466
Comments
|
@ikus060, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
|
Seams v4.10 uses my local installation of chronium, while v4.11 is using the version downloaded into Not sure why it doesn't use the local version. |
|
The problem seams to reside in With v4.11 it doesn't find my local installation of chronium. So it download it. |
4.10.0 was stable. I shifted all my scripts back to 4.10.0 and now the scripts are working fine. |
|
@bonigarcia @titusfortner do you know why Chromium is not being detected? |
|
I don't think SM is looking for Chromium? I also don't think it should... I think if you want something other than a released/named version of Chrome, you'll need to pass in the location of chromium in options class. |
Far enough. Could I define the location of chronium and chronium driver ? Both are available in PATH: |
|
Hmm, can you turn on logging so we can see what selenium manager is doing? https://www.selenium.dev/documentation/webdriver/troubleshooting/logging/ I think if the driver is found on PATH, but SM didn't see a browser, it will use that driver and try to get the browser for that driver. I'm trying to think what 4.10 would do... 4.10 would skip SM entirely. I can't remember if chromedriver looks for Chromium browsers if it can't find chrome, but that would make sense. Ok, so, if chrome isn't found, should SM look to see if chromium is installed instead of treating it as nothing installed... Probably if that better matches 4.10 behavior. |
|
The current implementation of Selenium Manager does not look for Chromium, just Chrome. But, of course, it can be implemented. If we want to support it, there are two possibilities:
|
Your chromedriver in the PATH is already being detected by Selenium Manager. Maybe the only thing you need to specify your browser binary ( |
|
@bonigarcia Thanks alot for your support. It's well appreciated. Are we seeing the same thing ?
|
|
Yes, chromedriver did look for chromium and now also looks for chrome for testing - https://github.com/bayandin/chromedriver/blob/main/chrome/chrome_finder.cc#L34 I think Selenium Manager needs to do the same before downloading something new. |
|
As recommended, to support selenium <=4.10 and selenium>=4.11, I used the following code: This effectively skip selenium-manager, use the chromedriver from the PATH and automatically find chronium web browser. |
|
better option is to just always the location of the browser you want: Selenium will get the right driver for whatever is there. |
Selenium Manager already checks for the existence of Chrome before downloading CfT. |
|
Right, I'm saying it should also check for an installed CfT and an installed Chromium. |
SM already checks CfT releases on the cache before downloading a new one.
That is what I said above it is not implemented (see my first post in this thread). |
|
As a workaround, I've added a symbolic link called So it looks like my version of chromedriver might not be compatible with the exact same version of chrome 🤔, and that an older version of chromedriver is recommended instead. I'm using Ruby with selenium-webdriver 4.11. The code I'm working with can be found at consuldemocracy/consuldemocracy#5162. |
|
You can turn on debugging to see what it's seeing, but you have a chrome/chromium install with version 111 somewhere. Selenium::WebDriver.logger.level = :debug |
|
I do. Sorry I didn't explain it correctly 🙏. And then I've created a Here's the output with debugging turned on: |
|
Ah, I didn't read your post closely enough. |
|
Currently, the warning is shown when the driver in PATH is strictly different from the recommended driver. This is your case (you have chromedriver 111.0.5563.146, and the recommended version is 111.0.5563.64). But typically, you don't need to worry since the major version (111) matches. So we have changed the Selenium Manager logic to show only the warning message when the major version is different. |
|
@bonigarcia I think the second one here is easier, and more closely follows default (non-SM) behavior - #12466 (comment) Can we track that somewhere else and close this one? |
|
|
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
Latest version 4.11.x is not working with Chronium. While the same code is working fine with 4.10.0.
How can we reproduce the issue?
Operating System
Ubuntu Linux 64bits
Selenium version
What are the browser(s) and version(s) where you see this issue?
Chromium 115.0.5790.102 snap
What are the browser driver(s) and version(s) where you see this issue?
Not sure
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: