Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cypress won't open #22683

Closed
ewminty-private opened this issue Jul 5, 2022 · 21 comments
Closed

Cypress won't open #22683

ewminty-private opened this issue Jul 5, 2022 · 21 comments
Labels
stage: wontfix Cypress does not regard this as an issue or will not implement this feature

Comments

@ewminty-private
Copy link

ewminty-private commented Jul 5, 2022 •
edited by astone123
Loading

Current behavior

I've installed Cypress on Ubuntu 18.04 according to the instructions and the command "npx cypress open" fails with only the following information which doesn't instruct me what the problem is or what to do about it:

[8931:0705/070931.992860:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8931:0705/070931.995582:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8931:0705/070932.007952:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8931:0705/070932.011180:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[9102:0705/070934.684260:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[9102:0705/070934.716168:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[8931:0705/070939.971951:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8931:0705/070940.064300:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8931:0705/071011.886724:ERROR:network_service_instance_impl.cc(978)] Network service crashed, restarting service.

Desired behavior

It should start I assume. Never used it before.

Test code to reproduce

npx cypress open

Cypress Version

10.3.0

Other

No response
@cypress-bot cypress-bot bot added the stage: investigating Someone from Cypress is looking into this label Jul 11, 2022
@astone123
Copy link
Contributor

@ewminty-private Can you check to make sure that you've installed all of the required dependencies for Linux that are outlined in the Cypress documentation? Thanks

https://docs.cypress.io/guides/getting-started/installing-cypress#Ubuntu-Debian

@astone123 astone123 added stage: needs information Not enough info to reproduce the issue and removed stage: investigating Someone from Cypress is looking into this labels Jul 13, 2022
@cypress-bot cypress-bot bot added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: needs information Not enough info to reproduce the issue labels Jul 13, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Jul 13, 2022 via email

@cypress-bot cypress-bot bot added stage: investigating Someone from Cypress is looking into this and removed stage: awaiting response Potential fix was proposed; awaiting response labels Jul 13, 2022
@astone123
Copy link
Contributor

@ewminty-private we do have some documentation around it here.

Can you follow the steps there and let us know if that helps? Thanks

@cypress-bot cypress-bot bot added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: investigating Someone from Cypress is looking into this labels Jul 14, 2022
@nagash77 nagash77 assigned marktnoonan and unassigned astone123 Jul 19, 2022
@marktnoonan
Copy link
Contributor

Hi @ewminty-private I'm going to close this issue out since it has been a week, I'm hoping the linked docs in this comment were adequate for your setup, if not please let us know.

@ewminty-private
Copy link
Author

ewminty-private commented Jul 25, 2022 via email

@marktnoonan
Copy link
Contributor

Hi @ewminty-private, thanks for letting us know. I will reopen. None of the replies you quote appear on this issue as far as I can tell, so from our side it looked like you just stopped communicating on Jul 13. I'll see what I can find out in terms of further troubleshooting.

@marktnoonan marktnoonan reopened this Jul 25, 2022
@cypress-bot cypress-bot bot added stage: investigating Someone from Cypress is looking into this and removed stage: awaiting response Potential fix was proposed; awaiting response labels Jul 25, 2022
@marktnoonan
Copy link
Contributor

@ewminty-private I've been able to confirm that Cypress works fine in Linux generally - I tested myself (plus, we run Linux in CI). Different distros though.

I'm not able to replicate the details of your actual setup right now, but I understand that you've followed our existing docs and still not been able to get Cypress to open with WSL and X-windows.

Looking around I think that somehow the error message Missing X server or $DISPLAY from ozone_platform_x11.cc must be genuine, even though everything appears to be set up correctly. It seems to me like Cypress attempts to start the electron app, and then Electron itself errors on this. (You can see this error is coming from Chromium source code, not Cypress itself).

I saw, some mentions of this same error and (maybe?) things you could try here. I would keep debugging in that direction.

I'm going to look into whether our existing documentation needs to be updated, and confirm we can set up Cypress from scratch this way ourselves, but that may take a little while.

Some other things I'd be curious about:

  • What happens when you echo $DISPLAY right before you run npx cypress open
  • Could you run DEBUG=cypress:* cypress open and share the logs?

@cypress-bot cypress-bot bot added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: investigating Someone from Cypress is looking into this labels Jul 27, 2022
@marktnoonan
Copy link
Contributor

One other suggestion, which seems to run counter to our docs, is #4034 (comment)

Work around is to unset DISPLAY prior to cypress run

This appears to solve a slightly different problem than yours, but I thought was interesting to see when searching around, and would be curious if this makes any difference.

@ewminty-private
Copy link
Author

ewminty-private commented Jul 27, 2022 via email

@cypress-bot cypress-bot bot added stage: investigating Someone from Cypress is looking into this and removed stage: awaiting response Potential fix was proposed; awaiting response labels Jul 28, 2022
@marktnoonan
Copy link
Contributor

@ewminty-private some more detailed info about printing debug logs is here.

In your case since you are running via npx I think the following should get you the logs: DEBUG=cypress:* npx cypress open

@cypress-bot cypress-bot bot added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: investigating Someone from Cypress is looking into this labels Jul 29, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Jul 29, 2022 via email

@cypress-bot cypress-bot bot added stage: investigating Someone from Cypress is looking into this and removed stage: awaiting response Potential fix was proposed; awaiting response labels Aug 2, 2022
@marktnoonan
Copy link
Contributor

@ewminty-private from the logs I see:

cypress:cli DISPLAY environment variable is set to 64.59.144.17:0.0 on Linux
  cypress:cli Assuming this DISPLAY points at working X11 server,
  cypress:cli Cypress will not spawn own Xvfb
  cypress:cli
  cypress:cli NOTE: if the X11 server is NOT working, Cypress will exit without explanation,
  cypress:cli   see [#4034](https://github.com/cypress-io/cypress/issues/4034)
  cypress:cli Solution: Unset the DISPLAY variable and try again:
  cypress:cli   DISPLAY= npx cypress run ... +0ms

Have you tried this DISPLAY= npx cypress open

unset DISPLAY doesn't help but it was worth a shot I suppose.

I'm not sure exactly how you did this, if it was more global it might have had other problematic side effects.

@cypress-bot cypress-bot bot added stage: awaiting response Potential fix was proposed; awaiting response and removed stage: investigating Someone from Cypress is looking into this labels Aug 2, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Aug 3, 2022 via email •
edited by AtofStryker
Loading

@cypress-bot cypress-bot bot added stage: investigating Someone from Cypress is looking into this and removed stage: awaiting response Potential fix was proposed; awaiting response labels Aug 5, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Aug 8, 2022 via email

@nagash77
Copy link
Contributor

@ewminty-private At this point we don't plan to offer official support for WSL. Can you help us understand why you want to use WSL vs our windows binary? That might help us make a better case to internal product managers as to why as a company we should invest more resources in this type of use case. I am going to close this issue for the time being while we await your response.

@nagash77 nagash77 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 25, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Aug 25, 2022 via email

@katia-demagkou
Copy link

Hey , after a lot of sweat and effort i have managed to open cypress twice. Although, no matter if it works, it didnt work for a long time. Anyone getting closer to the solution of this problem?

@nagash77 nagash77 added stage: wontfix Cypress does not regard this as an issue or will not implement this feature and removed stage: investigating Someone from Cypress is looking into this labels Sep 12, 2022
@ewminty-private
Copy link
Author

ewminty-private commented Oct 11, 2022 via email

@ewminty-private
Copy link
Author

ewminty-private commented Oct 11, 2022 via email

@nagash77
Copy link
Contributor

@ewminty-private I'm sorry to hear you are still having problems. Are your latest problems still related to the initial problem listed in the ticket using WSL? If not, I would suggest opening a new issue to track the current problem rather than append to an unrelated issue.

@ewminty-private
Copy link
Author

ewminty-private commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stage: wontfix Cypress does not regard this as an issue or will not implement this feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@nagash77 @marktnoonan @mike-plummer @astone123 @rockindahizzy @ewminty-private @katia-demagkou