cypress: Error: Could not start Xvfb. Install XVFB and run Cypress again.

We have the same problem on version 3.1.0

We has this same problem with Jenkins. Someone fixed it?

I’ve also reproduced this issue on gitlab-ci.

I’m still seeing this on GitLab CI with cypress v3.6.1

Still having this issue on Cypress 3.4.1 on Bitbucket pipelines:

It looks like this is your first time using Cypress: 3.4.1

[12:39:34]  Verifying Cypress can run /root/.cache/Cypress/3.4.1/Cypress [started]
[12:39:34]  Verifying Cypress can run /root/.cache/Cypress/3.4.1/Cypress [failed]
Your system is missing the dependency: Xvfb

Install Xvfb and run Cypress again.

Read our documentation on dependencies for more information:
https://on.cypress.io/required-dependencies

----------
Error: spawn Xvfb ENOENT
----------

I’m sure that XVFB is installed

Landing here with the same error on Gitlab CI. When I use cypress/base:10 and use Electron, it works fine. If I switch to cypress/browsers:chrome67 or cypress/browsers:chrome69 and run Cypress with browser set to Chrome, I get the error above all the time.

The fix will for this will be released in 3.5.0. The bug will exist in 3.4.1 as noted in this comment: https://github.com/cypress-io/cypress/issues/5110#issuecomment-530019785

We will try to release it this month, meanwhile, it is possible to patch Cypress NPM module yourself, see how https://docs.cypress.io/guides/guides/debugging.html#Patch-Cypress

@yuguangchuan

ps -ef | grep Xvfb | grep -v grep | awk '{print $2}' | xargs kill -9

it worked for me. 😃

Last time I met this issue, the root cause is that the “Xvfb” process is already running, and cypress can not start it with errors like:

It looks like this is your first time using Cypress: 3.1.0

 ✖  Verifying Cypress can run /home/mi/.cache/Cypress/3.1.0/Cypress
   → Cypress Version: 3.1.0
Your system is missing the dependency: XVFB

Install XVFB and run Cypress again.

Read our documentation on dependencies for more information:

https://on.cypress.io/required-dependencies

If you are using Docker, we provide containers with all required dependencies installed.
----------

Caught error trying to run XVFB: "XVFB exited with a non zero exit code.

There was a problem spawning Xvfb.

This is likely a problem with your system, permissions, or installation of Xvfb.
----------

Error: _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
----------

Platform: linux (Red Hat Linux - 7.4)
Cypress Version: 3.1.0"
----------

Platform: linux (Red Hat Linux - 7.4)
Cypress Version: 3.1.0

Then I checked that there’re really some running processes of Xvfb in system,

ps -ef | grep Xvfb

and after I killed them everything went well.

ps -ef | grep Xvfb | grep -v grep | awk '{print $2}' | xargs kill -9

So in my case, this is not a problem with Cypress. Hope it helps.

It seems like I just forgot to install the dependencies. It worked after installing those. https://docs.cypress.io/guides/guides/continuous-integration.html#Dependencies

This is a 5 second timeout set in https://github.com/cypress-io/cypress/blob/develop/cli/lib/exec/xvfb.js#L11 It seems like a very short and we should just increase it 30 seconds. Let me move this issue main Cypress repo so I can do the increase

It did actually - it was not correctly set to a milestone so it was missed when doing the changelog.

It was bumped up to 5 seconds… but now that I think about it, I have no idea why we wouldn’t set it to something like 30 seconds. I have seen situations where builds fail due to shutting off xvfb or starting it up.

https://github.com/cypress-io/cypress/blob/97e3092300e4487e9db01ad33d0ebb0acee7b4f2/cli/lib/exec/xvfb.js#L10

Yes, we are increasing the default xvfb start time out from 2 seconds to 5 seconds in cypress 3.0.0

Sent from my iPhone

On Apr 26, 2018, at 18:55, David Celis notifications@github.com wrote:

Sorry to bug you again, but these Xvfb errors are becoming even more frequent on our CI… Have you tried the timeout increase yet with any success?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

@AveVlad Sorry, but that seems unrelated to the problem reported in this issue, which is Xvfb failing to start in the first place when using the docker image.

If we can have exact dockerfile, setup instructions and the minimal test repository, we could debug this to find which system is failing.

Sent from my iPhone

On Apr 18, 2018, at 18:53, Vlad notifications@github.com wrote:

in docker

�[0m (Tests Finished)

• Tests: 1
• Passes: 1
• Failures: 0
• Pending: 0
• Duration: 4 seconds
• Screenshots: 1
• Video Recorded: false
• Cypress Version: 2.1.0

(Screenshots)

• /www/qw/cypress/screenshots/Simple test – Login – go to login.png (1280x720) �[91mWed, 18 Apr 2018 22:41:11 GMT cypress:server:headless attempting to close the browser �[0m�[91mWed, 18 Apr 2018 22:41:11 GMT cypress:server:browsers killing browser process �[0m�[91mWed, 18 Apr 2018 22:41:35 GMT cypress:server:timers child sending timer id 3 �[0m�[91mWed, 18 Apr 2018 22:41:37 GMT cypress:server:timers child sending timer id 20 �[0m�[91mWed, 18 Apr 2018 22:41:37 GMT cypress:server:timers child sending timer id 21 �[0m�[91mWed, 18 Apr 2018 22:41:37 GMT cypress:server:timers child sending timer id 23 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 35 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 36 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 37 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 38 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 39 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 40 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 41 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 42 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 43 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 44 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 45 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 46 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 47 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 48 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 49 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 50 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 51 �[0m�[91mWed, 18 Apr 2018 22:41:38 GMT cypress:server:timers child sending timer id 52 �[0m�[91mWed, 18 Apr 2018 22:41:39 GMT cypress:server:timers child sending timer id 53 �[0m�[91mWed, 18 Apr 2018 22:41:39 GMT cypress:server:timers child sending timer id 54 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 55 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 56 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 57 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 58 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 59 �[0m�[91mWed, 18 Apr 2018 22:41:40 GMT cypress:server:timers child sending timer id 60 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 64 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 65 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 66 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 67 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 68 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 69 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 70 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 71 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 72 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 73 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 74 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 75 Wed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 76 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 77 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 78 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 79 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 80 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 82 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 83 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 84 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 85 �[0m�[91mWed, 18 Apr 2018 22:41:41 GMT cypress:server:timers child sending timer id 86 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 5 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 6 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 7 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 9 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 10 �[0m�[91mWed, 18 Apr 2018 22:42:31 GMT cypress:server:timers child sending timer id 11 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 12 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 13 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 14 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 15 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 16 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 17 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 18 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 19 �[0m�[91mWed, 18 Apr 2018 22:42:32 GMT cypress:server:timers child sending timer id 22 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 24 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 25 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 26 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 28 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 29 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 30 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 31 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 32 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 33 �[0m�[91mWed, 18 Apr 2018 22:42:33 GMT cypress:server:timers child sending timer id 34 �[0m�[91mWed, 18 Apr 2018 22:42:35 GMT cypress:server:timers child sending timer id 61 �[0m�[91mWed, 18 Apr 2018 22:42:35 GMT cypress:server:timers child sending timer id 62 �[0m�[91mWed, 18 Apr 2018 22:42:35 GMT cypress:server:timers child sending timer id 63 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 81 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 87 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 88 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 89 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 90 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 91 �[0m�[91mWed, 18 Apr 2018 22:42:36 GMT cypress:server:timers child sending timer id 92 �[0m�[91m2018-04-18T22:42:36.939Z cypress:cli Stopping XVFB �[0m2018-04-18T22:42:36.951Z result simple { “failures”: null, “message”: “Could not find Cypress test run results” } — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Interesting, and we see this randomly on TravisCI when using Docker - XVFB not being detected, but restarting the build solves it. I wonder if increasing the timeout when passed as an option to https://github.com/cypress-io/xvfb/blob/master/index.js would solve this problem. This is so transient that we did not look into this, but seems different CIs can encounter it