HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
flatpak
xdg-desktop-portal-gtk
C2020–2025
flatpak / xdg-desktop-portal-gtk

xdg-desktop-portal-gtk

Gtk implementation of xdg-desktop-portal

6Distinct people
6Mentions
0Explicit recommenders
173GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Gtk implementation of xdg-desktop-portal

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year6 dated mentions

Observed mentions: 2020-01-29 13:25:48 UTC to 2025-10-26 02:17:23 UTC.

0122020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC202
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

6 sources
Meh, Linux Mint has some serious rough edges from my experience. Suspend doesn’t work if multiple users are logged in, save-as dialog windows open under the current window (a 7-year old bug!!!) [0], audio devices are not shared between users, some drives don't mount on boot, etc. These problems are probably fixable if you have the know-how but it isn't great for the tech illiterate. That being said, I have never had kernel panics or opened my computer to find a corrupted OS after a bad update (unlike Windows), so there's that. [0] https://github.com/flatpak/xdg-desktop-portal-gtk/issues/137
In I'm drowning in AI features I never asked for and I hate it
Even stuff such as OBS Studio was significantly slower on Wayland than on X11, at least until the efforts done _last year_ (e.g. https://feaneron.com/2021/03/30/obs-studio-on-wayland/ ) . Single-Window support for screencast API is also only a couple years old! Before that it would just error out, even if the D-Bus interface was there ( https://github.com/flatpak/xdg-desktop-portal-gtk/blob/b2b5e... ). That's why I say that it just moves way too fast for the glacial speed that commercial houses normally have. For at least 2 years (thinking 2016-2018) some distros were even shipping Wayland _without_ an actual working screen capture API. How do you even support those ?
In How Not to Support Desktop GNU+Linux, Zoom Edition
>the GTK filepicker would have to return read access to a file, rather than a filepath which a program than asks to open read-only. xdg-desktop-portal [1] does something pretty close, and it is how Linux applications shipped as Flatpaks access your files (at least when the Flatpak sandbox is in enforcing mode). Every sandboxed program has its own mount namespace which cannot see your home folder. When you want to open a file in a sandboxed program, you select the file in an out-of-process file chooser, and the portal puts a handle to that file in the program's view of the filesystem. [1] https://github.com/flatpak/xdg-desktop-portal-gtk/
In macOS Nix setup: an alternative to Homebrew (2020)
If you're running a modern Linux desktop you're probably running Wayland, and screencasts on that have long since been a complete pain in the neck with per-compositor "solutions" that mostly don't work quite right. Fortunately someone who works on Gnome wrote the obs-xdg-portal plugin that should fix this, at least for Gnome and hopefully soon for wlroots and KDE once they fully support the underlying portal API. Until then, the easiest way to get screencasting working is just to run in X11. (Ask me about ffmpeg raw GPU buffer capture one day; running a bunch of codec code as root is always exciting.) OBS Plugin: https://gitlab.gnome.org/feaneron/obs-xdg-portal/ For GTK: https://github.com/flatpak/xdg-desktop-portal-gtk For KDE: https://github.com/KDE/xdg-desktop-portal-kde For wlr: https://github.com/emersion/xdg-desktop-portal-wlr
In OBS Studio: Open-source software for video recording and live streaming
TL;DR: make sure you have pipewire and xdg-desktop-portal installed, look up how to enable pipewire for your browser. It might help. Well, this blog post barely scratches the surface. The Linux userspace display stack is currently undergoing a big overhaul, following the changes that happened in the kernel a few years ago (DRI3, KMS, atomic modesetting, etc). All of this made Wayland possible. That, plus the fact that apps rasterize their surfaces themselves nowadays (GPU-accelerated trough OpenGL/Vulkan). So, here comes Wayland with a new security model: you can't spy on other windows, so you cannot hack together a desktop sharing solution. A proper, cross-desktop solution is actually being worked on: pipewire[1]. Pipewire aims to replace both pulseaudio and jack for audio, and bring video in as well. So you will be able to direct which
Read the rest
video feed goes where, use the same webcam for multiple applications, and have applications take a video feed, transform it, and plug it elsewhere. You can see where this is fitting with desktop sharing: one feed per window, one feed per screen, one feed for the whole desktop, plus variants. Want to overlay a webcam? No problem. Everything is backed by Gstreamer for realtime hardware-accelerated video encoding/decoding. And the icing on the cake: Flatpak spearheaded the development of "portals"[2]: cross-desktop interfaces for individual programs to ask the user when accessing restricted resources (like a microphone, or a folder on your computer). So, what's needed here is: * Finish up pipewire and have it shipped on most distributions (should be installed in fedora 31, optional for sound in 32, default for sound in 33) * Have compositors talk to pipewire [3] * Have browsers and other software talk to pipewire [4] * ??? * Profit Good progress is being made on these points, except maybe the last? I expect support to start working out-of-the-box in some distros/browser/compositor combinations in 2020. Actually, support seems further along than I thought it was. But it seems that wlroots-based compositor haven't yet decided to support the xdg screensharing portal, and rely instead on a custom wayland extension. I wouldn't be surprised if such a portal is implemented for those. The main issue here is everyone waiting on everyone else before enabling/implementing it. But it looks like we're 80% there, and it just needs to be enabled in some cases (and pipewire installed). Then it will trickle down to most distros and electrons apps. However, I don't think legacy X apps will be able to continue sharing the desktop (they can still be shared by wayland capture programs, or capture the desktop if they implement the new interface). I guess pipewire might be able to create a virtual webcam for these, though. Valve might be working on their own stack with their "Gamescope" wayland compositor[5], for their streaming solution. And in the end, this should work much better, with hardware encoding, actual security, zero copy, etc. Hopefully there won't be a "next big thing" that breaks everything in just a few years. [1] https://pipewire.org/ [1] https://wiki.archlinux.org/index.php/PipeWire [2] https://flatpak.github.io/xdg-desktop-portal/portal-docs.htm... [2] https://flatpak.github.io/xdg-desktop-portal/portal-docs.htm... [3] http://jgrulich.cz/2018/03/06/screen-sharing-in-plasma-wayla... [3] https://jgrulich.cz/2018/07/04/how-to-enable-and-use-screen-... [3] https://wiki.gnome.org/Projects/Mutter/RemoteDesktop [3] https://www.reddit.com/r/linux/comments/8le7rm/first_steps_f... [3] https://github.com/emersion/xdg-desktop-portal-wlr/issues/1 [4] https://bugzilla.mozilla.org/show_bug.cgi?id=1496359 (looks disabled by default at compile time) [4] https://bugs.chromium.org/p/chromium/issues/detail?id=682122 (pipewire disabled in chrome://flags until v81 due to waiting on https://github.com/flatpak/xdg-desktop-portal-gtk/issues/204 "dialog hell" it seems) [4] zoom currently uses a gnome-specific screenshot API as a workaround: https://www.reddit.com/r/swaywm/comments/dr8yld/zoom_screens... [5] https://www.gamingonlinux.com/articles/valve-give-a-little-m...
In The sad state of screen sharing on desktop Linux

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.