unable to start chromedriver 2.16 on Debian machines

[GoogleCodeExporter]

See http://goo.gl/ll2FvQ for common issues.

Issue Description:

We have not been able to start the latest chrome driver version 2.16 on our 
Debian machines. Looks like it is unable to find dependent libraries.

The behavior is strange since for chrome driver version 2.15, it is able to 
locate same dependent libraries easily.

Please find the attached log for not working version 2.16 versus working 
version 2.15 with dependent libraries output.

-----Other helpful tips:
Attach your chromedriver log with verbose logging enabled (see
http://goo.gl/5Sx8mC for how to do this).

Original issue reported on code.google.com by tanvi.gour on 22 Jun 2015 at 9:14

Attachments:

• logs.txt

[GoogleCodeExporter]

Both 2.15 and 2.16 are linked against libgobject-2.0.so.0, so either both 
should work or both should fail. From the logs, it looks like you've got some 
kind of sandbox set up. Can you let us know a bit more about how this works? In 
particular, is the libglib2.0-0 package installed inside the sandbox?

Also, your 2.15 binary is 64-bit whereas the 2.16 binary is 32-bit. So you 
might need to install the 32-bit versions of each of these libraries as well?

Original comment by samu...@chromium.org on 29 Jun 2015 at 5:17

• Added labels: Needs-Feedback