Hi,
I’m on Sway with openSUSEway on Tumbleweed.
How can I figure out what this is doing wrong? It seems to slow down the whole system.
$ systemctl --user status xdg-desktop-portal-wlr
● xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal-wlr.service; static)
Active: active (running) since Thu 2023-08-03 18:44:46 CEST; 1 month 1 day ago
Main PID: 2750 (xdg-desktop-por)
Tasks: 6 (limit: 4915)
Memory: 1.6M
CPU: 5d 3h 15min 53.485s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal-wlr.service
└─2750 /usr/libexec/xdg-desktop-portal-wlr
Aug 03 18:44:46 dreamland systemd[2592]: Starting Portal service (wlroots implementation)...
Aug 03 18:44:46 dreamland systemd[2592]: Started Portal service (wlroots implementation).
Thanks for any ideas.
@crameleon Hi, I see this note:
Make sure the `XDG_CURRENT_DESKTOP` env var is set in the D-Bus user session to one of the UseIn values in wlr.portal
But the real question, is it needed, or just a recommends?
On MicroOS Hyprland/Sway I’m just using xdg-desktop-portal without issues…
This variable is set in my session (unsure if that’s available in the context xdg-desktop-portal-wlr is running in as well, but I would guess so):
$ echo $XDG_CURRENT_DESKTOP
sway
I think I require this portal service for screensharing.
It should also be worth noting that the resources go down to a reasonable level if I restart the service, it only goes up if running for an extended amount of time (and usage with various interactions).
@crameleon I don’t use screen sharing (hence no xdg-desktop-portal-hyprland), that’s why I packaged up waynergy 
and use Barrier on my main desktop…
Something leaking somewhere…
Package xdg-desktop-portal-wlr has no patches which means it could well be upstream problem. Did you try asking on this application support channels?
I haven’t, figured I try here first. It’s unfortunately not the easiest to reproduce for a proper report.
