command not found

[dominicbarnes]

On my Fedora 20 laptop (and presumably my Ubuntu 14.04 desktop, but I'm not at home atm) duo-test does not work very well.

$ duo test browser

  Error: Command failed: /bin/sh -c google chrome "http://localhost:60883/test/"
/bin/sh: google: command not found

    at ChildProcess.exithandler (child_process.js:729:12)
    at ChildProcess.EventEmitter.emit (events.js:110:17)
    at maybeClose (child_process.js:992:16)
    at Socket.<anonymous> (child_process.js:1142:11)
    at Socket.EventEmitter.emit (events.js:107:17)
    at Pipe.close (net.js:461:12)

On my machine at least, the command is called google-chrome, but I'm guessing this is not the case on Mac?

The name function is returning "google chrome", which after changing it to "google-chrome" it worked. (also noticed "internet explorer" should probably be "iexplorer".

[dominicbarnes]

I'm opening up an issue instead of a PR because I suspect we have a cross-OS problem to solve.

[matthewmueller]

ahh, okay. might be related some sort of process.argv slicing.

tossing in my preference for shorter names anyway, chrome and ie.

[yields]

works ok on my mac, what happens when you do xdg-open "google chrome" ?

[dominicbarnes]

@yields I get an error: Unable to detect the URI-scheme of "google chrome".

[Frikki]

Same issue on Linux Mint 17.1.

[stephenmathieson]

yeah .. a college had the same issue. got this stack trace:

  Error: Command failed: Unable to find application named 'google chrome'
    at ChildProcess.exithandler (child_process.js:648:15)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:756:16)
    at Socket.<anonymous> (child_process.js:969:11)
    at Socket.emit (events.js:95:17)
    at Pipe.close (net.js:465:12)

make: *** [test-browser] Error 1

but no more information