Install Xrdp on Ubuntu 20.04 LTS

 

This page has a nice workaround to try with a black screen on XRDP.  Need to figure out how it works, but nice to have it.

https://www.tecmint.com/install-xrdp-on-ubuntu/

Edit /etc/xrdp/startwm.sh

Add these lines just before the lines that test & execute Xsession as shown in the screenshot below.

unset DBUS_SESSION_BUS_ADDRESS

unset XDG_RUNTIME_DIR

restart Xrdp

systemctl restart xrdp

retry remote login.

--30--

xrdp on debian 9 notes.

 

Install xrdp xfce4 and vnc

 

apt install -y xrdp tigervnc-standalone-server

problem with xrdp.ini having autorun= default to the Session ID rather than reasonable value

change the autorun= to add autorun=Xvnc

 

cant seem to run Xorg session, but with xvnc installed works okay

 

upstream error

https://github.com/neutrinolabs/xrdp/issues/750

 

original error in Fedora 24

https://bugzilla.redhat.com/show_bug.cgi?id=1450681

 

error message is:

 /var/log/xrdp.log shows [ERROR] xrdp_wm_log_msg: Section "HPC15" not configured in xrdp.ini

install xsession and xsessionrc as follows

https://www.hiroom2.com/2018/05/07/ubuntu-1804-xrdp-xfce-en/

another file on debian 9 xrdp

https://ekozel.com/2019/10/05/setup-remote-desktop-xrdp-on-debian-9/

https://portal.databasemart.com/kb/a457/how-to-install-desktop-environment-and-xrdp-service-in-debian-9.aspx

 

 

 

 

--30--

install gnome-disks and xfce-terminal

Gnome-disks is installed by the package

 

sudo apt -y install gnome-disk-utility

 

xfce4's terminal isn't installed.  Sometimes the "open in terminal" fails, so install the xfce4 terminal.  It will show up in the system tab

 

apt -y install xfce4-terminal

 

 

--30--

xrdp and xfce4 problems on Ubuntu 18.04.4 release (started in 18.04.2)

described here:
https://github.com/microsoft/linux-vm-tools/issues/49

more info here, matches problem:

https://github.com/microsoft/linux-vm-tools/issues/76

This install fixed the problem on ubuntu 18.04.4

apt-get -y install xorgxrdp xorg-video-abi-23 xserver-xorg-core

cluster fuck

--30--

XRDP failure log message: connecting to 127.0.0.1 5910 error - problem connecting

The messages

connecting to sesman ip 127.0.0.1 port 3350
sesman connect ok
sending login info to sesman
login successful for display 10
started connecting
connecting to 127.0.0.1 5910
error - problem connecting

Printed in the dialog box when attempting to connect to an XRDP enabled system.

The latter problem implies a connectivity problem, which couldn't be further from the cause.

Many sites insist that installing XRDP, vncserver (of some sort) in one order or another is the problem.  Also misleading.

Then you look in xrdp-sesman-log in /var/log, you will see this

[INFO ] starting Xvnc session...
[ERROR] X server for display 10 startup timeout
[INFO ] starting xrdp-sessvc - xpid=3531 - wmpid=3530
[ERROR] X server for display 10 startup timeout
[ERROR] another Xserver is already active on display 10
[DEBUG] aborting connection...[20130627-08:55:49]
[INFO ] ++ terminated session:  username root, display :10.0, session_pid 3529, \

      ip 192.168.0.227:59050 - socket: 7

Indicating that somehow your RDP session has two Xservers active.  What happens when you log in is that a login method is performed to authenticate, and the top dialog indicates the progress of that.

Then it will spawn some VNC server session for the X session (uses 10, 11, etc.) to connect.

If you read the symptoms here, there is already a session or server on 5910.  Completely wrong.

To find the problem, one has to try running the window manager.  I don't know if this would happen for other than xfce4, which I use, but it produces the root problem.  run:

If you try running vncserver, you will see at the end of the startup this:

[dix] Could not init font path element /usr/share/fonts/default/Type1, removing from list!
[dix] Could not init font path element built-ins, removing from list!

Fatal server error:
could not open default font 'fixed'

Turns out that if any failure occurs in the chain of events between the authentication after the RDP login and getting the session going, you get the " Xserver is already active on display" message in the var log sesman log.

Other errors I suspect produce the same nonsense, someone reported when the vnc server and client couldn't agree on a geometry, the same error occurred.

This is probably the solution to all the load order issues and which vnc server (real or tight) package you use.

quoting:
I have solved it by installing xfonts-base

This also solved my problem.

xfce4 background, and linux command line xml parse example

http://unix.stackexchange.com/questions/131238/where-is-the-current-wallpaper-stored


xml script example

#!/bin/bash -

# taken from
#  http://unix.stackexchange.com/questions/131238/where-is-the-current-wallpaper-stored
# must install xmllint
# /usr/bin/xmllint      libxml2-utils

#
# define xfce4 xml file that holds info about desktops 
# 
DESKTOP="/home/$(id -un)/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml"
#
# define xpath that will extract current desktop background file name
# (NB I am no expert in xpaths and there is probably a much more elegant way
#  to do this but this works for me)
#
XPATH='(//property[@name="workspace0"]/property[@name="last-image"])[last()]/@value'
#
# use xmllint utility to apply xpath to file and extract file path and name
#
IMAGE=$(xmllint --xpath "string(${XPATH})" "${DESKTOP}")
#
# display the file info extracted
#
echo Current Wallpaper File = ${IMAGE}
#
# rest of script........
#

xx

XFCE window manager tab setting switch window key

XFCE on cubox comes with a setting such that the tab character switches windows, rather than auto completing.

info on this page:

http://ubuntuforums.org/archive/index.php/t-1771058.html

Also

http://stackoverflow.com/questions/23418831/command-line-auto-complete-tab-key-not-work-in-terminal-for-ubuntu

Without changing any settings, use control-i to autocomplete.

Try using Ctrl-I instead of tab

For changing the setting in the XFCE xml config:

edit
~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml

find the line 

<property name="&lt;Super&gt;Tab" type="string" value="switch_window_key"/>

and change it to 

<property name="&lt;Super&gt;Tab" type="empty"/>

reboot or whatever and then tab will work properly!

I have no idea why but when using vnc this file seems to override tab's normal behavior and makes it into a switch window key.

On Ubuntu 14.04, the xfce4 somehow resets the xfce4-keyboard-shortcuts.xml file each time you log in, so one needs a method to change the default

the Window manager keyboard shortcuts don't include a setting for the tab-complete Super tab, so it must be edited somewhere else.

Explanation of how to find and change what settings are in the Window Manager->Keyboard tab is here

http://forum.xfce.org/viewtopic.php?id=8860

Found explanation:
change "Switch window for same application" to clear from "alt tab"

xx