xrdp session dont start child sessions of some applications

[axelmaning00]

Hi! I connect to Arch Linux remotely with xrdp. On my remote arch linux, I run various remote work sessions to further connect to other machines. That is, the connection diagram looks something like this
mypc (win10mstsc) => archlinux (with xrdp) => other machine, to connect to other machines I use different clients (uvnc, rdp, anydesk) and if rdp and vnc work well as plugins in remmina, then you need to use anydesk separately . There is a problem. ANYDESK does not work in an xrdp session. If you run Anydesk locally, then everything works.
P.S. sorry my very bad eng
How to make anydesk work under xrdp normally? I heard that there is some problem with PAM from which pulseaudio, for example, did not boot, maybe this is somehow connected?
Forgive me for writing this thread, I'm new to linux and I'm not able to understand all this on my own, I usually read forums to solve problems, but I want this particular topic there are only a couple of branches on the Internet, and all of them are without full solutions .

Also every time to restart Arch, you need to manually enter sudo reboot in the console, since rebooting according to the description from KDE Plasma does not work.

[matt335672]

Hi @axelmaning00

Welcome to the world of Linux! Also, don't apologise for your English. The only way to learn a language is to use it, and you seem to be doing OK to me.

We need more information on what you mean by "ANYDESK does not work in an xrdp session"?

It looks like anydesk allows you to generate trace files. Could you generate one for a working session (locally) and also one for an xrdp session and post them here?

Also, what is the output of the command env | sort on both a working and xrdp session?

The reboot behaviour is normal. See #2305 for a discussion on this.

[axelmaning00]

This local session, anydesk working
env work.txt
anydesk.trace
This xrdp session:
env dont work xrdp
anydesk.trace file not created (anydesk not working)

[matt335672]

This won't be good (from the environment):-

HOME=/root
. . .
USER=root

This could well be #1684. Are you getting messages like this in /var/log/xrdp-sesman.log:-

pam_systemd(xrdp-sesman:session): Failed to create session: No child processes

If you are, the two workarounds for this problem are:-

1. If you're not using systemd to mount home directories, comment-out all calls to pam_systemd_home.so in /etc/pam.d/system-auth. See this post and this post
2. Build and install the pam_close_systemd_system_dbus module. See this post