{"action":"created","issue":{"url":"https://api.github.com/repos/testem/testem/issues/772","repository_url":"https://api.github.com/repos/testem/testem","labels_url":"https://api.github.com/repos/testem/testem/issues/772/labels{/name}","comments_url":"https://api.github.com/repos/testem/testem/issues/772/comments","events_url":"https://api.github.com/repos/testem/testem/issues/772/events","html_url":"https://github.com/testem/testem/issues/772","id":130412559,"number":772,"title":"dbus-launch with chromium via xfvb does not launch","user":{"login":"aortbals","id":871328,"avatar_url":"https://avatars.githubusercontent.com/u/871328?v=3","gravatar_id":"","url":"https://api.github.com/users/aortbals","html_url":"https://github.com/aortbals","followers_url":"https://api.github.com/users/aortbals/followers","following_url":"https://api.github.com/users/aortbals/following{/other_user}","gists_url":"https://api.github.com/users/aortbals/gists{/gist_id}","starred_url":"https://api.github.com/users/aortbals/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/aortbals/subscriptions","organizations_url":"https://api.github.com/users/aortbals/orgs","repos_url":"https://api.github.com/users/aortbals/repos","events_url":"https://api.github.com/users/aortbals/events{/privacy}","received_events_url":"https://api.github.com/users/aortbals/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2016-02-01T16:36:05Z","updated_at":"2016-02-02T22:27:40Z","closed_at":"2016-02-02T20:24:22Z","body":"When upgrading from [ember-cli#v2.2.0-beta.1](https://github.com/ember-cli/ember-cli/releases/tag/v2.3.0-beta.1) to [ember-cli#v2.3.0-beta.1](https://github.com/ember-cli/ember-cli/releases/tag/v2.3.0-beta.1), testem was upgraded from `0.9.11` to `1.1.3` (resolved from `^1.0.0`). This includes the [dbus-launch changes](https://github.com/testem/testem/pull/689). This causes the following error when running testem with [chromium](https://launchpad.net/ubuntu/trusty/+source/chromium-browser) on Ubuntu 14.04 via jenkins and xvfb.\r\n\r\n```\r\nBuilt project successfully. Stored in \"XXX\".\r\nnot ok 1 Browser \"dbus-launch --exit-with-session chromium,chromium-browser --user-data-dir=/tmp/testem.chromium --no-default-browser-check --no-first-run --ignore-certificate-errors http://localhost:8371/7540\" exited unexpectedly with exit code 1.\r\n\r\n1..1\r\n# tests 1\r\n# pass  0\r\n# skip  0\r\n# fail  1\r\nXvfb stopping\r\n```\r\n\r\nI was not able to find a solution with the current version, I reverted the upgrade which fixed this issue."},"comment":{"url":"https://api.github.com/repos/testem/testem/issues/comments/178863856","html_url":"https://github.com/testem/testem/issues/772#issuecomment-178863856","issue_url":"https://api.github.com/repos/testem/testem/issues/772","id":178863856,"user":{"login":"davidhao3300","id":5534398,"avatar_url":"https://avatars.githubusercontent.com/u/5534398?v=3","gravatar_id":"","url":"https://api.github.com/users/davidhao3300","html_url":"https://github.com/davidhao3300","followers_url":"https://api.github.com/users/davidhao3300/followers","following_url":"https://api.github.com/users/davidhao3300/following{/other_user}","gists_url":"https://api.github.com/users/davidhao3300/gists{/gist_id}","starred_url":"https://api.github.com/users/davidhao3300/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidhao3300/subscriptions","organizations_url":"https://api.github.com/users/davidhao3300/orgs","repos_url":"https://api.github.com/users/davidhao3300/repos","events_url":"https://api.github.com/users/davidhao3300/events{/privacy}","received_events_url":"https://api.github.com/users/davidhao3300/received_events","type":"User","site_admin":false},"created_at":"2016-02-02T22:27:40Z","updated_at":"2016-02-02T22:27:40Z","body":"Well, the main reason why I introduced this workaround is because Chrome consistently hangs for us on our Linux machines, didn't realize it affected Testem's tests as well lol. We can also introduce this as a flag that's by default off if it turns out this affects users differently for whatever reason."}}