Running Xrdp on Ubuntu
-
There has been a few threads on running Xrdp on Fedora,.. but of the ones I've found that are close are for Mint...
I realize it shouldn't be much different on getting it configured. However, for whatever reason, I have not been able to get it configured so that I can connect to it from Windows 10.
Any thoughts - I've used in the past, and it' worked fine...
-
need more info. How far along are you getting?
-
Are you just wanting RDP from Ubuntu to Windows? I use Remmina on Fedora with Cinnamon.
-
@JaredBusch said in Running Xrdp on Ubuntu:
Are you just wanting RDP from Ubuntu to Windows? I use Remmina on Fedora with Cinnamon.
I think that he is trying to run XRDP, the server.
-
@JaredBusch said in Running Xrdp on Ubuntu:
Are you just wanting RDP from Ubuntu to Windows? I use Remmina on Fedora with Cinnamon.
Remmina works perfectly when going from Ubuntu to Windows. The only exception is when I access a Windows system that has dual screens. Not found a way to switch screens as of yet.
No, in this case, I want to go from Windows to Ubuntu.
-
@scottalanmiller said in Running Xrdp on Ubuntu:
need more info. How far along are you getting?
The install was fine,.. nothing complicated there. But when I go to connect from WIndows, I get the XORG screen to sign in,.. but then it either goes to a black screen or just disconnects.
-
-
@scottalanmiller said in Running Xrdp on Ubuntu:
@JaredBusch said in Running Xrdp on Ubuntu:
Are you just wanting RDP from Ubuntu to Windows? I use Remmina on Fedora with Cinnamon.
I think that he is trying to run XRDP, the server.
Ah, read that backwards. Apparently, I need more coffee.
-
Have you tried looking in /etc/X11/Xwrapper.config ?
Make sure that you have...
allowed_users = anybody
-
Is your VNC server running correctly? Use
netstat
to see if it is listening. -
There's a couple of things to check.
The first and foremost is make sure your distro is using X and not Wayland. Someone here pointed out the right file to check for that. In Fedora, You check
/etc/gdm/custom.conf
, you uncomment the line #WaylandEnable=falseThanks to @black3dynamite for the pointers on Fedora.
I'll echo @StrongBad 's suggestion to check
/etc/X11/Xwrapper.config
-- if it doesn't exist, then create it with the settings he listed.You will also have better performance with a desktop environment like MATE or XFCE, rather than Cinnamon or Gnome.
-
Also, what version of Ubuntu are you using?
-
Ran into this tonight ...
-
@dafyre said in Running Xrdp on Ubuntu:
Also, what version of Ubuntu are you using?
~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic
-
@StrongBad said in Running Xrdp on Ubuntu:
Have you tried looking in /etc/X11/Xwrapper.config ?
Make sure that you have...
allowed_users = anybody
It was set as
allowed_users=console
updated.
-
Post change - Repeats,.. can't get out of it asking... but - step forward...
-
Ha... joy
Can't even sign in at the local. Select UserName, enter password, repeats.... sigh..
FML
-
uname -r 4.15.0-45-generic
gjacob@TSG:~$ sudo apt-get autoremove --purge Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up grub-efi-amd64-signed (1.93.11+2.02-2ubuntu8.10) ... /boot/vmlinuz-4.15.0-43201901161620-generic is unsigned. E: Your kernels are not signed with a key known to your firmware. This system will fail to boot in a Secure Boot environment. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: grub-efi-amd64-signed E: Sub-process /usr/bin/dpkg returned an error code (1)
gjacob@TSG:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+' rc linux-image-4.15.0-29-generic 4.15.0-29.31 amd64 Signed kernel image generic rc linux-image-4.15.0-43-generic 4.15.0-43.46 amd64 Signed kernel image generic ii linux-image-4.15.0-44-generic 4.15.0-44.47 amd64 Signed kernel image generic ii linux-image-4.15.0-45-generic 4.15.0-45.48 amd64 Signed kernel image generic
-
Before I say anything more, I have a question... Is this a system that's you're going to use locally and remotely, or will you be using it via RDP mostly?
-
@dafyre said in Running Xrdp on Ubuntu:
Before I say anything more, I have a question... Is this a system that's you're going to use locally and remotely, or will you be using it via RDP mostly?
For the now, it's sitting right here next to my desktop. But the idea is to be able to remote both ways (remmina works fine to Windows) so I only need to use the one keyboard/mouse/monitor(s).
I could use VNC - if I could get it to work... but for some reason it's 'failing'..
now,.. reversing the recent update/ installs I've done I get:
Setting up grub-efi-amd64-signed (1.93.11+2.02-2ubuntu8.10) ... /boot/vmlinuz-4.15.0-43201901161620-generic is unsigned. E: Your kernels are not signed with a key known to your firmware. This system will fail to boot in a Secure Boot environment. dpkg: error processing package grub-efi-amd64-signed (--configure): installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1 Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for man-db (2.8.3-2ubuntu0.1) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Errors were encountered while processing: grub-efi-amd64-signed E: Sub-process /usr/bin/dpkg returned an error code (1)
Looking at the listed kernels now:
:~$ dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+' rc linux-image-4.15.0-29-generic 4.15.0-29.31 amd64 Signed kernel image generic rc linux-image-4.15.0-43-generic 4.15.0-43.46 amd64 Signed kernel image generic pi linux-image-4.15.0-44-generic 4.15.0-44.47 amd64 Signed kernel image generic pi linux-image-4.15.0-45-generic 4.15.0-45.48 amd64 Signed kernel image generic
Odd that 44 and 45 were listed as
ii
and now so aspi