Running RDP on my Win10 box against my Raspbian distro on an R4 with xrdp. My keyboard layout was not corresponding to my Norwegian keyboard. I followed the advice in https://unix.stackexchange.com/questions/99085/save-setxkbmap-settings to get the keyboard (Norwegian). setxkbmap no in a terminal fixes it. I also followed the advice and added that to ~/profile. Problem is my keyboard layout seems to be reset when the connection is broken (for what ever reason, network glitch, rebooting router after fiddling with some settings etc) or simply being inactive for a while even without the connection being broken. Any takers? Quick question. What's the difference between setxkbmap no and setxkbmap -layout no? Both seems to do the trick but both suffers from the same lack of permanency.

I am using remote desktop on a windows machine to connect to a CentOS 7 machine running a Xrdp server. Recently I had a problem with an application, where the avaialable openGL version (2.1) was not enough and it suggested either updating it, or using VNC. While trying to make a VNC connection to work I made several updates inlcuding a Kernel update. I could not get the turboVNC to work at the same time than Xrdp, and damaged the settings somehow. Now, when I connect to the Xrdp session the Gnome shell window is very small and has a weird aspect ratio, making it unusable (see picture below, the black area is the the size of my screen). Even if logged out of the gnome session, where I am able to select other shell (KDE, for example) I still have the same window size. Since I could not find a similar problem, I am not sure what is causing the problem. How could I return the size of the window to its original shape and size?

I don't know what to do I spend around 2 weeks setting up XRDP. I have XRDP up and running with Xorg on a 64 core epyc 3 gen. and performance is terrible. The machine's main usage should be as a terminal server for YouTube videos, but it can't handle even a single session ( I am expecting 30). When the video is full screen, it's lagging and input lag is sometimes good but sometimes 10 seconds. Is there any way to increase performance? What I tried: 1. tried xorgxrdp and xorgxrdp-glamor (interestingly, without glamor it's responsive but not usable) 2. for test acceleration with AMD 5600xt - still same 3. server set up with tcp_send_buffer_bytes=4194304 and net.core.wmem_max = 8388608 4. max_bpp=24/32, use_compresion=true/false, crypt_level=none/high 5. audio: tried wia, pulse and pipewire 6. OS Rocky 9.6, Debian 11/12 I hope I didn't miss anything.

Hello I use XRDP for multiuser and I have performance issue and connec issue. First, is about channel drdynvc if its set to TRUE I cannot connect from windows RDP client and can connect without issues from remmina. Second performance, for some reason if is drdynvc set to FALSE performance is terrible all is laggy, but if its TRUE it works perfectly, but I cant connect from windows RDP. I'm little bit sad about it. Do anyone have solution? system is Rocky 9 with xrdp xorgxrdp-glamor from repositores. Thank you.

I have a Ubuntu installation where multiple users have desktop sessions at the same time, some over XRDP and another directly on VT7. How can I find out which of these users initiated a shutdown or reboot, e.g by the XRDP mechanism or by the systray popup menu? For example: Like in Windows system in event viewer I can see which user did restart or shutdown by that the user click on button in each session even in RDP so the same I search to do for Linux system None of the users will use the command-line to perform shutdown or restart.

I have the 'module' lmod command set up on my Ubuntu Linux servers. This works well for users who connect via ssh to the server ('module avail' shows the available modules). Some users want to connect using xrdp or x2go, and when they open a terminal window in that type of session, the 'module' commands don't work. I can solve this on a case-by-base basis by having them edit the preferences in the terminal app and setting 'Run command as a login shell'. New terminal sessions after that will have the 'module' environment set up correctly. How can I set this system-wide, so that all users get that 'login shell' behavior? Or, how can I configure it so that the lmod setup gets run whether it's a login shell or not?

There're color artifacts when connecting from Windows remote desktop client to Xrdp on a CentOS box. I want to check whether the underlying Xvnc will have same artifacts. Xvnc is running: LISTEN 0 5 127.0.0.1:5911 *:* users:(("Xvnc",pid=10260,fd=7)) I forward the port: ssh root@funktest -L 5911:localhost:5911 And connect with tightvnc vncviewer.exe to localhost:11. It is asking for the password I don't know. In /etc/xrdp/xrdp.ini there's the block: [Xvnc] name=Xvnc lib=libvnc.so username=ask password=ask What does ask mean? What's the default password used by xrdp?

With a basic install, per: dnf install -y xrdp openssl req -x509 -newkey rsa:2048 -nodes -keyout key.pem -out cert.pem -days 365 mv cert.pem /etc/xrdp/ mv key.pem /etc/xrdp/ systemctl start xrdp systemctl status xrdp systemctl enable xrdp firewall-cmd --add-port=3389/tcp --permanent firewall-cmd --reload I get the following when trying to connect: ... VNC error - problem connecting some problem The content of /var/log/xrdp.log is: [20170216-18:44:37] [INFO ] A connection received from: 192.168.76.11 port 63615 [20170216-18:44:37] [INFO ] A connection received from: 192.168.76.11 port 63615 [20170216-18:44:37] [INFO ] An established connection closed to endpoint: 192.168.76.11:63615 - socket: 8 [20170216-18:44:37] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7 [20170216-18:44:37] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem [20170216-18:44:37] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem [20170216-18:44:37] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 8 [20170216-18:44:37] [INFO ] A connection received from: 192.168.76.11 port 63616 [20170216-18:44:37] [ERROR] Listening socket is in wrong state we terminate listener [20170216-18:44:37] [INFO ] An established connection closed to endpoint: 192.168.76.11:63616 - socket: 8 [20170216-18:44:37] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7 [20170216-18:44:37] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem [20170216-18:44:37] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem [20170216-18:44:37] [DEBUG] xrdp_0000105d_wm_login_mode_event_00000001 [20170216-18:44:37] [WARN ] local keymap file for 0x0409 found and dosen't match built in keymap, using local keymap file [20170216-18:44:37] [DEBUG] returnvalue from xrdp_mm_connect 0 [20170216-18:44:41] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:42] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:43] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:44] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:45] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:46] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:47] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:48] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:49] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:50] [DEBUG] VNC Error after security negotiation [20170216-18:44:50] [DEBUG] VNC error before sending share flag [20170216-18:44:50] [DEBUG] VNC error before receiving server init [20170216-18:44:50] [DEBUG] VNC error before receiving pixel format [20170216-18:44:50] [DEBUG] VNC error before receiving name length [20170216-18:44:50] [DEBUG] VNC error before receiving name [20170216-18:44:50] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12 [20170216-18:44:50] [DEBUG] xrdp_mm_module_cleanup [20170216-18:44:50] [DEBUG] VNC mod_exit [20170216-18:44:50] [INFO ] An established connection closed to endpoint: 127.0.0.1:3350 - socket: 11 [20170216-18:46:09] [INFO ] An established connection closed to endpoint: 192.168.76.11:63616 - socket: 8 [20170216-18:46:09] [DEBUG] xrdp_mm_module_cleanup [20170216-18:46:09] [ERROR] Listening socket is in wrong state we terminate listener [20170216-18:46:09] [INFO ] A connection received from: 192.168.76.11 port 63630 [20170216-18:46:09] [INFO ] An established connection closed to endpoint: 192.168.76.11:63630 - socket: 8 [20170216-18:46:09] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7 [20170216-18:46:09] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem [20170216-18:46:09] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem [20170216-18:46:11] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 8 [20170216-18:46:11] [ERROR] Listening socket is in wrong state we terminate listener The content of /var/log/xrdp-sesman.log is: [20170216-18:44:28] [WARN ] [init:46] libscp initialized [20170216-18:44:28] [CORE ] starting sesman with pid 4144 [20170216-18:44:28] [INFO ] listening... [20170216-18:44:37] [INFO ] A connection received from: 127.0.0.1 port 44184 [20170216-18:44:38] [INFO ] scp thread on sck 8 started successfully [20170216-18:44:38] [INFO ] ++ created session (access granted): username root, ip 192.168.76.11:63616 - socket: 8 [20170216-18:44:38] [INFO ] starting Xvnc session... [20170216-18:44:38] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9 [20170216-18:44:38] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9 [20170216-18:44:38] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9 [20170216-18:44:38] [INFO ] An established connection closed to endpoint: 127.0.0.1:44184 - socket: 8 [20170216-18:44:38] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7 [20170216-18:44:38] [INFO ] An established connection closed to endpoint: 127.0.0.1:44184 - socket: 8 [20170216-18:44:38] [INFO ] Xvnc :10 -geometry 1904x1003 -depth 24 -rfbauth /root/.vnc/sesman_root_passwd -bs -nolisten tcp -localhost -dpi 96 [20170216-18:44:38] [INFO ] starting xrdp-sessvc - xpid=4196 - wmpid=4195 [20170216-18:44:38] [INFO ] ++ terminated session: username root, display :10.0, session_pid 4194, ip 192.168.76.11:63616 - socket: 8

I'm trying to use xrdp to RDP from my windows machine to my linux box(specifically xorg xrdp as mentioned in the Arch Linux wiki for setting up RDP). I'm having an issue with what I believe to be my desktop environment (xfce4) causing my RDP connection to be terminated. I have provided the snippets from XRDP and XRDP-Sesman below. I ssh'd in and decided to see what was happening on the linux box whenever I tried to connect with my Windows RDP client. I do get a login box, and the login seems to succeed. I have tried a lot of different solutions involving making sure: - .xsessions features the line xfce4-session - Xwrapper is setup to allow any user to connect - that my .xinitrc executes startxfce4 - set a keep alive timer within the .ini file **xrdp.log** [20190730-18:33:02] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:02] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20190730-18:33:02] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:51792) [20190730-18:33:02] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:02] [DEBUG] xrdp_mm_module_cleanup [20190730-18:33:02] [DEBUG] Closed socket 19 (AF_UNIX) [20190730-18:33:02] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:23] [INFO ] Socket 12: AF_INET connection received from 10.64.27.2 port 33394 [20190730-18:33:23] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:23] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389) [20190730-18:33:23] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20190730-18:33:23] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20190730-18:33:23] [DEBUG] TLSv1.2 enabled [20190730-18:33:23] [DEBUG] TLSv1.1 enabled [20190730-18:33:23] [DEBUG] TLSv1 enabled [20190730-18:33:23] [DEBUG] Security layer: requested 11, selected 1 [20190730-18:33:23] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:25] [INFO ] Socket 12: AF_INET connection received from 10.64.27.2 port 45509 [20190730-18:33:25] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:25] [DEBUG] Closed socket 11 (AF_INET 0.0.0.0:3389) [20190730-18:33:25] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20190730-18:33:25] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20190730-18:33:25] [DEBUG] TLSv1.2 enabled [20190730-18:33:25] [DEBUG] TLSv1.1 enabled [20190730-18:33:25] [DEBUG] TLSv1 enabled [20190730-18:33:25] [DEBUG] Security layer: requested 11, selected 1 [20190730-18:33:25] [INFO ] connected client computer name: DESKTOP-0C7KOCP [20190730-18:33:25] [INFO ] adding channel item name rdpdr chan_id 1004 flags 0x80800000 [20190730-18:33:25] [INFO ] adding channel item name rdpsnd chan_id 1005 flags 0xc0000000 [20190730-18:33:25] [INFO ] adding channel item name cliprdr chan_id 1006 flags 0xc0a00000 [20190730-18:33:25] [INFO ] adding channel item name drdynvc chan_id 1007 flags 0xc0800000 [20190730-18:33:25] [INFO ] TLS connection established from 10.64.27.2 port 45509: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 [20190730-18:33:25] [DEBUG] xrdp_00002b80_wm_login_mode_event_00000001 [20190730-18:33:25] [INFO ] Loading keymap file /etc/xrdp/km-00000809.ini [20190730-18:33:25] [WARN ] local keymap file for 0x00000809 found and doesn't match built in keymap, using local keymap file [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350 [20190730-18:33:31] [INFO ] xrdp_wm_log_msg: sesman connect ok [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait... [20190730-18:33:31] [DEBUG] return value from xrdp_mm_connect 0 [20190730-18:33:31] [INFO ] xrdp_wm_log_msg: login successful for display 10 [20190730-18:33:31] [DEBUG] xrdp_wm_log_msg: started connecting [20190730-18:33:32] [INFO ] lib_mod_log_peer: xrdp_pid=11136 connected to X11rdp_pid=11141 X11rdp_uid=1008 X11rdp_gid=1009 client_ip=10.64.27.2 client_port=45509 [20190730-18:33:32] [DEBUG] xrdp_wm_log_msg: connected ok [20190730-18:33:36] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:36] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:40] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:40] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:44] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:44] [DEBUG] Closed socket 20 (AF_UNIX) [20190730-18:33:48] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20190730-18:33:48] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20190730-18:33:48] [DEBUG] Closed socket 18 (AF_INET 127.0.0.1:52154) [20190730-18:33:48] [DEBUG] Closed socket 12 (AF_INET 10.64.5.120:3389) [20190730-18:33:48] [DEBUG] xrdp_mm_module_cleanup [20190730-18:33:48] [DEBUG] Closed socket 19 (AF_UNIX) [20190730-18:33:48] [DEBUG] Closed socket 20 (AF_UNIX) **xrdp-sesman.log** [20190730-18:32:31] [DEBUG] Closed socket 1 (AF_INET 127.0.0.1:3350) [20190730-18:32:31] [INFO ] starting xrdp-sesman with pid 11093 [20190730-18:32:31] [INFO ] listening to port 3350 on 127.0.0.1 [20190730-18:32:46] [INFO ] A connection received from 127.0.0.1 port 51792 [20190730-18:32:46] [INFO ] ++ created session (access granted): username walker, ip 10.64.27.2:57868 - socket: 12 [20190730-18:32:46] [INFO ] starting Xorg session... [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910) [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6010) [20190730-18:32:46] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6210) [20190730-18:32:46] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [INFO ] calling auth_start_session from pid 11099 [20190730-18:32:46] [DEBUG] Closed socket 7 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:32:46] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20190730-18:32:46] [CORE ] waiting for window manager (pid 11100) to exit [20190730-18:32:46] [CORE ] window manager (pid 11100) did exit, cleaning up session [20190730-18:32:46] [INFO ] calling auth_stop_session and auth_end from pid 11099 [20190730-18:32:46] [DEBUG] cleanup_sockets: [20190730-18:32:46] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:32:46] [DEBUG] cleanup_sockets: failed to delete /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:32:46] [INFO ] ++ terminated session: username walker, display :10.0, session_pid 11099, ip 10.64.27.2:57868 - socket: 12 [20190730-18:33:31] [INFO ] A connection received from 127.0.0.1 port 52154 [20190730-18:33:31] [INFO ] ++ created session (access granted): username walker, ip 10.64.27.2:45509 - socket: 12 [20190730-18:33:31] [INFO ] starting Xorg session... [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:5910) [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6010) [20190730-18:33:31] [DEBUG] Closed socket 9 (AF_INET 0.0.0.0:6210) [20190730-18:33:31] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:33:31] [INFO ] calling auth_start_session from pid 11139 [20190730-18:33:32] [DEBUG] Closed socket 7 (AF_INET 127.0.0.1:3350) [20190730-18:33:32] [DEBUG] Closed socket 8 (AF_INET 127.0.0.1:3350) [20190730-18:33:32] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20190730-18:33:32] [CORE ] waiting for window manager (pid 11140) to exit [20190730-18:33:32] [CORE ] window manager (pid 11140) did exit, cleaning up session [20190730-18:33:32] [INFO ] calling auth_stop_session and auth_end from pid 11139 [20190730-18:33:32] [DEBUG] cleanup_sockets: [20190730-18:33:32] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdp_chansrv_socket_10 [20190730-18:33:32] [DEBUG] cleanup_sockets: deleting /tmp/.xrdp/xrdpapi_10 [20190730-18:33:32] [DEBUG] cleanup_sockets: failed to delete /tmp/.xrdp/xrdpapi_10 [20190730-18:33:32] [INFO ] ++ terminated session: username walker, display :10.0, session_pid 11139, ip 10.64.27.2:45509 - socket: 12 Any advice that can point me towards a solution would be awesome thanks!

I have rootless Podman container (system: Alpine Linux) in Podman (master system: Alpine Linux). Container is able to work with xRDP (and sesman) so I am able to connect to it via local user (if defined). I would like to authorize user even if no account already defined on container system. I would like to write custom PAM module with checking external service data via OAuth2 or REST API requests. Unfortunately I am not able to get password user typed in xRDP login form. My current questions: - I have a plan to prepare sh script for this operation. Does it is possible in general? - I would like to keep xRDP login form so I don't have an access to web browser at time of login so external service cannot be activated before login form. I believe I can work with REST API of service also (but need token or user name - password pair). - Do I have any chance to get password from xrdp login dialog or really not due to PAM architecture? - Does PAM module is the only way here in Linux how to authorize+authenticate users for Alpine Linux (or in general for any Linux)? Thanks for help.

I'm encountering a problem with KDE Plasma on Debian 12 on a VM, when using xRDP to access my desktop remotely. The issue revolves around Polkit authentication, where the GUI prompt for administrative actions is not behaving as expected. Affected System Details: - Debian 12 VM with KDE Plasma created with QEMU/KVM - xRDP version: 0.9.21.1

plasmashell --version
	plasmashell 5.27.5
apt list --installed | grep policy
	policykit-1/stable,now 122-3 amd64 [installed,automatic]
	libpolkit-qt5-1-1/stable,now 0.114.0-2 amd64 [installed,automatic]
apt list --installed | grep polkit
	libpolkit-agent-1-0/stable,now 122-3 amd64 [installed,automatic]
	libpolkit-gobject-1-0/stable,now 122-3 amd64 [installed,automatic]
	libpolkit-qt5-1-1/stable,now 0.114.0-2 amd64 [installed,automatic]
	polkit-kde-agent-1/stable,now 4:5.27.5-2 amd64 [installed,automatic]
	polkitd-pkla/stable,now 122-3 amd64 [installed,automatic]
	polkitd/stable,now 122-3 amd64 [installed,automatic]

` Problem Description: When I'm connected through xRDP and try to perform tasks using GUI System Settings that require elevated privileges (like changing settings in the System Settings, or disabling the KDE Wallet subsystem), I'm not getting the usual Polkit GUI prompt to enter my password. As a result, I can't apply any changes. Observations: 1.) This issue is specific to my xRDP sessions. When logged in via the Display of Virtmanager using SPICE or via NoMachine, the Polkit prompts appear and function correctly. 2.) The problem persists across different administrative tasks that normally require authentication. 3.) When I am logged in the polkit-kde-authentication-agent-1 gets started for the user that is logged in:

root@debian12-test:~# pgrep -af polkit-kde-authentication-agent-1
5355 /usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1
root@debian12-test:~# ps -o user= -p 5355
user

4.) When I watch the journalctl -f -u polkit - When I login with NoMachine where Polkit works: `Dec 01 09:20:13 debian12-test polkitd: Registered Authentication Agent for unix-session:22 (system bus name :1.299 [/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) ` - When I login with xRDP where Polkit is broken: ` Dec 01 09:26:36 debian12-test polkitd: Registered Authentication Agent for unix-session:c12 (system bus name :1.376 [/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) ` - I do not get any error message with journalctl -f -u polkit Troubleshooting Done: - I've confirmed that polkit is installed and running. systemctl status polkit.service ● polkit.service - Authorization Manager Loaded: loaded (/lib/systemd/system/polkit.service; static) Active: active (running) Questions: 1. Are there specific configurations or known issues with Polkit and xRDP in KDE Plasma on Debian 12 that might be causing this? 2. Any suggestions on how to ensure the Polkit authentication agent starts correctly in xRDP sessions or how to debug this further? Any insights or suggestions would be greatly appreciated. I'm happy to provide additional details if needed. Thank you in advance!

I have setup XRDP on a ubuntu computer that I wanted to access remotely. There are Bluetooth and audio devices attached to that remote device that I would like to access. Using XRDP, it shows that there is no Bluetooth dongle and under Audio(Sounds) there are no microphones and the only output audio is a "Dummy Output". Is there a way to gain access to these hardware devices over XRDP? I have also tried Chrome Remote Desktop and I get the same thing. Local: Windows 10 Pro Remote: Ubuntu 20.04

I am trying to configure XRDP on my **Xubuntu 24.04** machine to allow remote connections from another Xubuntu 24.10 Linux machine (via VPN, same network). My goal is to **create a new XFCE session through XRDP**, which provides **the same desktop experience as my local session**, without interfering with any user that might be physically present at the machine. --- ### What I am trying to achieve - I want to **connect remotely** and start a **new session**, not take over the existing local session. - This **new session** should offer the **same XFCE environment as my local desktop**, including: - Panels and launchers in the same positions. - Desktop layout and configurations as I’ve set them locally. - The same user profile experience as when logging in physically at the console. - I need this remote session to **start even if nobody is logged in locally**. > **Note:** On standard **Ubuntu 24.04 (GNOME)**, there is **built-in support for remote desktop** via RDP (GNOME Remote Desktop). > It allows remote users to connect through RDP and either **share the existing session** or **create a new one**, depending on the setup. > I would like to achieve a **similar behavior** on **Xubuntu**, where I can create a **new remote session**, with my **XFCE desktop environment**, that mirrors the experience I have when logged in locally. --- ### What I have tried - **VPN access** is working fine. It's like I'm on the local network. - XRDP is installed and running. - Packages installed: - xorgxrdp - dbus-x11 - xfce4 and xfce4-goodies - /etc/X11/Xwrapper.config:

allowed_users=anybody
   needs_root_rights=no

- /etc/xrdp/startwm.sh contains:

#!/bin/sh

    if [ -r /etc/default/locale ]; then
        . /etc/default/locale
        export LANG LANGUAGE
    fi

    exec startxfce4

- I also tried adding export DISPLAY=:10 in startwm.sh. - I created executable ~/.xsession and ~/.Xclients with exec startxfce4. - .Xauthority has correct ownership and permissions. --- ### What happens - XRDP successfully establishes a connection, creating a new session on display :10. - Xorg seems to start fine, but startxfce4 exits immediately. - On the client side (Remmina RDP), I see a **black screen** for a few seconds and then the connection closes. - xrdp-sesman.log reports:

Window manager exited quickly

- .xorgxrdp.10.log shows the X server terminating cleanly without errors. --- ### What works (as an alternative) **NoMachine Free** works, but it only connects to the **local physical session**, which I do not want, because it disturbs any local user, in addition, there may be no active session (PC just turned on). --- ### The core question **How can I configure XRDP on Xubuntu 24.04 to start a new XFCE session that loads my full user environment (panels, launchers, desktop layout), providing the same experience as logging in locally, without disturbing local users, or without having any active session?** --- ### Notes - I do **not** need multiple concurrent remote sessions. - I only need **one remote session**, separate from the physical console. - I prefer a solution that allows me to replicate the **same user experience** I have locally.

I am trying to connect to a remote machine using Remmina with the XRDP protocol. I have installed and started the Xrdp server on the remote machine (Pop_OS) and I am trying to connect using the Remmina client on Arch Linux. When I try to connect, I just a black screen with no posted error message. If I change the connection settings in the client to use the wrong password, when I connect I get redirected to an Xrdp login window. So, the client is clearly connecting to the Xrdp server. Does anyone know what might be causing the black screen and how I can fix it? ---------------- **Update:** On further investigation, the problem seems to be that the X server is starting, but the client application is not. Xrdp seems to be trying to start the X server directly with Xorg (rather than xinit or startx). From xrdp's sesman.ini file: /usr/lib/xorg/Xorg -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log The server is starting and the log file being created, but nothing on the screen. I have tried adding a ~/.xsession file and running a similar command from a virtual terminal directly on the machine, and I also get a similar blank screen. Honestly, I am not sure how to properly launch an X client application using Xorg. Should Xorg refer to the ~/.xsession file, or do I need to do something else?

When I set up my home server, I installed Fedora 39 Server on it, and I set up remote access with xrdp, which worked great. Then after I upgraded to Fedora 40 and tried to remotely connect, I would get the login screen, enter my password and I'd immediately be kicked out. I can still connect in the terminal using PuTTY, I uninstalled and reinstalled the desktop (KDE), I reinstalled xrdp, but to no avail. When I run systemctl status xrdp, everything looks normal, except the session closes immeidately: I've looked online and maybe a remote session file would be left behind and inaccessible, but the solutions suggested there did not work either. Since the error doesn't seem very specific to me though, maybe I'm not looking in the right place. Any help is much appreciated.

I have an HP DL360 Gen9 with CentOS7 running and we recently physically migrated the server. Perhaps we didn't reboot the server in a long time or we never connected physically so I don't know if it was a previous issue or not. xfce was installed sometime in the last few years and we were able to remote into the server with xrdp installed without an issue. But when I'm connected physically to the server, it shows the OS loading screen right before its supposed to show a log-in screen. But it just goes blank (black) from there. Hitting Alt+F2, I can see that it is stuck at this: A start job is running Wait for Plymouth Boot Screen to Quit

I installed xrdp on a Debian-12.5.0-amd64 with the Gnome windows manager:

sudo apt update && sudo apt upgrade
sudo apt-get install xrdp
systemctl status xrdp
sudo adduser xrdp ssl-cert
systemctl restart xrdp

/etc/xrdp/sesman.ini is configured as such: [Sessions] ... KillDisconnected=false DiconnectedTimeLimit=0 IdleTimeLimit=0 I can connect using windows remote desktop and it works well, but the session freezes and then disconnects after a few minutes of inactivity saying that the session is over. I need to type on the server keyboard for the client to be able again to join the remaining session. - How to maintain the ability to open xrdp session without timeout? - How to work with a remote headless server, not requiring a local proof of life? Regards. Note that if using Xfce instead of Gnome, or if using Gnome on Ubuntu instead of Debian, the problem does not occur!

I am trying to connect via xRDP from Win10 to my recently installed Bodhi Linux. I could connect from this client to many other Ubuntu servers. This is my first time with Bodhi, but everything looks familiar. How can I solve this, or at least diagnose? Below I am posting relevant info. From logs $ tail -30 /var/log/xrdp.log ... [20220405-08:12:37] [INFO ] TLS connection established from ::ffff:192.168.0.71 port 60854: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 [20220405-08:12:37] [DEBUG] xrdp_000007ad_wm_login_mode_event_00000001 [20220405-08:12:37] [INFO ] Loading keymap file /etc/xrdp/km-0000080a.ini [20220405-08:12:37] [WARN ] local keymap file for 0x0000080a found and doesn't match built in keymap, using local keymap file [20220405-08:12:42] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350 [20220405-08:12:42] [INFO ] xrdp_wm_log_msg: sesman connect ok [20220405-08:12:42] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait... [20220405-08:12:42] [DEBUG] return value from xrdp_mm_connect 0 [20220405-08:12:43] [INFO ] xrdp_wm_log_msg: login successful for display 13 [20220405-08:12:43] [DEBUG] xrdp_wm_log_msg: started connecting [20220405-08:12:44] [INFO ] lib_mod_log_peer: xrdp_pid=1965 connected to X11rdp_pid=1973 X11rdp_uid=1000 X11rdp_gid=1000 client_ip=::ffff:192.168.0.71 client_port=60854 [20220405-08:12:44] [DEBUG] xrdp_wm_log_msg: connected ok [20220405-08:12:44] [DEBUG] xrdp_mm_connect_chansrv: chansrv connect successful [20220405-08:12:44] [DEBUG] Closed socket 18 (AF_INET6 ::1 port 32828) [20220405-08:12:45] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:192.168.0.176 port 3389) [20220405-08:12:45] [DEBUG] xrdp_mm_module_cleanup [20220405-08:12:45] [DEBUG] Closed socket 19 (AF_UNIX) [20220405-08:12:45] [DEBUG] Closed socket 20 (AF_UNIX) $ tail -30 /var/log/xrdp-sesman.log ... [20220405-08:12:42] [INFO ] A connection received from ::1 port 32828 [20220405-08:12:42] [INFO ] ++ created session (access granted): username user1, ip ::ffff:192.168.0.71:60854 - socket: 12 [20220405-08:12:43] [INFO ] starting Xorg session... [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910) [20220405-08:12:43] [ERROR] g_tcp_bind(9, 6010) failed bind IPv6 (errno=98) and IPv4 (errno=22). [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 0) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 5911) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6011) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6211) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 5912) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6012) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6212) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 5913) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6013) [20220405-08:12:43] [DEBUG] Closed socket 9 (AF_INET6 :: port 6213) [20220405-08:12:43] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350) [20220405-08:12:43] [INFO ] calling auth_start_session from pid 1966 [20220405-08:12:43] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350) [20220405-08:12:43] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350) [20220405-08:12:43] [INFO ] /usr/lib/xorg/Xorg :13 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20220405-08:12:43] [CORE ] waiting for window manager (pid 1972) to exit [20220405-08:12:45] [CORE ] window manager (pid 1972) did exit, cleaning up session [20220405-08:12:45] [INFO ] calling auth_stop_session and auth_end from pid 1966 [20220405-08:12:45] [DEBUG] cleanup_sockets: [20220405-08:12:45] [DEBUG] cleanup_sockets: deleting /run/xrdp/sockdir/xrdp_chansrv_audio_out_socket_13 [20220405-08:12:45] [DEBUG] cleanup_sockets: deleting /run/xrdp/sockdir/xrdp_chansrv_audio_in_socket_13 [20220405-08:12:45] [DEBUG] cleanup_sockets: deleting /run/xrdp/sockdir/xrdpapi_13[20220405-08:12:45] [INFO ] ++ terminated session: username user1, display :13.0, session_pid 1966, ip ::ffff:192.168.0.71:60854 - socket: 12 $ cat .xorgxrdp.13.log.old [ 2936.394] X.Org X Server 1.20.13 X Protocol Version 11, Revision 0 ... [ 2936.397] (++) Log file: ".xorgxrdp.13.log", Time: Tue Apr 5 08:12:43 2022 [ 2936.398] (++) Using config file: "/etc/X11/xrdp/xorg.conf" [ 2936.398] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 2936.399] (==) ServerLayout "X11 Server" [ 2936.399] (**) |-->Screen "Screen (xrdpdev)" (0) [ 2936.399] (**) | |-->Monitor "Monitor" [ 2936.400] (**) | |-->Device "Video Card (xrdpdev)" [ 2936.400] (**) |-->Input Device "xrdpMouse" [ 2936.400] (**) |-->Input Device "xrdpKeyboard" [ 2936.400] (**) Option "DontVTSwitch" "on" [ 2936.400] (**) Option "AutoAddDevices" "off" ... Firewall status. Rules 3 and 5 were added later on, but they did not solve the problem. $ sudo ufw status Status: active To Action From -- ------ ---- 22/tcp ALLOW Anywhere 3389 ALLOW 192.168.0.0/24 3389 ALLOW Anywhere 22/tcp (v6) ALLOW Anywhere (v6) 3389 (v6) ALLOW Anywhere (v6)

I'm a casual Linux user. I don't fully understand Xsessions and desktop/window manager configs and the like. I've got a Jetson Nano Mini and I want to setup Xrdp so I can stick it in the cupboard and use it remotely. I've installed Xrdp with sudo apt install xrpd and I can connect and login, but the desktop is not the same as the one you get when you login locally. I realise it's a different Xsession (or at least I think I do) but also the theme and layout are different. What do I need to do so that the desktop I see when I log in via Xrdp looks the same as the desktop I see when I login locally? I'm not super fussed about connecting to the console session over RDP, but if that's an easy on/off option in some config somewhere it would be good to know. The Jetson Nano is running Ubuntu 18.04.

I have a pretty generic Kubuntu install and cannot RDP into it. I installed xrdp and created the .xsession file and can connect successfully from my Mac. I get the KDE logo with the spinning gear, and then the screen goes black with an "X" cursor that I can move around the empty screen. That's it. I am using stock SDDM as a display manager. If I switch to lightdm, xrdp works great, but I can't log into the machine the regular way so that's a fail. I need to stick with SDDM to use my machine normally. Can someone help?