Chromedriver 2.30 does not work with Chrome 61

Bug #1719690 reported by Noemi Lapresta
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

The latest `chromium-chromedriver` release (`61.0.3163.79-0ubuntu0.14.04.1196`) is actually Chromedriver 2.30, which does not work with Chromium 61, both according to the release notes [ https://chromedriver.storage.googleapis.com/2.32/notes.txt ] and to my attempts to use it.

Ubuntu version:

Description: Ubuntu 14.04.5 LTS
Release: 14.04

`chromium-chromedriver` version: 61.0.3163.79-0ubuntu0.14.04.1196
`chromium-browser` version: 61.0.3163.79-0ubuntu0.14.04.1196

What I expected to happen: `chromium-chromedriver` works with the `chromium-browser` version of the same version number.

What happened instead: Selenium reported an error from `chromium-chromedriver` when trying to use it to boot Chromium

Revision history for this message
Noemi Lapresta (purpliminal-deactivatedaccount) wrote :

Is it really a duplicate? In my case, Chromedriver can't even launch Chrome. This strikes me as markedly different from #1719572, where Chromedriver can launch Chrome, but some issues exist regarding clicking links outside the viewport.

Revision history for this message
Olivier Tilloy (osomon) wrote :

@Noemi, do you have a detailed error message? Can you share the commands you use to launch chromium with chromedriver?

Revision history for this message
Noemi Lapresta (purpliminal-deactivatedaccount) wrote :

We're using Watir from Ruby, which uses Selenium underneath. The way we connect is, essentially:

```
require 'watir'

Watir::Browser.new :chrome
```

This is the error we get from it, which isn't particularly clear:

```
unknown error: Chrome failed to start: exited abnormally
  (Driver info: chromedriver=2.30,platform=Linux 4.4.0-51-generic x86_64) (Selenium::WebDriver::Error::UnknownError)
```

Revision history for this message
Noemi Lapresta (purpliminal-deactivatedaccount) wrote :

Launching chromedriver independently and attempting to connect to it as a remote WebDriver instance, we can see that it attempts to launch chromium-browser as such:

```
/usr/lib/chromium-browser/chromium-browser --disable-background-networking --disable-client-side-phishing-detection --disable-default-apps --disable-hang-monitor --disable-popup-blocking --disable-prompt-on-repost --disable-sync --disable-web-resources --enable-automation --enable-logging --force-fieldtrials=SiteIsolationExtensions/Control --ignore-certificate-errors --load-extension=/tmp/.org.chromium.Chromium.89Gfz0/internal --log-level=0 --metrics-recording-only --no-first-run --password-store=basic --remote-debugging-port=12850 --safebrowsing-disable-auto-update --test-type=webdriver --use-mock-keychain --user-data-dir=/tmp/.org.chromium.Chromium.SGNNaW data:,
```

Which returns the following error:

```
/usr/lib/chromium-browser/chromium-browser: error while loading shared libraries: libffmpeg.so: cannot open shared object file: No such file or directory
```

Revision history for this message
Olivier Tilloy (osomon) wrote :

Ah, that is bug #1718885 then, for which a fix is currently being built, and should be deployed soon.

Revision history for this message
Noemi Lapresta (purpliminal-deactivatedaccount) wrote :

@Olivier Thank you!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.