Uninstall Xrdp

[Frederic Laureano]

HiI installed xrdp a while back and it worked fine, I then tried to follow this tutorial to enable the clipboard ( -nergy.be/blog/?p=9285). I could then no longer RDP into the server and only connect via Putty.

To provide additional information about how to remove the xrdp files when performing a custom installation, there is in fact a post that has been published in December 2017 (please check here -nergy.be/blog/?p=11454)

I installed Ubuntu 20.04 and then installed xrdp. Whenever i tried to connect, either from another Ubuntu 20.04 box using either xfreerdp or krdc, or from a Mac, a black screen would show up, and then immediately disconnect. i made sure i did not have any other sessions on the server going on at the same time.

If you get a Warning Message [Authentication is required to create a color managed device] while connecting to the Ubuntu server through Xrdp, you need to execute the following commands to ignore it:

This is a big problem to many useres.I found out an error on my systems.I am using 2 Odroid C2 computers. I had the same issues. I installed from scratch and everything was ok. Then i did something not related to Remotedesktop and after that i could not log anymore.The last time i had the system working fine and i changed the IP adress from xxx.xxx.xxx.094 to xxx.xxx.xxx.096I could not log in via Remotedesktop.I had the second system running good, so i startet to compare filesin my case the /etc/xrdp/startwm.sh had a complete different content. It looked like it was copied over with a different text.Unfortunetly i got not further in it.I restored this file and now it is working fine again.There are so many tips for this problem, so just check that file.

It is a password complexity and language problem. Around 2019-2020 the rules for password authentication for user accounts are pushed up. I think in Debian other than Ubuntu. But anyway the XORG stuff is pretty old and maintenance rare, it seems to me that leads into some issues and I assuming the following.

There are some more traps for i.e. german users or other with non english keyboard layout. Because the Xorg authentication window always use the englisch layout. This leads to some restriction for your password because the most of the special characters (!"&..) are at different positions on non englisch layout keyboards. Also Y and Z are reversed in german layouts.

Having the devil of a job getting XRDP working! Can anyone offer any advice?

It is a clean install of 11.1 and I then added the XRDP components using the YaST software manager. After some (quite a lot actually) debugging, I have this information. Is it enough?

On 09/30/2009 08:26 PM, martinprowe wrote:

>

> Having the devil of a job getting XRDP working! Can anyone offer any

> advice?

> It is a clean install of 11.1 and I then added the XRDP components

> using the YaST software manager. After some (quite a lot actually)

> debugging, I have this information. Is it enough?

The difference I can detect is in the user credential screen - you can now change the session type field without clearing username/passwd. Neat. But what has not changed is the underlying authentication/connection issue?

Now the remote log records an extra (to that shown in the earlier posting) connection to itself on port 5910. My suspicion is that this is just an improvement in the status display and only indicates that the xrdp wrapper is linking to the vnc service?

TerminalServerUsers=tsusers

Only the users belonging to the group tsusers are allowed

to login on terminal server.

If unset or set to an invalid or non-existent group,

login for all users is enabled.

Just a very quick last question (if you are still monitoring this): can you confirm that you opened the firewall for xrdp or that you have the network connection on the internal zone? I only ask since I had no trouble with xrdp apart from trying to establish a Failsafe Terminal connection from the session type list. However KDE4 sessions worked fine.

Installed init script for VNC Server in Virtual Mode daemon

Start and stop the service with:

/etc/init.d/vncserver-virtuald (startstop)

Use chkconfig to start or stop the service at boot time.

I have not been able to uninstall this Component. I have tried the ubuntu way ( -to-uninstall-real-vnc-in-ubuntu-14-04), but it did not work to install deb and use dpkg to uninstall. I cannot use rpm either.

I have not been able to uninstall this Component. I have tried the

ubuntu way

( -to-uninstall-real-vnc-in-ubuntu-14-04),

but it did not work to install deb and use dpkg to uninstall. I cannot

use rpm either.[/color]

Hey,

I want to set up an XRDP/VNC server on my personal computer which is running the latest Arch linux (X64).

I wanted to use xrdp as I am going to connect to my computer from a windows based OS (work).

I want to be able to do so using microsoft's RDP program (mstsc) as I am unable to install any software I like, it's a laptop from work.

So now that we have Xvnc running properly, lets go to sourceforge and gank the latest xrdp tar ball...

I used the standard install (generic linux install) with "tar zxvf" then "make" and then "make install"

If you are using KDE, you should be all set, if another WM, then search through the forums (Ubuntu had several hits on xrdp and are Gnome specific) as I would more then likely steer you in the wrong direction.

I'd just use a normal tightvnc/x11vnc setup (tunnelled over SSH), and then get the tightvnc viewer without the installer, and throw it on a usb drive, this is what i currently do.

I have a portable firefox,portable pidgin, and tightvnc all on a flash drive, and i use SSH tunneling for all connections to my home box. So i can run firefox/pidgin locally without them being installed, and tunnel all traffic securely throguh my home computer, and when i need to i just start up x11vnc and use tightvnc to connect. (All traffic tunneled through SSH).

Many users are working on multiple operating systems on numerous machines, so carrying all these machines all the time is not feasible. Remote Desktop is used to connect different operating systems like Debian from remote locations. It enables the user to connect to the network and access all your resources from a single machine across the globe.

The desktop environment is required to install the remote desktop on the host machine and connect to the RDP using it. Now, use the following command to get the xfce4 and xfce4-goodies desktop environment on the Debian machine:

The snippet below shows the results of the above command containing the IP address with the broadcast address. Now, simply copy the IP address and store it, so it can be used to connect from other machine:

To use the Debian machine on the Remote Desktop, open the terminal to Debian 12 to install the xfce desktop environment. After that, open its terminal to install the xrdp on the Debian machine and configure it to start the xfce environment at the time of remote connection. Also, configure the Uncomplicated Firewall by adding the xrdp user to it and add the port number as the firewall rule. After that, simply open the Remote Desktop Connection from the client machine and use the IP address of the Debian to establish the connection.

I got a new computer (client), an apple silicon mac (macos 13) if that makes a difference.On the old computer, rdp to this server (debian) worked OK.From the new computer the first time I tried I got an xrdp login error as I did not save the password correctly .After fixing the password, rdp connection goes now directly to entirely black screen, the mouse cursor still looks like the mac's cursor when I move over the rdp window or click on it.Oddly, the rdp screenshot updated correctly to show my debian's desktop during the first few tries, now it doesn't anymore, not sure if I canged something.

EDIT: SOLVED, I think. I installed gdm3 then performed a full firmware upgrade from armbian-config. Performed a reboot and now I have an X desktop over RDP. It's working. I wonder if I cheated and lightdm is still broken and using gdm3 is simply a cheats way out. Why would lightdm not work would still be interesting investigating.

Installing xfce4 and xrdp on a now (rest in peace) original version 1 Rasberry Pi B want without a hitch. Installed xrdp, then installed xfce4, made it the default desktop environment and it worked. This was to replace the Raspian desktop which was choking the original Pi. Well... It did just have 256Mb RAM in absolute total. This BananaPi Pro has 1Gb. More wiggle room.

xrdp seems to be working. It will time out, give me the connection log, goes back to the login box within the RDP session and when I click on cancel, the Remote Desktop client quits. I genuinely do not know where the problem lies and how to effectively diagnose this.

Which VNC server are you using with xrdp? I read a post a while back that said there was issues with one and when I switched it worked well for me. If I remember correctly TightVNC might be the one to use.

I have an Xubuntu 9.10 Karmic Koala VM set up within VMware ESX to test out xrdp. xrdp appears to appropriately start up when Xubuntu is booted. When I try to RDP to the VM (it has a DHCP address), I get the following messages: connecting to...

This is the procedure I have followed to successfully setup Xrdp on Garuda KDE Dr460nized. It has not been easy, so I guess it is a good thing to share it in case it may help other Garuders (maybe even users of other Arch Linux derivatives).

The first problem I ran into was that the aur/xrdp package, once running, reported the following journal error: xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc.so or similar.

3a8082e126