Missing error handler on `socket`

### Expected behavior

My Travis CI build to complete the Jasmine Unit tests defined, reporting the number run and success vs. failure.
### Actual behavior

This is the output from my build log. [Here](https://travis-ci.org/georgeedwards/Gen-App/builds/120847556) is the full build log. Also, [here](https://github.com/georgeedwards/Gen-App/commit/fba70d6960b88ea01858ef8b1fc26eece1e49e34) is the full github repository that was being built.

```
[09:39:04] Starting 'client.unit_test'...
05 04 2016 09:39:04.281:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
05 04 2016 09:39:04.287:INFO [launcher]: Starting browser Chrome
05 04 2016 09:39:05.519:INFO [Chrome 49.0.2623 (Linux 0.0.0)]: Connected on socket /#7wcOJ3uFvZX-HgZeAAAA with id 49035067
Missing error handler on `socket`.
TypeError: (msg || "").replace is not a function
at /home/travis/build/georgeedwards/Gen-App/node_modules/karma/lib/reporter.js:45:23
at [object Object].onBrowserError (/home/travis/build/georgeedwards/Gen-App/node_modules/karma/lib/reporters/base.js:58:60)
```
### Enviroment Details
- Karma version (output of `karma --version`):
- Relevant part of your `karma.config.js` file

```
├── karma@0.13.22
├── karma-chrome-launcher@0.1.12
├── karma-coverage@0.2.7
├── karma-firefox-launcher@0.1.7
├── karma-ie-launcher@0.1.5
├── karma-jasmine@0.3.8
├── karma-ng-html2js-preprocessor@0.1.2
├── karma-opera-launcher@0.1.0
├── karma-phantomjs-launcher@0.1.4
```

Not sure which bits of the config file are relevant, [here](https://github.com/georgeedwards/Gen-App/blob/fba70d6960b88ea01858ef8b1fc26eece1e49e34/karma.conf.js) is the whole thing.
### Steps to reproduce the behaviour
1. Clone my Repo (link above)
2. Build it on Travis, or presumably any other ubuntu build server
3.

Start with karma/lib/reporter.js:45 and karma/lib/reporters/base.js:58, then reproduce the reported Karma 0.13.22 Jasmine run using the linked repository and karma.conf.js. Check the browser-error path associated with the non-string message and verify that the Travis-style test run completes without the reported TypeError or missing error-handler message.

Written by the indexing model from the issue text.