Chrome 121.0.6167.85 not working

[dmurdoch]

I have just updated Chrome, and RSelenium has stopped working. Running rsDriver fails as shown below.

Operating System: MacOS 12.7.3

Selenium Server version (selenium-server-standalone-3.0.1.jar etc.) Not sure how to determine this.

Browser version (firefox 50.1.0, chrome 54.0.2840.100 (64-bit) etc.) Chrome 121.0.6167.85

Other driver version (chromedriver 2.27, geckodriver v0.11.1, iedriver x64_3.0.0, PhantomJS 2.1.1 etc.) chromedriver 121.0.6167.85

Expected behaviour

Things were working fine before my Chrome upgrade.

Actual behaviour

Calling rsDriver fails. as shown below. To reproduce, install Chrome 121.0.6167.85 and run the line below.

rsDriver(verbose = TRUE, port = 6195L, chromever = "121.0.6167.85", geckover = NULL, phantomver = NULL)
checking Selenium Server versions:
BEGIN: PREDOWNLOAD
BEGIN: DOWNLOAD
BEGIN: POSTDOWNLOAD
checking chromedriver versions:
BEGIN: PREDOWNLOAD
BEGIN: DOWNLOAD
BEGIN: POSTDOWNLOAD
[1] "Connecting to remote server"

Selenium message:Unable to create new service: ChromeDriverService
Build info: version: '4.0.0-alpha-2', revision: 'f148142cf8', time: '2019-07-01T21:30:10'
System info: host: 'djmair3.local', ip: '2607:f2c0:e7c2:37b:5051:4819:eaae:b816', os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '1.8.0_71'
Driver info: driver.version: unknown

Could not open chrome browser.
Client error message:
	 Summary: SessionNotCreatedException
 	 Detail: A new session could not be created.
	 Further Details: run errorDetails method
Check server log for further details.
$client
[1] "No sessionInfo. Client browser is mostly likely not opened."

$server
PROCESS 'file23a798c7688.sh', running, pid 672.

I don't know where to look for the "server log". I get similar results whether or not I delete the downloaded "LICENSE.chromedriver" file.

[dmurdoch]

I found that the chromedriver executable that was installed in ~/Library/Application Support/binman_chromedriver/mac64/121.0.6167.85/chromedriver wasn't marked executable. Simply fixing that has got things working again.

[mapdek]

I found that the chromedriver executable that was installed in ~/Library/Application Support/binman_chromedriver/mac64/121.0.6167.85/chromedriver wasn't marked executable. Simply fixing that has got things working again.

@dmurdoch : can you explain how to make a chromedriver executable?

[dmurdoch]

@mapdek: Start terminal, and change directory to where the chromedriver file is stored. My current one is in ~/Library/Application Support/binman_chromedriver/mac-arm64/127.0.6533.119. The last part should be very similar to the version number of Chrome, but probably won't match exactly.

Make sure you have a file named chromedriver there. If you only have a *.zip file, you're in the wrong directory.

Run chmod a+x chromedriver.

That's it!

[mapdek]

Thank you @dmurdoch for your quick reply! This is the location and chromedriver file I have stored on my desktop:

as you mentioned, the chromedriver.exe is outside the .zip file. This was the case in previous Chromedriver versions and was working until recently.

The only (noticeable) change I had in my situation is a slower internet connection (as mentioned in this issue #274 ), but I am not sure this is related to Chrome not opening up.

[dmurdoch]

My instructions were for a Mac (or other Unix-like system). You're on Windows, so they won't work there.

[mapdek]

Apologies for this @dmurdoch, I hadn't seen that. Thanks!