At work i use fedora for development and recently switched to kde and sddm for a change.
At home i use slackware-current with kde and sddm.

A thing i just noticed is the following:
- in fedora i get 3 xdg-desktop-portal processes (xdg-desktop-portal, xdg-desktop-portal-kde, xdg-desktop-portal-gtk), all under my username
- in slackware i get 6! three on my username and three under the sddm username

So what i would like to know is why my sddm is spawning this processes? Does anyone else notice the same thing?
I have no idea what the correct behaviour would be, but i'm leaning on fedora's since these portals where meant to be used on a graphical user session for sandboxing purposes

Maybe related to the way systemd handles processes

After some investigations i ended up in a bug report stating issues with processes of xdg-desktop-portal spawned by sddm too soon.
https://bugs.kde.org/show_bug.cgi?id=458865
near the end there's a link to a commit, where its shown an env variable to disable qt from spawning desktop portals, QT_NO_XDG_DESKTOP_PORTAL. This, as far as I understood, was made to prevent the qt part of sddm to set the xcursor before all the rest of the user environment was completely loaded.

So i exported this var in my /etc/environment and rebooted and now I only have desktop-portals under my user.
They also seems to work, at least from firefox i can open my downloads in dolphin just fine. I did notice a slow startup though.

2 members found this post helpful.

Also found this patch from a gentoo overlay
https://www.gentoofan.org/gentoo/pol...o-portal.patch
And this fedora discussion where they do the same thing in fedora37
https://ask.fedoraproject.org/t/core...al-kde/28552/2

3 members found this post helpful.