cypress: ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read
Current behavior
When Cypress is run in a CI environment where there is no physical GPU available, an error message similar to the following is output:
[266:1014/183729.600834:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:
This is new in Cypress 13.3.1 and is a regression from Cypress 13.3.0.
It affects for instance:
- GitHub Actions with Ubuntu
22.04/ Node.js20.8.0 - CircleCI Ubuntu
22.04in Docker / Node.js20.6.1
The error message occurs in CI where it uses Xvfb (X virtual framebuffer) when there is no other X11 server available due to missing hardware graphic.
Desired behavior
The only message output when starting Cypress in CI should be similar to the following:
DevTools listening on ws://127.0.0.1:35223/devtools/browser/18023e84-028d-4b1e-a9d3-afb174f8232f
There should be no message with the following text output:
ERROR:object_proxy.cc
Test code to reproduce
Workflows from Cypress repos show the issue since the update to Cypress 13.3.1:
- https://github.com/cypress-io/github-action/actions/workflows/example-cron.yml
- https://github.com/cypress-io/cypress-example-kitchensink/blob/master/.github/workflows/single.yml
- https://github.com/cypress-io/cypress-docker-images/blob/master/circle.yml for example “test-image-medium-factory-test-factory-cypress-included-electron” on https://app.circleci.com/pipelines/github/cypress-io/cypress-docker-images
Cypress Version
First reported on version: 13.3.1
Reproducible also on version: 13.6.4
Node version
20.8.0 / 20.6.1
Operating System
Ubuntu 22.04
Debug Logs
| Workflow | Cypress 13.3.0 | Cypress 13.3.1 |
|---|---|---|
| GitHub Actions | Job 17616845243 | Job 17685117337 |
| CircleCI | Job 48307 | Job 48982 |
Other
Error history
- Cypress
13.0.0/13.1.0showed (see also https://github.com/cypress-io/cypress/issues/25357):
[443:1014/182211.580014:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
-
Cypress
13.2.0and13.3.0were free from ERROR codes on starting -
Cypress
13.3.1->13.6.0show:
[266:1014/183729.600834:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 62
- Comments: 60 (19 by maintainers)
Commits related to this issue
- :green_heart: Downgrade cypress to fix its error https://github.com/cypress-io/cypress/issues/28061 — committed to lebaz20/metrics by deleted user 7 months ago
- modify: downgrade cypress version to avoid https://github.com/cypress-io/cypress/issues/28061 — committed to pondersource/dev-stock by MahdiBaghbani 7 months ago
- fix: Update ci.yml implemeting this: https://github.com/cypress-io/cypress/issues/28061#issuecomment-1862612842 — committed to nerdbord/good-dev-hunting-app by szymonkadas 6 months ago
Can people with this issue confirm it actually BREAKS something? I am getting it but the tests are still passing as usual.
Having same for Cypress 13.3.1 in CI, but no errors on OSX
Try running the build with ubuntu-latest name: Cypress Regression runs-on: ubuntu-latest
Confirming that we can no longer reproduce this on Cypress 13.6.6 in CI
@noshiro-pf
It’s very likely that the message
is not related to the following error:
I would agree with @MikeMcC399 that this is likely not the cause of anyones hanging/failures, but the last message you see in the terminal before it fails in some people’s cases.
We’d need to do a git bisect to narrow down when this was introduced in 13.3.1. That would help since nothing obvious comes out as the problem looking at the changes.
(This is happening in Firefox and Chrome, so not related to our Chrome manifest v3 upgrade)
Seeing the same error when running Cypress 13.4.0 in CI
Confirming this on Cypress 13.4.0 running in CI mode on an Amazon Linux 2023 Docker image (Nodejs 18). Same code works fine on OSX (M1 Pro).
This issue no longer occurs after updating to cypress@13.3.5 (released Feb 20, 204).
@MikeMcC399 @ojemuyiwa Thank you for your advice! Sorry, my problem was that I was using an array in the tsconfig.json that cypress reads.
Related issue: https://github.com/cypress-io/cypress/issues/27466
Did that last night and you were absolutely right the first time the error is in
"@cypress/code-coverage": "^3.12.14"I downgraded to"@cypress/code-coverage": "3.12.5"and errors all gone. I believe ther error is internal maybe in istanbul-lib-coverageIt also occurs on Github Actions with node 18 and Cypress 13.5.1, 13.6.0
@cimak
You didn’t say which of the Stack Overflow solutions you used. WSLg would be the preferred one.
Windows Subsystem for Linux GUI (WSLg) provides a GUI environment for WSL2 out-of-the-box.
Installation information for WSLg is available on
Existing WSL installations can be updated to use WSLg. New WSL installations automatically use WSLg. See https://github.com/cypress-io/cypress-documentation/issues/5353).
Note that according to https://github.com/cypress-io/cypress/issues/27858#issuecomment-1729598898 Cypress does not currently support WSL2. See also https://github.com/cypress-io/cypress-documentation/issues/5489.
I was getting this exact error when running cypress under WSL2/win11. Installing XServer on windows worked for me, I’m not sure if it is a final solution but I’m leaving this here, maybe someone will find it helpful.
Having same error when running Cypress 12.17.4 in Jenkins:
You are correct. After looking into this further this issue was caused because coverage was attempting to run against a production build, while my NYC config was not set to instrument in a prod environment. Thanks for the response though 👍
@ojemuyiwa / @jerrychong25
Have you run Cypress with debug enabled in CI/CD? For instance in GitHub Actions you would set the environment variable
DEBUGwith:Maybe a fix in
cypress/browsers:node-18.16.0-chrome-114.0.5735.133-1-ff-114.0.2-edge-114.0.1823.51-1cypress recommended CI/CD images? cypress 13.6.1 works locally on mac book pro but almost every image I’ve tried has this error and fails everything thereafter i.e. coverage tasks, runners, tests etc.Same Problem… latest version
Going by previous similar messages, the message
is probably not causing test failures, HOWEVER if your test is failing, then this may be the last message you see, so it looks as though it IS the cause.
If you are seeing issues, then you should be following the Troubleshooting steps in the documentation.
I think you’re onto something as I reverted to 13.0 and still got the hanging issues. My problem is at least 1 test will hang on a white screen or a page that says “default blank page” in the test replay (seems to always be a failing test). I’ve read elsewhere it’s a problem with retries so will maybe try turning retries off for now.
Kindly get this issue fixed. I am so badly stuck
Am currently running on ubuntu-latest and still having this problem 😦
Confirming the same error after upgrading to Cypress v13.5.1. Docker in Jenkins CI on Ubuntu 16.04