appium/appium — pull request #2880 by rickihastings (2014-06-17 13:06:49+00:00)
Title: Detect architecture type on linux

We should detecting architecture type because chromedriver can have problems running 32bit if the required libraries aren't available on a 64bit OS.

```
debug: Killing any old chromedrivers, running: ps -e | grep /home/testuser/dev/appium/build/chromedriver/linux/chromedriver | grep -v grep |grep -e '--port=9515$' | awk '{ print $1 }' | xargs kill -15
debug: Successfully cleaned up old chromedrivers
debug: Spawning chromedriver with: /home/testuser/dev/appium/build/chromedriver/linux/chromedriver
debug: [CHROMEDRIVER STDERR] /home/testuser/dev/appium/build/chromedriver/linux/chromedriver: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory
debug: Chromedriver exited with code 127
debug: Cleaning up appium session
error: Failed to start an Appium session, err was: Error: Chromedriver quit before it was available
debug: Error: Chromedriver quit before it was available
at Chromedriver.onClose (/home/testuser/dev/appium/lib/devices/android/chromedriver.js:120:11)
at ChildProcess.emit (events.js:98:17)
at Process.ChildProcess._handle.onexit (child_process.js:809:12)
debug: Responding to client with error: {"status":33,"value":{"message":"A new session could not be created. (Original error: Chromedriver quit before it was available)","origValue":"Chromedriver quit before it was available"},"sessionId":null}
POST /wd/hub/session 500 2126.288 ms - 204
```
This occurs on a 64bit of the latest Ubuntu desktop, I also had a similar error occur on CentOS, but didn't debug it far enough to realise it was looking for 32bit libraries. This pull request will fix this.