The call to gconf_client_get_bool(...) at [1] hangs indefinitely on start-up when Chrome is started in an environment where gconfd is not available. 

This seems to be quite common in testing scenarios with Chromedriver and Xvfb, where there is no full desktop environment. I suspect this is also the root cause for [2].

[1] https://cs.chromium.org/chromium/src/ui/accessibility/platform/atk_util_auralinux.cc?rcl=0&l=64

[2] https://github.com/SeleniumHQ/docker-selenium/issues/87