ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read #28061

MikeMcC399 · 2023-10-15T12:44:55Z

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.js 20.8.0
CircleCI Ubuntu 22.04 in Docker / Node.js 20.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

see also Message "DevTools listening on ws://127.0.0.1" #26753

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.0 showed (see also ERROR:gpu_memory_buffer_support_x11 on GitHub Ubuntu #25357):

[443:1014/182211.580014:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Cypress 13.2.0 and 13.3.0 were free from ERROR codes on starting
Cypress 13.3.1 -> 13.6.0 show:

[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:

The text was updated successfully, but these errors were encountered:

csvan · 2023-10-31T21:31:34Z

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).

DmytroKhomychPrintify · 2023-11-01T10:34:06Z

Having same for Cypress 13.3.1 in CI, but no errors on OSX

MikeMcC399 · 2023-11-01T11:09:51Z

@csvan / @DmytroKhomychPrintify

I only see this error message in CI and this is where Cypress uses Xvfb (X virtual framebuffer) in place of a physical graphic hardware adapter.

MikeMcC399 · 2023-11-01T11:14:44Z

If it can be determined that the error message in this issue is harmless:

[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:

perhaps it could be added to the list of "garbage warnings" in

https://github.com/cypress-io/cypress/blob/develop/cli/lib/exec/spawn.js

and which are filtered out by that module?

pythonquick · 2023-11-13T02:28:20Z

Seeing the same error when running Cypress 13.4.0 in CI

jerrychong25 · 2023-11-15T03:21:31Z

Having same error when running Cypress 12.17.4 in Jenkins:

Opening Cypress...
[493:1115/040124.736155:ERROR:zygote_host_impl_linux.cc(273)] Failed to adjust OOM score of renderer with pid 646: Permission denied (13)
[493:1115/040124.746972:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

AlexanderTunick · 2023-11-20T07:49:13Z

Confirming the same error after upgrading to Cypress v13.5.1.
Docker in Jenkins CI on Ubuntu 16.04

ci
NODE_PATH=./cypress cypress run --env cfg=dev --record --group Adm --browser chrome --spec cypress/e2e/adm/**

[1356:1120/040141.013878:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: 

DevTools listening on ws://127.0.0.1:43273/devtools/browser/5d984b5a-2049-4d52-93b4-95d4dc152e26

jerrychong25 · 2023-11-20T16:07:32Z

Anyone found the solution?

Priyanka21manohar · 2023-11-21T04:51:14Z

Anyone found the solution?

Try running the build with ubuntu-latest
name: Cypress Regression
runs-on: ubuntu-latest

GarethCake · 2023-11-21T04:54:49Z

Anyone found the solution?

Try running the build with ubuntu-latest name: Cypress Regression runs-on: ubuntu-latest

Am currently running on ubuntu-latest and still having this problem :(

akshaygupta5233 · 2023-11-21T11:23:58Z

Kindly get this issue fixed. I am so badly stuck

csvan · 2023-11-21T13:11:55Z

Can people with this issue confirm it actually BREAKS something? I am getting it but the tests are still passing as usual.

Priyanka21manohar · 2023-11-22T06:27:41Z

Anyone found the solution?

Try running the build with ubuntu-latest name: Cypress Regression runs-on: ubuntu-latest

Am currently running on ubuntu-latest and still having this problem :(

Are you stuck with that error or it proceed with the Cypress test along with this error?
I didn't face the issue after updating all the runs-on: ubuntu-latest in the YAML file.

GarethCake · 2023-11-22T06:30:39Z

Anyone found the solution?

Try running the build with ubuntu-latest name: Cypress Regression runs-on: ubuntu-latest

Am currently running on ubuntu-latest and still having this problem :(

Are you stuck with that error or it proceed with the Cypress test along with this error? I didn't face the issue after updating all the runs-on: ubuntu-latest in the YAML file.

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.

MikeMcC399 · 2023-11-22T07:22:02Z

Going by previous similar messages, the message

ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read

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.

cimak · 2023-11-24T12:21:13Z

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.

MikeMcC399 · 2023-11-25T09:19:19Z

@cimak

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.

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
- GitHub: Windows Subsystem for Linux GUI
- Microsoft Learn: Run Linux GUI apps on the Windows Subsystem for Linux
Existing WSL installations can be updated to use WSLg. New WSL installations automatically use WSLg.
See Windows Subsystem for Linux (WSL2) information does not cover WSLg cypress-documentation#5353).
Note that according to Command was killed with SIGSEGV (Segmentation fault) #27858 (comment) Cypress does not currently support WSL2. See also WSL/WSL2 installation documented although unsupported cypress-documentation#5489.

ivy-tian · 2023-11-27T03:42:25Z

Is there a solution to this issue? I'm currently stuck here. The Cypress task runs fine locally, but it encounters this error and fails on the CI.

We are running e2e tests on a self-hosted VM. Is there a way to avoid the issue "when it uses Xvfb (X virtual framebuffer) because there is no other X11 server available due to missing hardware graphics"

RamyTalal · 2023-11-27T15:25:39Z

I'm also having this issue on Bitbucket.

[1541:1127/150440.272221:ERROR:zygote_host_impl_linux.cc(273)] Failed to adjust OOM score of renderer with pid 1695: Permission denied (13)

[1541:1127/150440.286074:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

danielkoch · 2023-11-27T16:01:57Z

Same issue on GitLab pipeline.

jennifer-shehane · 2023-11-27T18:58:55Z

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)

MikeMcC399 · 2023-11-27T22:15:55Z

(This is happening in Firefox and Chrome, so not related to our Chrome manifest v3 upgrade)

It is also reproducible testing against Electron, see

https://github.com/cypress-io/github-action/actions/runs/7000454887/job/19041127272

DevTools listening on ws://127.0.0.1:44767/devtools/browser/65199945-2077-4288-8d52-191948370bd7
[1934:1127/040432.303024:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: 

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        13.6.0                                                                         │
  │ Browser:        Electron 114 (headless)                                                        │
  │ Node Version:   v20.8.1 (/home/runner/runners/2.311.0/externals/node20/bin/node)               │
  │ Specs:          1 found (spec.cy.js)                                                           │
  │ Searched:       cypress/e2e/**/*.cy.{js,jsx,ts,tsx}                                            │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

sbednarzlf · 2023-11-29T18:28:54Z

Hi,
I have the same problem with Cypress 13.6 on Node v21.2.0. Tests run in the Azure DevOps pipeline.

npx cypress run --browser chrome
DevTools listening on ws://127.0.0.1:33525/devtools/browser/b25c722e-2087-4f49-b712-48cfb3fcdd2f
[1850380:1129/142614.557483:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

gunslingor · 2023-11-29T21:33:47Z

Same Problem... latest version

gunslingor · 2023-11-29T22:07:19Z

I can confirm, this error breaks google cloudbuild when it is initiated via a google cloud bitbucket trigger, however it does not seem to break it when I initiate the build locally.

Here is the difference:

LOCAL CMD: gcloud builds submit --region=us-west2 --config cloudbuild.yaml

REMOTE TRIGGERED:

konrad-szczepaniak-esky · 2023-12-01T11:26:33Z

It also occurs on Github Actions with node 18 and Cypress 13.5.1, 13.6.0

4nderss · 2023-12-01T14:55:52Z

Breaks our azure pipelines builds which run tests inside Docker.

[233:1201/144811.571742:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type: 

DevTools listening on ws://127.0.0.1:35031/devtools/browser/9c4a8df9-1afc-4bc7-89b0-acb838db4e32

    at ChildProcess.exithandler (node:child_process:419:12)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:489:12)
    at maybeClose (node:internal/child_process:1091:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: 'docker run -e CYPRESS_SPEC="xx.cy.ts" -v /home/vsts/work/1/s/cypress:/e2e/cypress cypress-base:1.0.0 cypress:run:spec'
}

Can't upgrade past 13.2 or this blocks our build.

rajishanmugi · 2023-12-27T09:03:07Z

I am trying to run cypress tests. It is all running fine in my local. But in github actions execution, the web page is not loading. I tried adding below.

chromewebsecurity as false
testIsolation false
retries with 2
changed my cypress version to be 13.3.0
My node version is v20.10.0
System Platform: linux (Debian - 11.5)

[Am getting a blank page on cy.visit(baseUrl) ]

MikeMcC399 · 2024-01-12T11:35:19Z

@rajishanmugi

The problem you are describing is not the one in this issue.

jennifer-shehane · 2024-01-12T15:50:30Z

Looking at the examples provided and the error messages provided - this message is not causing runs to fail. There is some other cause that the run is failing, where this happens to be the error message before it. Even some of the stack traces provided here prove that the error is coming from another source. Please read your terminal errors carefully and run the run in debug mode mode to print the set of logs to see where the failure is.

What we will likely end up doing is parsing out this message and suppressing it from the Terminal output (as we have done before) in order to correctly direct users to the true reason their builds are failing/hanging. The long term fix will take time to update Electron.

We're open to PRs to suppress the message.

ojemuyiwa · 2024-01-12T21:31:32Z

"@cypress/code-coverage" is the underlying issue

MikeMcC399 · 2024-01-14T10:44:12Z

@ojemuyiwa

"@cypress/code-coverage" is the underlying issue

That may be true for you, however it is not necessarily the case for other users, including myself. I am not using @cypress/code-coverage.

noshiro-pf · 2024-01-15T09:22:06Z

~~Seeing the same error when running Cypress 13.6.2 on Github Actions and on WSL (cypress open, cypress run).~~

DevTools listening on ws://127.0.0.1:36551/devtools/browser/db3972a0-fbb9-4e6a-9fe0-4692cf1abf05
[8956:0115/181526.210849:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^
TypeError [Error]: value.replace is not a function
    at normalizeSlashes (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/util.js:62:18)
    at Object.getExtendsConfigPath (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/ts-internals.js:24:54)
    at readConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:127:64)
    at findAndReadConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:50:84)
    at create (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:146:69)
    at register (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:127:19)
    at Object.registerAndCreateEsmHooks (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/esm.js:25:49)
    at file:///home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/esm/transpile-only.mjs:8:7
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)

Node.js v20.11.0

MikeMcC399 · 2024-01-15T09:28:36Z

@noshiro-pf

It's very likely that the message

[8956:0115/181526.210849:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

is not related to the following error:

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^
TypeError [Error]: value.replace is not a function
    at normalizeSlashes (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/util.js:62:18)
    at Object.getExtendsConfigPath (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/ts-internals.js:24:54)
    at readConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:127:64)
    at findAndReadConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:50:84)
    at create (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:146:69)
    at register (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:127:19)
    at Object.registerAndCreateEsmHooks (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/esm.js:25:49)
    at file:///home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/esm/transpile-only.mjs:8:7
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)

ojemuyiwa · 2024-01-15T10:24:19Z

@noshiro-pf

It's very likely that the message

[8956:0115/181526.210849:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

is not related to the following error:

node:internal/process/esm_loader:34
      internalBinding('errors').triggerUncaughtException(
                                ^
TypeError [Error]: value.replace is not a function
    at normalizeSlashes (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/util.js:62:18)
    at Object.getExtendsConfigPath (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/ts-internals.js:24:54)
    at readConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:127:64)
    at findAndReadConfig (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/configuration.js:50:84)
    at create (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:146:69)
    at register (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/index.js:127:19)
    at Object.registerAndCreateEsmHooks (/home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/dist/esm.js:25:49)
    at file:///home/xxx/.cache/Cypress/13.6.2/Cypress/resources/app/node_modules/ts-node/esm/transpile-only.mjs:8:7
    at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)

Yeah seems like esm module loader error. value.replace seems like a string replace is trying to take place internally and failing.

noshiro-pf · 2024-01-15T11:35:53Z

@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: #27466

StruckCroissant · 2024-01-28T02:56:38Z

I'm currently getting this error on Cypress 13.6.3. I also have @Cypress/code-coverage version 3.12.19. Running locally is fine, but when running the CI it throws the error and appears to prevent coverage from being generated.

> vite preview
  ➜  Local:   http://localhost:4173/
  ➜  Network: use --host to expose
DevTools listening on ws://127.0.0.1:46263/devtools/browser/b88c3106-a5c2-4937-b0c4-1a0cf9d52cc6
[2058:0128/024517.177506:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

MikeMcC399 · 2024-01-28T11:14:25Z

@StruckCroissant

I'm currently getting this error on Cypress 13.6.3. I also have @Cypress/code-coverage version 3.12.19. Running locally is fine, but when running the CI it throws the error and appears to prevent coverage from being generated.

DevTools listening on ws://127.0.0.1:46263/devtools/browser/b88c3106-a5c2-4937-b0c4-1a0cf9d52cc6
[2058:0128/024517.177506:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: unknown error type:

It's very unlikely that your problem with @cypress/code-coverage is stopping this from working. All the CircleCI workflows on https://app.circleci.com/pipelines/github/cypress-io/code-coverage?branch=master for @cypress/code-coverage succeed even though they also show the message ERROR:object_proxy.cc.

StruckCroissant · 2024-01-28T20:31:44Z

@MikeMcC399
It's very unlikely that your problem with @cypress/code-coverage is stopping this from working. All the CircleCI workflows on https://app.circleci.com/pipelines/github/cypress-io/code-coverage?branch=master for @cypress/code-coverage succeed even though they also show the message ERROR:object_proxy.cc.

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 👍

CT4nk3r · 2024-02-07T11:48:09Z

Still seems to be an issue on 13.6.4, azure vm with ubuntu-latest. Still not something that breaks, but looks really out of place when you are just trying to figure out what the issue is with something.

MikeMcC399 · 2024-02-07T11:55:32Z

@CT4nk3r

Still seems to be an issue on 13.6.4, azure vm with ubuntu-latest. Still not something that breaks, but looks really out of place when you are just trying to figure out what the issue is with something.

Thanks for your cross-check! I had already updated the original post to include Cypress 13.6.4. The number of replies in this thread indicates that it is an on-going annoyance and distraction.

#28061 (comment) said that they are open to PRs to suppress the message. Nobody has come forward so far and the Cypress.io team hasn't actively pick it up either, so the error message remains.

niklasscharfy · 2024-02-14T16:59:12Z

still annoying

harshitBhardwaj97 · 2024-02-17T13:01:15Z

I am also facing a similar issue, I am trying to build a ci/cd pipeline, in which I also have added step to run e2e tests with cypress.

I am not using typescript for this project, and the tests are passing on my local machine (although there also I am getting this warning, but still tests are passing).

For the reference, this is my pipeline.yml file, in which I have also tried using ubuntu-latest -

name: Deployment pipeline

on:
  push:
    branches:
      - main

jobs:
  simple_deployment_pipeline:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: "20"
      - name: Install dependencies
        run: npm install
      - name: Check style
        run: npm run eslint
      - name: Build the app
        run: npm run build
      - name: Run tests
        run: npm run test
      - name: e2e tests
        uses: cypress-io/github-action@v5
        with:
          command: npm run test:e2e
          start: npm run start-prod
          wait-on: http://localhost:5000

The workflow just gets stuck after the error shown in first screenshot, and I have to cancel it, if someone is having any idea how to solve it then kindly respond.

For the complete code, refer this - https://github.com/harshitBhardwaj97/Full-Stack-Open-Pokedex-CICD

MikeMcC399 · 2024-02-17T13:23:57Z

@harshitBhardwaj97

Your problems are not due to the message

ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read

I suggest you remove the line

command: npm run test:e2e

and the action will automatically run your tests.
Since this is not a product bug, but a workflow error, this issue list is not the right place to request assistance.

You can get support from the Cypress technical community on Discord

(click on button)

Also, you should probably be using the current action version cypress-io/github-action@v6

harshitBhardwaj97 · 2024-02-17T15:11:06Z

Thanks a ton @MikeMcC399, kindly excuse if I asked a very basic question, I am self taught aspiring engineer, and I was following the instructions that were told to me. Once again thanks, now the CI pipeline is executing e2e tests as well -

So I guess the key takeaway here is, that cypress-io/github-action@v6 internally is responsible executing the tests.

MikeMcC399 · 2024-02-17T15:26:14Z

@harshitBhardwaj97

Your problem was that you were trying to run Cypress in open (interactive) mode through
"test:e2e": "cypress open"
so the workflow was waiting for user input and could not progress.

MikeMcC399 · 2024-03-02T18:24:58Z

This issue no longer occurs after updating to cypress@13.3.5 (released Feb 20, 204).

It seems that PR chore(dependency): Upgrade Electron 27 #28792 provided the resolution.

csvan · 2024-03-03T13:20:42Z

Confirming that we can no longer reproduce this on Cypress 13.6.6 in CI

jennifer-shehane · 2024-03-04T14:30:47Z

@MikeMcC399 Oh, interesting. I must have missed a backport of this because I thought it was only in Electron 28. Great!!

MikeMcC399 · 2024-03-04T14:52:10Z

@jennifer-shehane

Oh, interesting. I must have missed a backport of this because I thought it was only in Electron 28. Great!!

I was not able to find any reference to this issue on https://github.com/electron/electron and so I can't name any relevant Electron PR. If you happen to know which PR might have been responsible, you're welcome to add a reference to it here. If not, don't worry!

mlaw93 · 2024-03-13T13:04:43Z

@rajishanmugi

I am trying to run cypress tests. It is all running fine in my local. But in github actions execution, the web page is not loading. I tried adding below.

chromewebsecurity as false

testIsolation false

retries with 2

changed my cypress version to be 13.3.0

My node version is v20.10.0

System Platform: linux (Debian - 11.5)

[Am getting a blank page on cy.visit(baseUrl) ]

Did you ever resolve this issue?

jennifer-shehane added stage: needs investigating Someone from Cypress needs to look at this type: error message labels Oct 16, 2023

jennifer-shehane added the v13.3.1 🐛 label Nov 27, 2023

jennifer-shehane mentioned this issue Feb 9, 2024

ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.portal.Settings.Read: object_path= /org/freedesktop/portal/desktop: org.freedesktop.portal.Error.NotFound: Requested setting not found #28907

Closed

CamilleDrapier mentioned this issue Feb 16, 2024

Add unzip to factory cypress-io/cypress-docker-images#1015

Merged

jennifer-shehane mentioned this issue Feb 26, 2024

chore(dependency): Upgrade Electron 28 #28959

Open

3 tasks

MikeMcC399 closed this as completed Mar 2, 2024

jennifer-shehane removed the stage: needs investigating Someone from Cypress needs to look at this label Mar 4, 2024

MikeMcC399 mentioned this issue Mar 15, 2024

Warning: vkCreateInstance: Found no drivers! warning shown when running Cypress #29085

Closed

ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read #28061

ERROR:object_proxy.cc(590) Failed to call method: org.freedesktop.portal.Settings.Read #28061

Comments

MikeMcC399 commented Oct 15, 2023 • edited Loading

Current behavior

Desired behavior

Test code to reproduce

Cypress Version

Node version

Operating System

Debug Logs

Other

Error history

csvan commented Oct 31, 2023 • edited Loading

DmytroKhomychPrintify commented Nov 1, 2023

MikeMcC399 commented Nov 1, 2023

MikeMcC399 commented Nov 1, 2023

pythonquick commented Nov 13, 2023

jerrychong25 commented Nov 15, 2023 • edited Loading

AlexanderTunick commented Nov 20, 2023

jerrychong25 commented Nov 20, 2023

Priyanka21manohar commented Nov 21, 2023

GarethCake commented Nov 21, 2023

akshaygupta5233 commented Nov 21, 2023

csvan commented Nov 21, 2023

Priyanka21manohar commented Nov 22, 2023

GarethCake commented Nov 22, 2023

MikeMcC399 commented Nov 22, 2023

cimak commented Nov 24, 2023 • edited Loading

MikeMcC399 commented Nov 25, 2023

ivy-tian commented Nov 27, 2023

RamyTalal commented Nov 27, 2023 • edited Loading

danielkoch commented Nov 27, 2023

jennifer-shehane commented Nov 27, 2023 • edited Loading

MikeMcC399 commented Nov 27, 2023

sbednarzlf commented Nov 29, 2023

gunslingor commented Nov 29, 2023

gunslingor commented Nov 29, 2023

konrad-szczepaniak-esky commented Dec 1, 2023

4nderss commented Dec 1, 2023 • edited Loading

rajishanmugi commented Dec 27, 2023

MikeMcC399 commented Jan 12, 2024

jennifer-shehane commented Jan 12, 2024

ojemuyiwa commented Jan 12, 2024

MikeMcC399 commented Jan 14, 2024

noshiro-pf commented Jan 15, 2024 • edited Loading

MikeMcC399 commented Jan 15, 2024

ojemuyiwa commented Jan 15, 2024

noshiro-pf commented Jan 15, 2024

StruckCroissant commented Jan 28, 2024

MikeMcC399 commented Jan 28, 2024

StruckCroissant commented Jan 28, 2024

CT4nk3r commented Feb 7, 2024

MikeMcC399 commented Feb 7, 2024

niklasscharfy commented Feb 14, 2024

harshitBhardwaj97 commented Feb 17, 2024

MikeMcC399 commented Feb 17, 2024 • edited Loading

harshitBhardwaj97 commented Feb 17, 2024

MikeMcC399 commented Feb 17, 2024

MikeMcC399 commented Mar 2, 2024

csvan commented Mar 3, 2024

jennifer-shehane commented Mar 4, 2024

MikeMcC399 commented Mar 4, 2024

mlaw93 commented Mar 13, 2024 • edited Loading

MikeMcC399 commented Oct 15, 2023 •

edited

Loading

csvan commented Oct 31, 2023 •

edited

Loading

jerrychong25 commented Nov 15, 2023 •

edited

Loading

cimak commented Nov 24, 2023 •

edited

Loading

RamyTalal commented Nov 27, 2023 •

edited

Loading

jennifer-shehane commented Nov 27, 2023 •

edited

Loading

4nderss commented Dec 1, 2023 •

edited

Loading

noshiro-pf commented Jan 15, 2024 •

edited

Loading

MikeMcC399 commented Feb 17, 2024 •

edited

Loading

mlaw93 commented Mar 13, 2024 •

edited

Loading