I'm in the midst of a great brawl with Wayland and OBS Studio. OBS can't seem to pick up screen/window capturing capabilities via pipewire, even though the service is running perfectly well. I think I've narrowed it down to xdg-desktop-portal(-kde?). It'll start, then after a short duration segfault. I'd like to get to the bottom of this, so I'm just going to fire off some questions and hope that at least some of them can get answered:

1. How do I properly debug a service? The best I can provide at the moment is the systemctl status log:

Code: Select all

● xdg-desktop-portal.service - Portal service
     Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static; vendor preset: ena>
     Active: failed (Result: signal) since Wed 2021-11-17 02:02:09 PST; 1s ago
    Process: 77820 ExecStart=/usr/libexec/xdg-desktop-portal (code=killed, signal=SEGV)
   Main PID: 77820 (code=killed, signal=SEGV)

Nov 17 02:01:39 murphy systemd[1423]: Starting Portal service...
Nov 17 02:01:39 murphy systemd[1423]: Started Portal service.
Nov 17 02:02:09 murphy systemd[1423]: xdg-desktop-portal.service: Main process exited, code=kille>
Nov 17 02:02:09 murphy systemd[1423]: xdg-desktop-portal.service: Failed with result 'signal'.

which isn't that much information to go off of. If someone could offer up a good resource on the best way to do it in the context of a forum post that would be awesome.

2. There's 3 xdg-desktop-portal* services.

- xdg-desktop-portal: I've narrowed this down to be maintained by Flatpak (https://github.com/flatpak/xdg-desktop-portal), and it at least plays *some* role in all of this, as it's a dependency of...
- xdg-desktop-portal-kde: Self describes itself as "A backend implementation for xdg-desktop-portal that is using Qt/KDE" (https://invent.kde.org/plasma/xdg-desktop-portal-kde/). What does that really mean though? Does it wrap the standard desktop portal provided by flatpak, or is it meant to run alongside it? If the latter, I have the package installed, and there's no service under the name of `xdg-desktop-portal-kde`
- xdg-desktop-portal-gtk: I haven't looked very far into this one, but it has a `.service` that runs alongside the Flatpak portal, unlike the KDE variant. Hence my confusion above.

3. A direct successor to question 2, which package should I report the issue to? should this go in Flatpaks tracker, or KDEs? Maybe this isn't a problem with this desktop-portal thing at all, but rather an issue with OBS. I'm running the latest version, that's meant to have support for pipewire builtin by default, but it's definitely not there.

4. I'm using the version of OBS that's installed via a .deb package. Does it still need this flatpak xdg-desktop-portal? If so that voids all the above questions and sets me back a considerable amount.

System information:

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-40-generic (64-bit)
Graphics Platform: Wayland

Package Information:

xdg-desktop-portal Version: 1.6.0-1
xdg-desktop-portal-kde Version: 5.23.3-0xneon+20.04+focal+release+build35
xdg-desktop-portal-gtk Version: 1.6.0-1build1
obs-studio Version: 27.1.3-0obsproject1~focal
pipewire Version: 0.3.33-0+20.04+focal+release+build42

Okay so it's a new day and I did a bit more testing. xdg-desktop-portal.service only breaks when obs is run. I had originally said that it crashes after a short duration which is not the case. It had been running without fault for about 90 minutes before I broke out OBS and it crashed.