New issue
Advanced search Search tips

Issue 1894 link

Starred by 14 users

Issue metadata

Status: Fixed
Owner: ----
Closed: Jul 2017

Sign in to add a comment

chromedriver 2.31 should be linked with glibc 2.17

Reported by, Jul 25 2017

Issue description

Issue Description:

Trying to run chromedriver 2.31 on latest RHEL or Centos (version 7.3) results in a missing GLIBC 2.18 library reference:

Steps to reproduce (if relevant, you MUST provide a simplified html page or
link to public site):

# wget
# unzip
# ./chromedriver --version
./chromedriver: /lib64/ version `GLIBC_2.18' not found (required by ./chromedriver)

-----Other helpful tips:

Using chromedriver 2.30 works, but there are significant bugfixes in 2.31.

Ditto.  Just ran into this this morning
Project Member

Comment 2 by, Jul 25 2017

Status: WontFix (was: Unconfirmed)
Like John mentioned here, glibc version used by Chromium has been updated and there is no good way to work around that.

Closing the issue. If anyone has suggestions, please feel free to post here and we will reopen the issue.
Project Member

Comment 3 by, Jul 26 2017

 Issue 1899  has been merged into this issue.

Comment 4 Deleted

Hello ChromeDriver Team,

Could you please recommend what should be done with Centos 7 installations?

Comment 7 by, Aug 1 2017

I've seem chromium had a commit to relax to GLIBC 2.17.
Is that a good sign that next chromedriver will have the GLIBC 2.18 constraint relaxed too?
Project Member

Comment 8 by, Aug 1 2017

Labels: ChromeDriver-2.32
Status: Fixed (was: WontFix)
Yes, with, the next release of ChromeDriver will back to require only GLIBC 2.17.
Project Member

Comment 9 by, Aug 11 2017

 Issue 1926  has been merged into this issue.
Is there any timetable for a 2.32 release?

Comment 11 Deleted

Project Member

Comment 12 by, Aug 30 2017

Release cycle has already begun. New binaries will be uploaded soon.
Thanks for your patience!
Thank you!

Comment 14 by, Sep 1 2017

It looks like 2.32 binary is available and the GLIBC dependency issue is fixed. Thank you!

Sign in to add a comment