Firefox 50.1.0 not working

[stanbe]

Bug report

• Node Version: 6.7.0
• Protractor Version: 4.0.10
• Angular Version: 2.1.0
• Browser(s): Firefox 50.1.0
• Operating System and Version Win8.1 Enterprise
• Your protractor configuration file

exports.config = {
    capabilities: {
        'browserName': 'firefox'
    },
    specs: ['**/*.e2e.spec.js'],
    useAllAngular2AppRoots: true,
    baseUrl: 'http://localhost:64065/',
    directConnect : true
};

• A relevant example test

describe('Expense overview list', function () {

    it('should should have Anakin Skywalker as first entry', function () {
        browser.get('/home');
        expect(browser.getTitle()).toEqual('Angular');

        browser.get('/overview');

        expect(element(by.id('00000000-0000-0000-0000-000000000001')).getText()).toEqual('ANAKIN SKYWALKER');
    });
});

• Output from running the test

[15:08:27] I/direct - Using FirefoxDriver directly...
[15:08:27] I/launcher - Running 1 instances of WebDriver
[15:09:12] E/launcher - Timed out waiting for the WebDriver server at http://127.0.0.1:60626/hub
[15:09:12] E/launcher - Error: Timed out waiting for the WebDriver server at http://127.0.0.1:60626/hub
    at Error (native)
    at onError (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\http\util.js:87:11)
    at ManagedPromise.invokeCallback_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:1379:14)
    at TaskQueue.execute_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2913:14)
    at TaskQueue.executeNext_ (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2896:21)
    at asyncRun (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:2775:27)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\promise.js:639:7
    at process._tickCallback (internal/process/next_tick.js:103:7)
From: Task: WebDriver.createSession()
    at Function.createSession (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:329:24)
    at Driver (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\firefox\index.js:386:38)
    at Direct.getNewDriver (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\direct.js:75:26)
    at Runner.createBrowser (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\runner.js:198:43)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\built\runner.js:285:30
    at _fulfilled (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
    at self.promiseDispatch.done (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30)
    at Promise.promise.promiseDispatch (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
    at C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:556:49
    at runSingle (C:\Users\john\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:137:13)
[15:09:12] E/launcher - Process exited with error code 199

• Steps to reproduce the bug
  just run protractor protractor.conf.js
• The URL you are running your tests against (if relevant)
  see protractor.conf.js

Firefox is starting but nothing happens, just an empty screen.

[Xotabu4]

+1

[ThomasOpiolka]

+1

[BishuSinha]

+1

[juliemr]

Right, firefox is very confused with the latest versions of selenium server. We're investigating what's compatible with what now, with marionettedriver and geckodriver and various versions of selenium. Stay tuned.

[juliemr]

See also #3750

[sjelin]

(assigning to you @mgiambalvo because I didn't assign many over issues to you, and I feel like I need to balance)

[heathkit]

We will need to update the directConnect provider for Selenium 3.0. However, Firefox is still broken. We can address this once Firefox 51 ships.