Protractor 5.1.1 doesn't work with Chrome 57

(node:9828) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[11:48:42] I/launcher - Running 1 instances of WebDriver
[11:48:42] I/local - Starting selenium standalone server...
[11:49:12] E/launcher - Error: Error: Timed out waiting for the WebDriver server at http://10.10.10.76:45678/wd/hub
    at onError (C:\projects\JustEat.TopPlacement.ManagementWeb\src\JustEat.TopPlacement.ManagementWeb.ProtractorTests\node_modules\selenium-webdriver\http\util.js:102:16)
    at process._tickCallback (internal/process/next_tick.js:103:7)
[11:49:12] E/launcher - Process exited with error code 100

Protractor.conf.js looks like this:

    allScriptsTimeout: 30000,
    specs: [
        "./**tests/*.js"
    ],
    capabilities: {
        browserName: "chrome",
        chromeOptions: {
            args: ["--test-type", "--no-sandbox"],
        },
        loggingPrefs: {
            browser: "ALL"
        }
    },
    jasmineNodeOpts: {
        showColors: true,
        defaultTimeoutInterval: 5 * 60 * 1000
    },

[qualityshepherd]

Just for completeness, thanks to @NickTulett suggestion, you can turn off the password manager (and infobars) in Protractor thusly…

    capabilities: {
        browserName: 'chrome',
        chromeOptions: {
            args: [
                '--disable-infobars'
            ],
            prefs: {
                // disable chrome's annoying password manager
                'profile.password_manager_enabled': false,
                'credentials_enable_service': false,
                'password_manager_enabled': false
            }
        }
    },

[dinvlad]

UPDATE: removing “–remote-debugging-port” option from Protractor config (but not Karma!) solves the issue (understandably, because it interferes with ChromeDriver on that port)! I.e. Protractor 5.1.1 works with Chrome 57 on a headless system without Xvfb. https://github.com/angular/protractor/issues/4164#issuecomment-288909191 if anyone is interested.