After installing a new version of the system (Ubuntu), I debugged the problem of firing Cypress (white screen on very early cypress loading stage) for about two weeks. Starting from Docker networking issues, to a GPU hardware acceleration problem, to a Linux switch from X server to Wayland. I believe this issue will finally be resolved by the Cypress team. However, for those who have reached this place - the temporary solution is to disable Wayland. To do this, uncomment the line #WaylandEnable=false in the /etc/gdm3/custom.conf file and reboot the machine.

Can you elaborate a bit what pieces are missing?
We have a custom build of chromium here, running with wayland on arm64. It would be nice if we could point cypress to use this browser.

I've tried to start it like this: cypress run --browser /usr/bin/chromium --headed --config-file ./cypress/config/test.config.ts.
I've patched the cli to skip the verify process. But now it seems to hang inside of /root/.cache/Cypress/10.7.0/Cypress/Cypress --no-sandbox -- --run-project /home/testuser --headed --browser /usr/bin/chromium. I suspect this is the electron starter app that doesn't work with Wayland yet.
Is there a way to skip the electron starter app and directly launch the browser in question?

if it's chromium, using the --ozone-platform=wayland should do the trick. You can specify that as a flag, or put it into your ~/.config/chrome-flags.conf file.

When starting cypress, the initial testing-types-runner window also launches under Xwayland since it's an Electron app. So, if testing with Firefox, running xlsclients lists both 'Cypress' and 'firefox'; this is the problem that this issue is really about, since it should not be necessary to use Xwayland for any runner/browser combo at this point in time.

When cypress launches, it ends up spawning a binary and passes arguments to it, some of those arguments are for Electron. So the fix for this issue can be made with one line, which will stop both the runner and browser from launching under Xwayland, and maybe fix all browsers. In the lib/exec/spawn.js file, an addition of the --ozone-platform=wayland option to the Electron args seems to work. At around line 109, change this:

        const electronArgs = [];

To this:

        const electronArgs = ['--ozone-platform=wayland'];

With this change xlsclients does not list any Cypress process, and the browsers are also launched correctly under Wayland. Maybe this can probably be done with config files too, but I didn't look in to that.

Edit: changed where to add flag for simplicity.

The right flag actually might be this: --ozone-platform-hint=auto ¹ - that would probably account for folks using X and Wayland together. I'm honestly not sure why it isn't the default in chromium

I tested --ozone-platform-hint=auto with Cypress 13.7, i.e. added const electronArgs = ['--ozone-platform-hint=auto']; to lib/exec/spawn.js:109, and it works for the runner and browser as well, so is a likely a better solution.