Xrdp Windows Client

It doesn't exist in my computer. I need to use Windows 10 Remote Desktop as the connecting client, so I've used xrdp. If I install x2go do I need a dedicated x2go.

Hello World,

  • Step 4: Remote Desktop Client. To be able to access the Raspberry Pi remotely, we need a corresponding remote desktop client software on the client. As already mentioned in the introduction, Windows comes with a suitable client. You can find it under: All Programs - Accessories - Remote Desktop Connection.
  • The Xrdp web client This is the component that does the actual connection to the FastX server to display graphics and interact with the session. The xrdp web client is built using AngularJS and a custom set of RDP libraries. The FastX API gets all the needed information to make an XRDP connection using the Xrdp web client.

Today’s post is about a recurring issue that occurs when using xRDP software solution on Ubuntu systems. The system crash popup that appears each time you login into your remote session after performing the xRDP installation process. So far, we never had time to investigate this issue and usually this is considered as a minor annoyances for the users. We have spend some time in investigating this problem and this post will show you how to get rid of this crash message system.

Let’s do this…

Initial Connection

Let’s assume that we are performing a manual installation of xRDP package on Ubuntu 18.04. To perform this installation, we have simply issued the following command in a Terminal Console

sudo apt-get install xrdp

At this stage, we do not perform any additional configuration and we should be able to perform a remote connection to Ubuntu. So, start your favorite remote desktop client, provide ip address or hostname and you should see the xrdp login page. Provide your credentials and Press OK

Click on picture for better resolution

If everything is ok, a remote connection to your system should be performed. However, you will notice that you have received a popup asking you to authenticate

Click on picture for better resolution

Identifying the root cause

In our previous post , we have explained why this behavior was triggered. PolKit authorization framework is controlling which actions can be performed on the system by the users. However, we have not yet provided the way to configure Ubuntu to avoid these popups. We might publish a post about all the possible way to fix the popup issue. However, if you google and look on internet, the most frequent answer to solve this issue consists in two steps

  • create a file in /etc/polkit-1/localauthority.d.conf called 02-allow-color.d.conf
  • copy/paste the text below in the file

The file is basically an authorization file rules that can be used to override policies defined by the PolKit authorization framework component. This file is basically saying that if a user is part of the group users (in this example), it will be allowed to perform the colord actions defined in the policy file. With this configuration change in place, when performing a remote connection to Ubuntu, no more popups about authentication required will be displayed but the system crash popup start to showing up

Click on picture for better resolution

So, it seems that the creation of this file is actually causing the crash popup. By checking the /var/crash library content, a crash report related to the PolcyKit is available. So, logically, the issue is related to the PolKit component and the error is caused by the addition of this 02-allow-colord.conf file. As soon as the file is deleted, the Authentication Required popups are displayed but no more crash system popup.

Click on picture for better resolution

The problem is indeed related to the Polkit engine and more specifically to the file being used…..Searching on Internet for some tips (or even better a solution), we came across this post . Apparently, it’s important to know the Polkit version in use on the system as this will define how the authorization rules files would be processed (or not processed). If the version of the PolKit is < 0.106, you need to create a .pkla file (and not a .conf file).


Checking on Ubuntu 18.04, using the command pkaction –version, we can clearly see that the version is 0.105 and thus we need to use correct syntax for this version

What Is A Windows Client

Click on picture for better resolution

The solution is basically to create the proper file, with the proper file extension and proper syntax to be used so the system recognize fully the authorization rules and does not crash anymore. Based on the documentation founded here, the following .pkla file has been generated. This file tell the PolKit framework that any users can perform actions defined in the colord.xml policy file

Save the file as 45-allow-colord.pkla and place it in the following directory (you need admin rights to copy files in this location !!)

Before trying to connect remotely to your system, ensure that the /var/crash directory is empty. You can delete the content of the directory using the following command

sudo rm /var/crash/*

When done, try to perform a remote connection and if everything works as expected, you should have access to your desktop with no Authentication Required Popups and no system crash popup. Double check that no crash report has been generated while using the new Polkit format file by checking the content of /var/crash directory. It should be empty….

After some much time, we have finally identified and fixed the issue related to this system crash popup. Since we are aware of the issue, we have updated the Standard installation script (ver 0.2) so the script create the .pkla file and not the .conf file anymore. Noboby never focused on this small issue. The strange thing is this story is that the allow-colord.conf file seems to work as the Authentication required popups are gone but they indeed generate another annoyance.

Voila ! The issue is solved and it’s time to go and relax

Till next time

See ya

Xrdp Windows Client Download

Select language:

To manage the Raspberry Pi over the network, it is also possible to access it remotely via remote desktop in addition to SSH and VNC. Microsoft’s Remote Desktop Protocol (RDP) enables the transmission and control of screen content over the network. This is particularly useful for Windows users, since Windows already has the appropriate client (Microsoft Terminal Services Client). In the following article I show step-by-step how to set up Remote Desktop on the Raspberry Pi and then access it using Windows/Mac/iPhone/Android.

Difficulty level:

Xrdp Windows Client

Schritt 1: Activate Boot to Desktop

First, the Raspberry Pi must be configured to start the (graphical) desktop after booting. This can be configured with a few clicks via raspi-config:

Select the entry »3 Enable Boot to Desktop/Scratch« and then confirm »Desktop Log in as user ‘pi’ at the graphical desktop«.

Step 2: Install XRDP Server

NOTE – Raspberry Pi with PIXEL desktop

Unfortunately, XRDP does not work with the new Raspbian Image right away. The integrated RealVNC Server and XRDP are in conflict and cannot be used together. To resolve this conflict, RealVNC must be uninstalled before installing XRDP:

After boot to Desktop has been activated, the actual installation of the Remote Desktop Server follows. Under Linux, XRDP is a free implementation of the Remote Desktop Protocol. We can install these directly using the package manager APT. When the installation is complete, the XRDP daemon starts automatically.

The basic installation is already done. In the future, the XRDP server will be started automatically in the background when the system is started.

If necessary, the XRDP settings in the files /etc/xrdp/xrdp.ini and /etc/xrdp/sesman.ini can still be adjusted. However, this is not mandatory and may only be required in special applications. That’s why I’m not going to go into that.

Step 3: Reboot

Windows To Linux Rdp

A restart of the Raspberry Pi is recommended to complete the setup:

Step 4: Remote Desktop Client

To be able to access the Raspberry Pi remotely, we need a corresponding remote desktop client software on the client.


As already mentioned in the introduction, Windows comes with a suitable client. You can find it under:
All Programs -> Accessories -> Remote Desktop Connection

Mac OS X

If you have installed MS Office for Mac, you will find the Microsoft Client at “Applications → Remote Desktop Connection”. Otherwise it can be downloaded via iTunes – Microsoft Remote Desktop.


For other operating systems the following clients are available:

Linux: RDesktop
Android: Microsoft Remote Desktop
Apple iOS: Microsoft Remotedesktop

Step 5: Establishing a Remote Desktop Connection

To establish a remote desktop connection with the Raspberry Pi, we must first specify its IP address.

After we click on Connect, we get a login screen from the XRDP server of our Raspberry Pi. The access data are identical to those for SSH. If the user or password has not been changed under Raspbian, the default user is pi and the password is raspberry.

After successful registration we can already see the desktop of the Raspberry Pi after a few seconds and operate it with mouse and keyboard.

My recommendations were helpful?
Then just say 'thank you' with a coffee!

Rate this Post:
4.45/5 (11 votes)

Raspberry Pi – Install Remote Desktop (XRDP), 4.45 out of 5 based on 11 ratings

Xrdp Client Windows 10


Xrdp Windows Client Download

You may also like: