Xrdp Fedora 43

Ask Fedora
1

Anybody got xrdp to work with Fedora 43?

Should xrdp work with Wayland?

After the login dialog the RDP connection just closes.

PRETTY_NAME=“Fedora Linux 43 (Xfce)”

System is at multi-user.target

xrdp.log
[INFO ] xrdp_wm_log_msg: sesman connect ok
[INFO ] xrdp_wm_log_msg: Performing login request for weberjn
[INFO ] xrdp_wm_log_msg: login was successful - creating session
[INFO ] xrdp_wm_log_msg: session is available on display 10 for user weberjn
[INFO ] xrdp_wm_log_msg: Connecting to session
[INFO ] loaded module ‘libvnc.so’ ok, interface size 4832, version 4
[INFO ] VNC: Clipboard (if available) is provided by chansrv facility
[INFO ] xrdp_wm_log_msg: Connecting to chansrv
[INFO ] Layout from ClientLayout (geom=1920x1080 #screens=1) : 0:(1920x1080+0+0)
[INFO ] Layout from OldServerLayout (geom=1920x1080 #screens=1) : 1804289383:(1920x1080+0+0)
[ERROR] VNC server closed connection

F43 server gets stuck in reboot after adding xfce-desktop
2

I note that “PRETTY_NAME” includes ‘(Xfce)’

Is Xfce the desktop environment you installed and wish to use?

If so, note that xfce 4.20 (on f43) is not Wayland enabled and uses Xorg instead.

I use xrdp all the time on F42 and just tested with F43 and it works just fine.

In /etc/xrdp/xrdp.ini, I enable Xorg and disable VNC:

; Some session types such as Xorg, X11rdp and Xvnc start a display server.
; Startup command-line parameters for the display server are configured
; in sesman.ini. See and configure also sesman.ini.
[Xorg]
name=Xorg
lib=libxup.so
username=ask
password=ask
ip=127.0.0.1
port=-1
code=20

#[Xvnc]
#name=Xvnc
#lib=libvnc.so
#username=ask
#password=ask
#ip=127.0.0.1
#port=-1
#xserverbpp=24
#delay_ms=2000
; Disable requested encodings to support buggy VNC servers
; (1 = ExtendedDesktopSize)
#disabled_encodings_mask=0
; Use this to connect to a chansrv instance created outside of sesman
; (e.g. as part of an x11vnc console session). Replace ‘0’ with the
; display number of the session
#chansrvport=DISPLAY(0)

I also add the file ~/startwm.sh to the home directory of the user logging in via xrdp:

#!/bin/sh

dbus-launch --exit-with-session /usr/bin/startxfce4

and set its permissions to 0755 (O:rwx,G:rx,W:rx)

After restarting xrdp:

systemctl restart xrdp

I am able to log in via xrdp and use Xfce.

If you’re not using Xfce YMMV. If so, perhaps someone else can assist.

HTHAL

3

Yes, this is XFCE.

I tried your settings, but get
xrdp-sesman.log
[ERROR] waitforx: Unable to open display :10

I get the error dialog shown in

but the the rename waitforx hack doesn’t change anything

As I get the login dialog, xrdp seems to work, but doesn’t start a session.

4

What are the contents of ~/.xorgxrdp.10.log and ~/.xsession-errors? That’s often a good place to find errors related to Xorg startup.

Did you confirm that /etc/xrdp/sesman.ini is pointing at the correct Xorg binary (/usr/libexec/Xorg)? Did you confirm that such a binary exists?

Do you have the appropriate Xorg server(s)/packages installed?

Many of the above questions can/will be answered by checking ~/.xorgxrdp.10.log and ~/.xsession-errors.

Usually when I see errors like that, it’s that something like Xorg not being referenced correctly and/or the appropriate packages aren’t installed.

Do you have access to the console of the system in question? If so, can you start Xfce there?

5

Hi, im having the same issue (Unable to open display :10), i dont have a ~/.xorgxrdp.10.log, its like the xorg server starts with an error always, i tried executing the Xorg command directly from another only-terminal session but it doesnt work, as soon as someone connects it dies and throws no useful logs.

Im pretty sure this is a Fedora 43 only problem, since Fedora 42 works fine with gnome-session-xsession

6

I can confirm that Fedora 43 works just fine (as does Fedora 42) with xrdp and XFCE.

I’m firing up a brand new Fedora 43 (gnome) workstation on a VM to confirm it works properly as well, but IIRC it does.

With which version of Fedora are you experiencing this issue?

7

I have confirmed that the Windows RDP client can successfully connect to Fedora 43 workstation by enabling the remote desktop in Settings>System>Remote Desktop***.

XRDP is not required for this to work. In fact, IIRC Xorg has been removed from Fedora 43 Workstation.

Xorg is still available (and xrdp connections via Xorg) for the XFCE spin and probably several others (details anyone?) as XFCE is not yet ready for Wayland.

What fedora version/desktop environment are you trying to use with Xrdp?

***Edit: It seems that rdp is forcefully disconnected after a certain amount of idle time. Once that occurred, I was unable to connect via RDP and saw the following in /var/log/messages:

Failed to start remote desktop session: GDBus.Error:org.freedesktop.DBus.Error.Failed: Session creation inhibited

I believe I was able to address that by disabling screen blanking and power saving features. I have just confirmed this with another VM. Fedora 43 workstation will force disconnect RDP if screen blanking and power saving options are enabled, and will not allow further RDP connections until after a reboot.

This issue does not occur when screen blanking (in power settings and screen lock settings)/power saver options are enabled.

The RDP server that's built in to KDE is buggy
8

Xrdp with Xfce in F43 works like this:

sudo dnf install xrdp xrdp-selinux
sudo tee /etc/sysconfig/desktop << EOF > /dev/null
PREFERRED=xfce4-session
EOF
sudo systemctl enable xrdp.service --now
sudo firewall-cmd --permanent --add-service=rdp
sudo firewall-cmd --reload

All other configs can be left in default state.

9

I’d note that the default xrdp configuration disables Xorg and enables Xvnc as the back end display mechanism. AFAIK, VNC does not provide audio passthrough and generally provides poorer quality interaction than Xorg/xorgxrdp, especially on local networks.

Which is why I generally disable Xvnc and enable Xorg. Your (and other folks’) use case may not be the same as mine, but it’s worthwhile to note that the default configuration limits performance and functionality (especially as it relates to video quality and any sound at all) on higher bandwidth networks.

1 Like
10

Guess I was missing the PREFERRED.

Thanks.

1 Like