xRDP on Raspbian - no keyboard or mouse upon connect

[whayden1]

I have a new install on a Pi4 running Raspbian 10 (buster). I have installed "xrdp" and verified that it is running. All packages have been upgraded and updated.

I can connect to the Pi4 via RDP via my Win10 and even an old Win7 machine without issue. I connect, log in and can see the screen. The problem occurs after login. Upon logon I see the desktop, but the keyboard and mouse do not work. They worked at the logon screen, but not when I get to the desktop.

I've tried this a number of times now with the same results.

Any help is greatly appreciated.

[PJKram]

I have the same problem. When I install raspbian on a SD card everything works fine. But when I use Berryboot and install rasbian on a usb drive, I can start a remote rdp login, I can login, I get a desktop but mouse and keyboard do not work. The xrdp log file tells me that the modules mouse and kbd can not be found.

[ 38.613] (II) LoadModule: "mouse"
[ 38.614] (WW) Warning, couldn't open module mouse
[ 38.614] (EE) Failed to load module "mouse" (module does not exist, 0)
[ 38.614] (II) LoadModule: "kbd"
[ 38.614] (WW) Warning, couldn't open module kbd
[ 38.614] (EE) Failed to load module "kbd" (module does not exist, 0)
[ 38.614] rdpIdentify:

What could be the problem ?

[jvriend]

I have this also when upgraded from Jessie to buster.
With Jessie never had a problem, and with a fresh full install of buster it seem to work
but when i changed some settings in bootconfig.txt so he could see a screen of 6 inch,
it stopped working.
I use an RPI 3B and try to connect with windows 7.
I did notice that i saw the handlings i did on my local-screen (screen just connected with the HDMI) , were also shown on the remote
desktop, as it is a copy of my local-screen.

[jvriend]

I have no clue why, but i just found out that when i turn of the screen-saver on a working
system, after reboot the remote control doesn't have a keyboard and mouse.
When i turned on my screen-saver again, my remote control works again ??

I use the default remote desktop from windows to connect with xrdp on my raspbian Buster
and raspbian buster is the default full installation, and xrdp installed.

I have two machines with the RPI as heart and connected through HDMI to a 6' screen.
I like to test and develop the software on a remote (bigger screen) so i can also test the
connected hardware

[jberculo]

Thanks @jvriend!

This was exactly my issue. Turning on the 'screen blank' option at the display preferences fixed it.

I am also in the dark as of the why, but I guess I now have to find another way to force my pi not to go in sleep mode.

[EdwinDigital]

I also met this problem. Enable [Screen Blanking] works for me well, great thanks, guys!

[gonan75]

Simply amazing. I was ready to rip out my remaining hair over this issue. Who knew that screen blanking being disabled would cause this issue. Thanks everyone!

[The_Esch]

Hello and thank you! it work and I can use mouse & keyboard via xrdp again.
but, how can you prevent the raspi to go to sleep mode?

[panca]

Thanks a lot, I was at the end of my wits too until I found this thread. I wonder what causes this and how one could have discovered this systematically? Isn't this kind of a bug? I find something else weird: once the two xrdp-services are enabled, multiple xrpd-related processes are resident in memory, the Xorg-one eating considerable amounts of memory (on a 1gb-model it's 10% of available RAM), even though xrpd is not being used. I happen to have a 64-bit version of RpiOS (Debian) running on another rpi4, where these processes are only loaded once xrpd is activated, and are unloaded again after the user logged off. There xrpd-sesman and xrpd processes are running but they are must be in a dormant waiting/listening state without eating significant memory (0.0 in ps). Maybe there is more misconfiguration in the default xrpd install on default RpiOS?

[fruitoftheloom]

Thanks a lot, I was at the end of my wits too until I found this thread. I wonder what causes this and how one could have discovered this systematically? Isn't this kind of a bug? I find something else weird: once the two xrdp-services are enabled, multiple xrpd-related processes are resident in memory, the Xorg-one eating considerable amounts of memory (on a 1gb-model it's 10% of available RAM), even though xrpd is not being used. I happen to have a 64-bit version of RpiOS (Debian) running on another rpi4, where these processes are only loaded once xrpd is activated, and are unloaded again after the user logged off. There xrpd-sesman and xrpd processes are running but they are must be in a dormant waiting/listening state without eating significant memory (0.0 in ps). Maybe there is more misconfiguration in the default xrpd install on default RpiOS?

xrdp is generic software provided by Debian, it has had no optimizations from RPT / RPF for the Raspberry Pi OS & Hardware.

Hence why RealVNC is offered by default in RaspiOS and RaspiOS64 Beta Operating Systems...

Therefore you need to contact the xrdp developers to make them aware of issues you *feel* need fixing.