Hi, For some time, I have had a problem with screen sharing/capturing in Sway. I tested it using both Firefox and Chromium with Google Meet and this test page: https://mozilla.github.io/webrtc-landing/gum_test.html. I went through the troubleshooting checklist (available here: https://github.com/emersion/xdg-desktop-portal-wlr/wiki/%22It-doesn't-work%22-Troubleshooting-Checklist) to find out that xdg-desktop-portal.service is not started. Not that it fails. It is not even being attempted. How can I make it start? Below is what I tried. I noticed that xdg-desktop-portal.service is a "PartOf" graphical-session.target, so I configured my sway.target to bind to the graphical session. The Sway target is started in the Sway configuration, which includes a slightly modified 50-systemd-user.conf available in the Arch package: --- 50-systemd-user.sh --- # Upstream refuses to set XDG_CURRENT_DESKTOP so we have to. exec systemctl --user set-environment XDG_CURRENT_DESKTOP=sway exec systemctl --user import-environment DISPLAY \ SWAYSOCK \ WAYLAND_DISPLAY \ XDG_CURRENT_DESKTOP exec hash dbus-update-activation-environment 2>/dev/null && \ dbus-update-activation-environment --systemd DISPLAY \ SWAYSOCK \ XDG_CURRENT_DESKTOP=sway \ WAYLAND_DISPLAY \ PATH exec systemctl --user start sway.target --- The sway.target is very simple: --- (~)$ cat .config/systemd/user/sway.target [Unit] Description=Sway target AllowIsolate=yes BindsTo=graphical-session.target --- This changed nothing, so I tried to start xdg-desktop-portal manually to find out that it ends with a core dump. Logs attached. Not sure if this is related to the problem that the service is not started or if it is an unrelated issue. Any advice? Thanks, Radek