Showing posts with label xfce4. Show all posts
Showing posts with label xfce4. Show all posts

Thursday, August 19, 2021

install xrdp for remote desktop on friendlyarm ubuntu version, focal 20.04.

Must translate thru google translate.  Translated version copied and pasted here.

XRDP with xorg doesn't work, probably due to missing hardware to frame buffer.  Seems to rig to use vnc remote desktop method to  remote the desktop.

Installed xfce4 for window manager

<run following thru google translate for updated info>
snapshot copied and saved 8/19/2021

https://wiki.friendlyarm.com/wiki/index.php/How_to_setup_XRDP_server_on_NanoPC-T4


How to setup XRDP server on NanoPC-T4

View Chinese

1 Step1: Install XRDP remote desktop

Enter the following command to install:

sudo apt install  -y tigervnc-standalone-server xrdp
 sudo  sed  -e  's/^new_cursors=true/new_cursors=false/g'  -i  / etc / xrdp / xrdp.ini

2 Step2: Edit /etc/xrdp/startwm.sh

Edit /etc/xrdp/startwm.sh:

sudo  vim  / etc / xrdp / startwm.sh

Comment out the last two lines in the file (comment method: add # sign at the beginning of the line), as shown below:

# test -x /etc/X11/Xsession && exec /etc/X11/Xsession 
# exec /bin/sh /etc/X11/Xsession

Then add the following at the end of the file:

lxsession -s LXDE -e LXDE

3 Step3: Edit /etc/xrdp/xrdp.ini

Edit /etc/xrdp/xrdp.ini

sudo  vim  / etc / xrdp / xrdp.ini

Scroll to the address of "; Session types", delete all other session types, only [Xvnc] is left:

;
; Session types
;
; 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.
 [ Xvnc ] 
name =Xvnc
 lib =libvnc.so
 username =ask
 password =ask
 ip =127.0.0.1
 port =- 1 
#xserverbpp=24 
#delay_ms=2000

4 Step4: Disable light-locker

Since light-locker will not work properly in the XRDP environment, we need to disable it in the XRDP environment. In order not to affect the real environment, here we use a packaging script to solve the problem. First, rename the original file:

the sudo  CP  / usr / bin / Light-Locker / usr / bin / Light-locker.orig
 the sudo  RM  / usr / bin / Light-Locker

Create another script to call it, and use the editor to create a file /usr/bin/light-locker with the following content:

#!/bin/sh
 
# The light-locker uses XDG_SESSION_PATH provided by lightdm. 
if  [  !  -Z  " \$ {XDG_SESSION_PATH}"  ] ; then 
  / usr / bin / light-locker.orig
 else 
  # Disable light-locker in XRDP. 
  true 
fi 
EOF

Give the script executable permissions:

sudo  chmod  755  / usr / bin / light-locker

5 Step5: Start xrdp service

sudo systemctl enable xrdp
 sudo systemctl restart xrdp

6 Step6: Test the remote desktop connection

Use the Microsoft Remote Desktop client to create a new connection, the address is the IP address of the development board, and the user name and password are pi. In order to get a better experience, the resolution is recommended to be set to 1280x800, and the color depth is 24 bits. The settings are as shown in the figure below. Shown:

  • Xrdp-ip.png
  •  
  • Xrdp-settings.png

After the connection is successful, as shown in the figure below:
Win-xrdp-friendlydesktop.png


--30--

Thursday, May 20, 2021

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--

Saturday, January 11, 2020

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--

Monday, January 22, 2018

install xwindows and xfce4 on Windows 10 + Ubuntu (creators version)


However, you can install graphical Linux applications and run these under WSL if you have an X server like VcXsrv or Xming, on your Windows machine. 

https://solarianprogrammer.com/2017/04/16/windows-susbsystem-for-linux-xfce-4/


a bit from the above link

1 sudo apt install xfce4
Next, you will need to modify the .bashrc file. There are a few text editors that work under WSL. I suggest to use vim or nano, e.g.:
1 cd ~
2 nano .bashrc
The second command from above will open .bashrc in nano and you can scroll to the end of the file and write:
1 export DISPLAY=:0.0
Save the modified file by pressing CTRL+X and answering Y when asked if you want to save the file. Close and restart the console window.
Next, you will need to install an X server for Windows. I suggest VcXsrv which works well with WSL. Download and start the installer, you can safely accept the default settings.

https://sourceforge.net/projects/vcxsrv/

https://sourceforge.net/projects/xming/

Sunday, August 6, 2017

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.