Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • X xdg-desktop-portal-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • xdg-desktop-portal-gnome
  • Issues
  • #74

xdg-desktop-portal-gnome 44 causes delays in non-GNOME desktops

Test Case

  • Install xdg-desktop-portal-gnome 44.beta (I believe 44.rc isn't any different)
  • Log out, then log into a non-GNOME desktop like MATE
  • Open an app that uses portal. In my case, I used the Firefox Snap.
  • From the app, open the Open dialog

What Happens

Nothing for 2 minutes or however long the service timeout takes. After that initial timeout, the filechooser dialogs open like normal.

Other Info

This is a regression compared to xdg-desktop-portal-gnome 43.

My understanding is that xdg-desktop-portal currently attempts to load the portal backends in alphabetical order. By coincidence, this happens to do what we would expect (gnome, then gtk, kde, lxqt, wlr).

It is expected that systems with multiple desktop environments installed will have multiple portal backends installed. These backends should work in any of the desktops. (For instance, maybe MATE users want to have the GTK 4.10 icon view filechooser for their Flatpak/Snap web browser.)

I tried reporting this issue as #71 (closed) but I think this issue is now more clear about the issue.

Ideas

xdg-desktop-portal-gnome should not block while waiting for a response from a mutter service that isn't running (or might not even be installed).

If that dependency is essential, maybe there is some way we can have xdg-desktop-portal-gnome only run in GNOME sessions and fallback to another backend (xdg-desktop-portal-gtk, etc.) in non-GNOME sessions?

Edited Mar 09, 2023 by Jeremy Bicha
Assignee
Assign to
Time tracking