Vnc error problem connecting some problem centos

Hello, I have installed and used xrdp on a centos 7.0 + gnome. I used this resource https://draculaservers.com/tutorials/install-xrdp-centos/ for install xrdp. I always used session Xorg for login ...

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp. I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1
  • Ensure the OS is up to date with sudo yum update

  • Install EPEL repository with sudo yum install epel-release

  • Install and enable XRDP with:-

    sudo yum install xrdp
    sudo systemctl enable --now xrdp
    sudo systemctl enable --now xrdp-sesman
    
  • If you’re using the firewall, allow external access to TCP port 3389 with:-

    sudo firewall-cmd --add-port=3389/tcp --permanent
    sudo firewall-cmd --reload
    
  • If you’re using SELinux, sudo yum install xrdp-selinux

  • If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

    • sudo yum install xorgxrdp
    • Edit /etc/xrdp/xrdp.ini. If the [Xorg] section is commented out, uncomment it.
    • If you changed xrdp.ini, sudo systemctl restart xrdp to pick up the changes.
  • Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall "MATE Desktop".

  • The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

    # This file is read by /etc/X11/xinit/Xclients if the user does not
    # override it - see /etc/X11/xinit/Xsession for details
    
    # Set the default desktop for all users
    PREFERRED=mate-session
    
  • XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to ~/.xsession or ~/.Xclients . For MATE, this command is adequate:-

    ln -sf /usr/bin/mate-session ~/.xsession
    

    As an aside, some websites suggest creating a vanilla file ~/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

  • Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):-
    sudo yum install gdm
    sudo systemctl set-default graphical
    sudo systemctl isolate graphical
    
  • When using the Xvnc backend, you may need to set the colour depth on the client to 24 or 32 if the desktop, or the applications require mesa 3D support. The Xorg backend always runs at a suitable colour depth.

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

xrdp screenshot.jpg
xrdp screenshot.jpg (72.36 KiB) Viewed 39453 times

The components I am using include:

Code: Select all

Windows:	Remote Desktop Connection Shell Version 6.3.9600 (Supports Network Level Authentication and RDP 8.1)
Linux:	CentOS Linux release 7.2.1511 (Core)
Linux:	xrdp.x86_64 version 1:0.9.0-4.el7 from @epel
Linux:	tigervnc.x86_64  version 1.3.1-9.el7  from @base
Linux:	tigervnc-server.x86_64 version 1.3.1-9.el7 from @base

My xdrp.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51143
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51143 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 8
[20170108-19:19:04] [ERROR] Listening socket is in wrong state we terminate listener
[20170108-19:19:04] [INFO ] A connection received from: 10.0.0.154 port 51144
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [CORE ] WARNING: Invalid x.509 certificate path defined, default path will be used: /etc/xrdp/cert.pem
[20170108-19:19:04] [WARN ] Invalid X.509 certificate path defined, default path will be used: /etc/xrdp/key.pem
[20170108-19:19:04] [DEBUG] xrdp_00001058_wm_login_mode_event_00000001
[20170108-19:19:04] [WARN ] local keymap file for 0x0409 found and dosen't match built in keymap, using local keymap file
[20170108-19:19:04] [DEBUG] returnvalue from xrdp_mm_connect 0
[20170108-19:19:07] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:08] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:09] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:10] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:11] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:12] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:13] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:14] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:15] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] VNC Error after security negotiation
[20170108-19:19:16] [DEBUG] VNC error before sending share flag
[20170108-19:19:16] [DEBUG] VNC error before receiving server init
[20170108-19:19:16] [DEBUG] VNC error before receiving pixel format
[20170108-19:19:16] [DEBUG] VNC error before receiving name length
[20170108-19:19:16] [DEBUG] VNC error before receiving name
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 12
[20170108-19:19:16] [DEBUG] xrdp_mm_module_cleanup
[20170108-19:19:16] [DEBUG] VNC mod_exit
[20170108-19:19:16] [INFO ] An established connection closed to endpoint: 127.0.0.1:3350 - socket: 11

My xrdp-sesman.log sequence for the failed session is as follows:

Code: Select all

[20170108-19:17:18] [WARN ] [init:46] libscp initialized
[20170108-19:17:18] [CORE ] starting sesman with pid 4180
[20170108-19:17:18] [INFO ] listening...
[20170108-19:19:04] [INFO ] A connection received from: 127.0.0.1 port 38634
[20170108-19:19:04] [INFO ] scp thread on sck 8 started successfully
[20170108-19:19:04] [INFO ] ++ created session (access granted): username brian, ip 10.0.0.154:51144 - socket: 8
[20170108-19:19:04] [INFO ] starting Xvnc session...
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 9
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: NULL:NULL - socket: 7
[20170108-19:19:04] [INFO ] An established connection closed to endpoint: 127.0.0.1:38634 - socket: 8
[20170108-19:19:04] [ERROR] env_set_user: error creating .vnc dir
[20170108-19:19:04] [INFO ] Xvnc :11 -geometry 1280x768 -depth 24 -rfbauth /home/brian/.vnc/sesman_brian_passwd -bs -nolisten tcp -localhost -dpi 96 -depth 24  
[20170108-19:19:05] [INFO ] starting xrdp-sessvc - xpid=4188 - wmpid=4187
[20170108-19:19:05] [INFO ] ++ terminated session:  username brian, display :11.0, session_pid 4186, ip 10.0.0.154:51144 - socket: 8

I would be grateful if a community member more skilled than I (which I suspect is just about everyone) could provide some guidance in resolving this connection problem. I can provide additional .ini configuration information if that would be helpful. Thanks!

Содержание

  1. CentOS
  2. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  3. Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  4. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  5. Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»
  6. Vnc Error — Problem Connecting #2086
  7. Comments
  8. login successful for display 10. VNC error — problem connecting some problem #1459
  9. Comments

CentOS

The Community ENTerprise Operating System

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/08 20:00:10

With the help of Centos forum resources, I added GUI (MATE Desktop) support to a dedicated Centos 7 web server (Centos 7 Live DVD — Can Gnome/GUI be installed later? viewtopic.php?f=47&t=60762).

While the MATE desktop is a convenient addition to the main server console, I would also like to provide remote GUI capability to my main workstation which is a Windows 7 desktop. I am trying to connect remotely to the MATE desktop using a Windows Remote Desktop client on the Windows side and xrdp on the Centos side, but am encountering a «some problem» VNC connection error which I think is coming from the Centos side:

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by BGood » 2017/01/09 17:21:48

Re: Windows Remote Desktop/Centos 7 xrdp connection fails with «some problem»

Post by FAB5FLAVE » 2017/08/23 15:19:27

Installed xdrp and tigervnc windows RDP connected no problem.

Installed MATE Desktop got the same «some problem» error when trying to connect.

Tried numerous things to get this working like changing port number, reinstalling xdrp and tigervnc etc.

Eventually resolved the issue by removing xrdp and tigervnc and reinstalling

yum remove xrdp
yum remove tigervnc-server.x86_64
yum remove tigervnc-server-minimal.x86_64
reboot

systemctl start xrdp

Didn’t start
systemd[1]: Started xrdp daemon.
systemd[1]: Starting xrdp daemon.
systemd[3144]: Failed at step EXEC spawning /usr/sbin/xrdp: Permission denied
systemd[1]: xrdp.service: main process exited, code=exited, status=203/EXEC
systemd[1]: Unit xrdp.service entered failed state.
systemd[1]: xrdp.service failed.

So ran the following
chcon -t bin_t /usr/sbin/xrdp
chcon -t bin_t /usr/sbin/xrdp-sesman

Источник

Vnc Error — Problem Connecting #2086

Im experiencing the following error with the tool xrdp in a suse 15 sp1 machine in azure, I just wanna know is someone has seen it before.

Please wait, we now perform access control.
Reply from access control: Sucess
connecting to sesman ip 127.0.0.01 port 3350
seman connect ok
sending login info to session manager, please wait.
login successful for display 201
VNC started connecting
waiting 2000 ms for VNC to start.
VNC connecting to 127.0.0.1 6101
VNC error — problem connecting
some problem

The text was updated successfully, but these errors were encountered:

@jsanchezzz — these two lines look odd:-

Have you changed the X11DisplayOffset=10 setting in sesman.ini? It looks like it’s set to around 200, which probably won’t work.

@jsanchezzz — do you need any more help with this?

@matt335672 yes, I reinstalled the xrdp, but it showing the same error. Also I did not change the X11DisplayOffset=10, how can i see if the X11DisplayOffset has changed somehow?

It’s in /etc/xrdp/sesman.ini :-

Hello as you said the X11DisplayOffset is set to 200, and we dont know why? could you tell us how to change it to 10, please? see the image attached.

Well, you seem to have two problems here

The first problem is solved by editing /etc/xrdp/sesman.ini , correcting the value, and restarting the xrdp-sesman service.

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.

We changed the parameter but it did not work, We did a deeper investigation to know why the rdp is not working and we entered the logs, we saw something about a certificate, I would like to know if you have any knowledge, because the certificate is installed but the vm does not find it.

see the images attached and the notepad.
log JS.txt

If you don’t have a certificate, xrdp will fall back on a less secure connection method, so I’d expect it still to work. I think you should leave that for now.

A couple of questions for you:-

  • What version of xrdp is installed?
  • What desktop have you installed on the machine?

What version of xrdp is installed?

What desktop have you installed on the machine?

linux suse 15 sp1

«Linux SuSE 15 sp 1» isn’t what I’d call a desktop. I mean, are you running GNOME or KDE (or similar)? You’ll need a desktop installed for xrdp to start. Do you have one installed?

As far as the certificate error goes

I’ve checked the sources for 0.9.6 and it’s telling me that either /etc/xrdp doesn’t exist on that machine, or /etc/xrdp/cert.pem doesn’t exist on that machine. What do you get on the machine for these two command when logged in as root:-

We solved the problem:

1 — Performing a clean installation of patterns-gnome-gnome_basic
2 — Allowing remote sesion with remote manager
3 — Installing xrdp xorgxrdp
4 — enabling the vm firewall and open the port 3389 ( systemctl enable firewalld, systemctl startd firewalld firewall-cmd —permanent —zone=public —add-port=3389/tcp )

Thanks for you support, it was rellay heplful to solve the issue.

Thanks for letting us know.

Did you get your certificate problem sorted out too?

Jumping into this conversation 3 years later.

I’m not asking a question here, but trying to add something to the quoted observation below:

The second and more serious problem is that you’ve got a file on your system which needs privilege to change and something unknown has changed it. That’s not a good position to be in. Not only do we not know what else might have changed in the xrdp configuration, but there might be other files which have changed that could affect system operation. So I think it’s worth trying to figure out how this file could have changed.
— matt335672

I’ve observed the same issue. The configuration at /etc/xrdp/sesman.ini says that the default is 10 but I see 200.
I’m not sure what changed this configuration.

However, I’ve observed something peculiar:

I’m running OpenSUSE Tumbleweed in a VM under Hyper-V under Windows11. Unfortunately I have to use Windows 🙁

I have GWSL, which is a Xserver with some tweaks intended to make life easier if you are using WSL. But I’m not using OpenSUSE under WSL; I’m using OpenSUSE under a VM, under Hyper-V.

Then I have two choices for opening a RDP session: (a) using GWSL or (b) using Remote Desktop Connection, which is native to Windows11.

I’ve discovered that GWSL employs/requires DISPLAY=:10.0 whilst Windows Remote Desktop Connection employs/requires DISPLAY=:200.0

I can open KDE full screen using GWSL, but I have to open first a ssh session and then run startplasma-x11 from it, which is inconvenient, but works.

However, I cannot open KDE full screen using Windows Remote Desktop Connection. But I’ve discovered that it starts to work fine if I first open a GWSL connection. In other words: if I open first a window with KDE in it via GWSL, after that, I can open another window running KDE in it via Windows Remote Desktop Connection. In this case, applications running in the first window employ DISPLAY=:10.0 whilst application in the second window employ DISPLAY=:200.0 .

Needless to say that I don’t understand why it behaves this way.

Seems like the RDP server for display 10 works like a transport layer for the RDP server for display 200. The evidence is: if I close the RDP server for display 10 (i.e.: I close GWSL), the window containing applications associated to display 200 stop working after 10 seconds and the entire KDE session dies.

I would prefer to use WIndow Remote Desktop Server, since it performs better. But, as explained, it will require GWSL for some unknown reason. which forces me to use GWSL anyway.

Trying to answer the question «who changed X11DisplayOffset=10 to X11DisplayOffset=200». my guess is package hyper-v , installed automatically on OpenSUSE when the VM is first installed. I’m not sure though. Just a guess.

Источник

login successful for display 10. VNC error — problem connecting some problem #1459

I have installed and used xrdp on a centos 7.0 + gnome. I used this resource https://draculaservers.com/tutorials/install-xrdp-centos/ for install xrdp.
I always used session Xorg for login because of xrdp never worked with Xvnc session

A few days ago I have updated a linux with command sudo yum update
After the update, the menu Xorg disappeared from Session list and when I used Xvnc session I get an error — Login successful for display 10. VNC error — problem connecting some problem

I googled a lot and read and tried a lot of solutions for the fix issue but without success.

The text was updated successfully, but these errors were encountered:

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.

I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.

I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

The issue was not solved.

]# rpm -q centos-release
centos-release-7-7.1908.0.el7.centos.x86_64

]# getenforce
Enforcing
[root@localhost

]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
[root@localhost

I have installed:
xrdp-selinux.x86_64 1:0.9.11-5.el7

I have added the sesman.ini file to this post.
sesman.txt

Output for Xvnc :10
[root@localhost

Xvnc TigerVNC 1.8.0 — built Aug 9 2019 03:04:19
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12001000, The X.Org Foundation

Tue Dec 17 11:24:38 2019
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5910
vncext: created VNC server for screen 0

Where and how can I change the colour depth?

Xorg still is not available in the session list.

I’m using Mate desktop. Gnome desktop worked under root account without any issue till yum update.

I just realized I gave you some duff info about the session list — apologies. The session list is stored in /etc/xrdp/xrdp.ini , and not /etc/xrdp/sesman.ini .

If you look in xrdp.ini at around line 181, you should find the following commented-out section:-

Remove the ‘#’ line prefixes and restart the xrdp service. That should give you your Xorg session back.

To run Xorg, you’ll need xorgxrdp installed, but you probably already have that if it was working before.

Colour depth is available (in the Windows client) on the ‘Display’ tab:-

Let us know if that’s useful.

  1. I have edit the /etc/xrdp/xrdp.ini and uncommented this strings
    #[Xorg]
    #name=Xorg
    #lib=libxup.so
    #username=ask
    #password=ask
    #ip=127.0.0.1
    #port=-1
    #code=20

I have restarted the server

When I’m trying connect by rdp — I see an only a black screen. Doesn’t matter which color I use -15 or 32 bits.

  1. I have added the new logs.
    Xorg.0.log
    xrdp.log
    xrdp-sesman.log
    yum.log

I wasn’t familiar with MATE, so I’ve gone away and had a look at it.

Can you try the following:-

  • Make sure the whole MATE desktop is installed with yum groupinstall «MATE Desktop» . It’s possible you’ve only got the mate-desktop RPM installed which isn’t enough.
  • Issue this command as the user you’re trying to log in as to set your default session.

Then have another go.

If you’re still having problems, post the output of the file

/.xsession-errors. This file is (or should be) created when the user logs on and runs the session.

Let us know how it goes.

We have a small progress.

List of installed Groups
Installed Environment Groups:
MATE Desktop
Available Environment Groups:
Minimal Install
Compute Node
Infrastructure Server
File and Print Server
Cinnamon Desktop
Basic Web Server
Virtualization Host
Server with GUI
GNOME Desktop
KDE Plasma Workspaces
Development and Creative Workstation
Installed Groups:
MATE
Available Groups:
Cinnamon
Compatibility Libraries
Console Internet Tools
Development Tools
Educational Software
Electronic Lab
Fedora Packager
General Purpose Desktop
Graphical Administration Tools
Haskell
LXQt Desktop
Legacy UNIX Compatibility
Milkymist
PostgreSQL Database Server 10 PGDG
PostgreSQL Database Server 11 PGDG
PostgreSQL Database Server 12 PGDG
PostgreSQL Database Server 9.4 PGDG
PostgreSQL Database Server 9.5 PGDG
PostgreSQL Database Server 9.6 PGDG
Scientific Support
Security Tools
Smart Card Support
System Administration Tools
System Management
TurboGears application framework
Xfce

Sessions files
-rwxr-xr-x. 1 root root 13 Dec 18 09:42 /root/.Xclients


-rwxr-xr-x. 1 root root 13 Dec 18 09:43 /root/.xsession

After run command bellow I saw the normal RDP screen with Xvnc, Xorg. I tried to login, but the login process stuck. After a few minutes the rdp returned the error

ln -sf /usr/bin/mate-session

  1. Xsession log files
    xsession-errors.txt

The session log shows the desktop is starting. The RDP log shows that XRDP is unable to connect to the X server.

  • Does the same thing happen with both Xvnc and Xorg back ends?
  • For Xorg, have you definitely got the xorgxrdp RPM installed?
  • Xorg generates a log file in

/.xorgxrdp. .log . So for the above example where display 11 is being used, the log file is in

/.xorgxrdp.11.log . If you’re having problems with Xorg, please post the contents of this file.
On CentOS 7, the Xvnc log is stored by journalctl along with stderr from xrdp-sesman (which is not the same as /var/log/xrdp-sesman.log ). If you’re having problems with Xvnc, please post the output of the following command (run as root), which displays the last 3 minutes of this output:-

I have installed xorgxrdp and now everything works properly .
Thank you for your attention and support.

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp . I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1

Ensure the OS is up to date with sudo yum update

Install EPEL repository with sudo yum install epel-release

Install and enable XRDP with:-

If you’re using the firewall, allow external access to TCP port 3389 with:-

If you’re using SELinux, sudo yum install xrdp-selinux

If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

  • sudo yum install xorgxrdp
  • Edit /etc/xrdp/xrdp.ini . If the [Xorg] section is commented out, uncomment it.
  • If you changed xrdp.ini , sudo systemctl restart xrdp to pick up the changes.

Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall «MATE Desktop» .

The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to

/.Xclients . For MATE, this command is adequate:-

As an aside, some websites suggest creating a vanilla file

/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

    Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):-

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

What if you add this instruction into Readme file — at the paragraph troubleshooting?

I see what you mean — there are very brief instructions in the README.md which appears on the front page on Github.

What might make more sense is to link from the README.md to the Wiki, as the Wiki can be updated more easily than README.md. I’ll do some more research (after Xmas probably) and try to get something together which has instructions for all desktops.

Maybe it is interesting, but on Fedora 30/31, I am facing the same issue (exact same displayed message), but only for corporate users.
With local created users, it works.
I am using Xvnc.

Hello,
I had the same situation, Xvnc broken when rendering NVIDIA didn’t work through VNC for old technology.
I installed tigerVnc and running this command:
tigervncserver -localhost no
Viewer Vnc:
vncviewer ip:1
e.g. 192.168.1.1:1

Hello, I am facing a RDP issue from Windows 10 to RHEL8 trying both Xvnc and Xorg. Using either option, after entering credentials and selecting OK, the RDP session immediately closes. For users who were on the system previously and had their sessions time out, they can still RDP into the machine, but all other users can not start a RDP session successfully. Any ideas?

@rja1972 — please start a new thread. I can’t see any similarities between this issue and what you are describing.

Knowing what OS you are on, and what your xrdp version is would be useful.

I’m closing this thread now, as the issue raised by the OP was addressed. Please feel free to raise a new issue if you’ve posted above and you still need help getting something working.

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

  • When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.
  • I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.
  • I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

You are right. I am running CentOS Stream 9 and encounter the same problem. Able to connect after setting the depth to 32 in my RDP client despite the fact that I am connecting as root.

Источник

Цитата
Сообщение от _sg2
Посмотреть сообщение

они ещё и на юх посылают

Никто вас никуда не посылал. Просто вы задаёте странные вопросы со странным упорством, не взирая на мои ответы.

Цитата
Сообщение от _sg2
Посмотреть сообщение

Им помочь пытаешься

Есть пословица мудрая: «Благими намерениями вымощена дорога в ад». Я ценю, что вы ради меня заморочились, поставили и запустили у себя всю эту байду. Но фразой «а вот у меня заработало», ей-Богу, вы мне никак не помогли. Пока что вы только тратите моё время на странные расспросы, что меня и раздражает.

Впрочем, я, безусловно от части не прав, так как не полностью описал проблему. Я написал, что у меня не работает, но не написал, зачем мне это надо. Не думал, что с этим могут возникнуть такие проблемы. Исправляюсь: я не могу настроить удалённый рабочий стол. Когда я подключаюсь к удалённому серверу по RDP, при попытке авторизации я вижу это:

VNC сервер не запускается

. Там написано, что проблема c VNC. Поэтому я и написал, что у меня проблема с VNC.

Но вы тоже хороши:

Цитата
Сообщение от _sg2
Посмотреть сообщение

Из этой ваше фразы и понимаешь, что вы к VNC-серверу зачем-то ломитесь по RDP

Уверен, что никто другой бы эту фразу так не понял. Но даже если допустить такой абсурд, что это меняет в сути проблемы? Проблема в том, что VNC сервер не запускается, о чём я совершенно ясно писал изначально. Не важно, пытаюсь я к нему подключиться по RDP, HTTP, USB, или какими-нибудь ещё более извращёнными методами. Проблема лишь в том, что он изначально не запускается, а не в том, что я с ним потом собираюсь делать. Ну почему такие элементарные вещи надо разжёвывать?

Цитата
Сообщение от _sg2
Посмотреть сообщение

Дык установите его и подключайтесь! Кто ж не даёт.

Ёперный театр, да как бы я мог увидеть то, что представил на скриншоте, если бы у меня не был установлен этот несчастный XRDP?!! Конечно я его установил первым делом! И это именно он на скриншоте ругается на VNC. А логи, что я представил, вы очевидно, не удосужились почитать. Там целый лог от XRDP. Если он его пишет, значит, наверное, он установлен?

Цитата
Сообщение от _sg2
Посмотреть сообщение

Системное администрирование — наука точная…

Честное слово, не хочу вас обижать. Но вот сейчас уже до истерического смеха просто. Надеюсь, связь между моим истерическим смехом и вашей фразой не придётся разжёвывать как все предыдущие.


Description


Dean Hunter



2017-06-26 18:43:07 UTC

Description of problem:
Cannot start an RDP session

Version-Release number of selected component (if applicable):
xrdp.x86_64  1:0.9.2-12.fc26

How reproducible:
Consistent

Steps to Reproduce:
1. Create a new Fedora 26 Beta install using Live USB
2. Apply all pending updates
3. sudo dnf -y install xrdp
4. sudo firewall-cmd --add-port=3389/tcp --permanent 
5. sudo firewall-cmd --reload
6. sudo systemctl enable xrdp
7. sudo systemctl start xrdp
8. sudo dnf -y install freerdp
9. xfreerdp /v:localhost
10. Answer yes to question about certificate names not matching
11. Enter userid/password when prompted

Actual results:
The Connection log window is displayed with the VNC error

Expected results:
Gnome desktop to be displayed

Additional info:


Comment 3


Bojan Smojver



2017-06-26 21:05:05 UTC

Do you have SELinux running on the machine by any chance? If so, did you install xrdp-selinux package?

Also, new TigerVNC packages require some extra options, which are mentioned in README.Fedora file. Did you apply those to your config?


Comment 4


Dean Hunter



2017-06-26 22:12:22 UTC

Thank you for your response.  Yes, I have SELinux running.  No, originally I had not installed xrdp-selinux, but since filing this bug report I found the README.Fedora.  I did:

1. sudo dnf -y install xrdp-selinux
2. sudo reboot
3. logged into Gnome
4. xfreerdp /v:localhost

but the problem persists.  Then I editted the VNC stanza of sesman.ini and restarted xrdp, and again the problem persists.


Comment 5


Dean Hunter



2017-06-26 22:24:24 UTC

By the way, README.Fedora references /etc/X11/Xwrapper.config which dies not exist in my installation.


Comment 6


Bojan Smojver



2017-06-26 22:30:30 UTC

(In reply to Dean Hunter from comment #5)
> By the way, README.Fedora references /etc/X11/Xwrapper.config which dies not
> exist in my installation.

If you're running xorgxrdp, you will need to create that file. Does not apply to VNC.


Comment 7


Bojan Smojver



2017-06-26 22:35:48 UTC

Anything in the audit logs about SELinux denials?

Also, what you you have in /etc/pam.d/xrdp-sesman? Default or Gnome specific stuff (i.e. gdm-password entries)?


Comment 8


Dean Hunter



2017-06-27 21:39:23 UTC

Thank you for the note about Xwrapper.config.  I have had not notices about SELinux denials.  Please remind me how to search the audit log for denials.

>cat /etc/pam.d/xrdp-sesman
#%PAM-1.0
# Generic Fedora config
auth       include      password-auth
account    include      password-auth
password   include      password-auth
session    include      password-auth

# Gnome specific Fedora config
#auth       include      gdm-password
#account    include      gdm-password
#password   include      gdm-password
#session    include      gdm-password


Comment 9


Bojan Smojver



2017-06-27 21:42:37 UTC

To search for denials, try:

grep denied /var/log/audit/audit.log

You may also want to convert that into a more readable SELinux format:

grep denied /var/log/audit/audit.log | audit2allow -m denials

Try using Gnome specific stuff in xrdp-sesman PAM configuration. That is what I have on my VM that runs xrdp and Gnome.


Comment 10


Dean Hunter



2017-06-28 22:22:47 UTC

$ sudo grep denied /var/log/audit/audit.log | audit2allow -m denials

module denials 1.0;

require {
	type unconfined_service_t;
	type geoclue_t;
	type lib_t;
	type init_t;
	type useradd_t;
	type xdm_t;
	class dir { search setattr };
	class dbus send_msg;
}

#============= geoclue_t ==============
allow geoclue_t unconfined_service_t:dir search;

#============= useradd_t ==============
allow useradd_t init_t:dbus send_msg;

#============= xdm_t ==============
allow xdm_t lib_t:dir setattr;

$


Comment 11


Dean Hunter



2017-06-28 22:30:35 UTC

Modified /etc/pam.d/xrdp-sesman to be:

#%PAM-1.0
# Generic Fedora config
#auth       include      password-auth
#account    include      password-auth
#password   include      password-auth
#session    include      password-auth

# Gnome specific Fedora config
auth       include      gdm-password
account    include      gdm-password
password   include      gdm-password
session    include      gdm-password

then restarted xrdp but the problem persists.


Comment 12


Bojan Smojver



2017-06-28 23:23:42 UTC

I'm out of ideas, so try to strace the xrdp processes when you login to see what's happening. There were problems with IPv6 at one point as well, so you may want to try disabling that.


Comment 13


Dean Hunter



2017-06-29 00:42:17 UTC

I am not familiar with strace.  Can you give me the command lines for which you would like to see the output?


Comment 14


Bojan Smojver



2017-06-29 00:45:46 UTC

Posting all of strace output will probably not be practical - the program prints out system calls. So, you would need to be able to determine which system call is resulting in the problem that may be related.

Normally, you want to see which xrdp processes are running when the service is started and then run:

strace -f -p <pid> -p <pid>...

This will then follow the forks of these processes as well.


Comment 15


Dean Hunter



2017-06-30 13:40:59 UTC

[admin@developer ~]$ sudo systemctl restart xrdp
[admin@developer ~]$ sudo systemctl status xrdp
● xrdp.service - xrdp daemon
   Loaded: loaded (/usr/lib/systemd/system/xrdp.service; enabled; vendor preset:
   Active: active (running) since Fri 2017-06-30 08:37:56 CDT; 7s ago
     Docs: man:xrdp(8)
           man:xrdp.ini(5)
 Main PID: 6216 (xrdp)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/xrdp.service
           └─6216 /usr/sbin/xrdp --nodaemon

Jun 30 08:37:56 developer.hunter.org systemd[1]: Started xrdp daemon.
Jun 30 08:37:56 developer.hunter.org xrdp[6216]: (6216)(140429996107904)[INFO ] 
Jun 30 08:37:56 developer.hunter.org xrdp[6216]: (6216)(140429996107904)[INFO ] 
[admin@developer ~]$ sudo strace -f -p 6216 -o strace.log
strace: Process 6216 attached
strace: Process 6250 attached
^Cstrace: Process 6216 detached
[admin@developer ~]$ zip strace.zip strace.log
updating: strace.log (deflated 96%)
[admin@developer ~]$ 

strace.zip is attached


Comment 17


Dean Hunter



2017-07-10 17:33:27 UTC

Was the strace useful?  Do you need anything else?


Comment 18


Bojan Smojver



2017-07-20 00:31:37 UTC

(In reply to Dean Hunter from comment #17)
> Was the strace useful?  Do you need anything else?

Looked at the strace output and I can only see what appear to be timeouts to be back end (i.e. the VNC process), if I'm reading that correctly. I'm not any smarter after it, I'm afraid. :-(


Comment 19


Bojan Smojver



2017-07-20 00:35:23 UTC

Do you have this set in /etc/xrdp/sesman.ini when you're running the VNC session:

param=-AcceptCutText=0
param=-SendCutText=0
param=-SendPrimary=0
param=-SetPrimary=0


Comment 20


Dean Hunter



2017-07-24 17:13:06 UTC

So xrdp is timing out while trying to connect to VNC?  I have only the default configuration of VNC provided by a new install of Fedora 26.

Installed Packages
tigervnc-license.noarch                     1.8.0-1.fc26               @anaconda
tigervnc-server-minimal.x86_64              1.8.0-1.fc26               @anaconda

None of the parameters you listed are set in the sesman.ini built by a new install of Fedora 26 and I have not changed the file.  In which stanza do they belong?


Comment 21


Dean Hunter



2017-07-24 17:40:09 UTC

I found that I had tried this test before with a ticket opened with Neutrino Labs: https://github.com/neutrinolabs/xrdp/issues/765  So I added the params to the [Xvnc] stanza, restarted xrdp, and tried again with the same erroneous results.

I see some new information in the ticket from grishin-a that says there is a problem with xrdp-selinux.  Can you review it and advise whether it really applies to this problem?


Comment 22


Dean Hunter



2017-07-24 18:14:02 UTC

grishin-a is using the MATE desktop where I am using the standard Gnome desktop.  grishin-a is installing oddjob-mkhomedir which is not installed with Fedora 26 Workstation.  His changes to xrdp-selinux seem to be limited to to including oddjob-mkhomedir.


Comment 23


Bojan Smojver



2017-07-24 20:56:50 UTC

(In reply to Dean Hunter from comment #20)

> None of the parameters you listed are set in the sesman.ini built by a new
> install of Fedora 26 and I have not changed the file.  In which stanza do
> they belong?

Per README.Fedora:
---------------
TigerVNC 1.8.0 enables clipboard support by default (i.e. no need to run
vncconfig), which may cause disconnections in xrdp. To avoid the issue, these
can be added to [Xvnc] stanza in /etc/xrdp/sesman.ini:

param=-AcceptCutText=0
param=-SendCutText=0
param=-SendPrimary=0
param=-SetPrimary=0

Of course, cut and paste support will not work with these set.
---------------

This was sprung upon us in xrdp world without any notice and there must be some kind of bug in xrdp that is causing disconnections. Given that recent Fedoras can have both version 1.7.x and 1.8.x of TigerVNC installed, I didn't want to set this as default.

Also, without patched xrdp, passing that =0 would not work anyway.

I know, less than ideal...


Comment 24


Bojan Smojver



2017-07-24 20:57:42 UTC

The SELinux theories are always easy to prove/disprove - just turn it off or put it in permissive mode. If it starts working, it was SELinux.


Comment 26


Dean Hunter



2017-07-26 17:36:41 UTC

I created a new VM with gnome-boxes and Fedora-Workstation-Live-86_64-26-1.5.iso.  I applied all updates then installed, configured using all of your advice, and tested.  Xrdp still does not work.  I have attached the log of my work, see Comment 25.

I know you said Xrdp works in your VM, what am I doing that is different?


Comment 27


Bojan Smojver



2017-07-27 03:00:45 UTC

I am thinking that maybe some component is missing to run gnome properly. Can you run gnome all by itself on that VM?


Comment 28


Dean Hunter



2017-07-27 23:09:00 UTC

Yes, Gnome seems to work.  I have used Activities to run Terminal to install and test Xrdp, Files to find the configuration and log files, Text Editor to edit the configuration files, and Software to update the installation of Fedora 26.

Did you use Fedora 26 Workstation for your VM?


Comment 29


Bojan Smojver



2017-07-27 23:16:12 UTC

(In reply to Dean Hunter from comment #28)

> Did you use Fedora 26 Workstation for your VM?

My VM is an upgrade from (I think) F25. I think I may have used the workstation product to install it.


Comment 30


Dean Hunter



2017-08-02 16:51:47 UTC

I created a new VM using Fedora-Workstation-Live-x86_64-25-1.3.iso, then followed the same procedure as in Comment 25 to install, configure, and test Xrdp.  This installs the same version of Xrdp as with Fedora 26, and, without surprise, produces the exact same erroneous results.

I was trying to reproduce your VM where you say Xrdp works.  So I will not be able to compare a working installation with the installation created from Fedora 26 Workstation Live.  Please, can you tell me what is missing?


Comment 31


Bojan Smojver



2017-08-02 23:19:53 UTC

(In reply to Dean Hunter from comment #30)

> Please, can you tell me what is missing?

I honestly wish I could. There is bound to be something that I must have done by hand to get mine working (although I don't remember it), but I cannot remember what any more, if anything.

I do have root logins turned off in my sesman.ini. That surely cannot be it.


Comment 32


Dean Hunter



2017-08-03 00:01:16 UTC

I REALLY do not understand.  Could you not create a Fedora 26 Workstation VM, as I have done, and compare it to the VM where you say Xrdp is working?


Comment 33


Bojan Smojver



2017-08-03 00:35:52 UTC

(In reply to Dean Hunter from comment #32)
> I REALLY do not understand.  Could you not create a Fedora 26 Workstation
> VM, as I have done, and compare it to the VM where you say Xrdp is working?

I will do that when I get an opportunity.


Comment 34


Dean Hunter



2017-08-03 01:12:02 UTC

Here is another data point: I built another VM using CentOS 7.0, updated, installed, and tested Xrdp.  It works with the default configuration.  The first difference I see is that CentOS 7 is using a different version of TigerVNC:

[admin@centos70 ~]$ yum list installed tigervnc*
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.ancl.hawaii.edu
 * epel: fedora-epel.mirror.lstn.net
 * extras: mirror.cs.vt.edu
 * updates: repos-tx.psychz.net
Installed Packages
tigervnc-license.noarch                      1.3.1-9.el7               @anaconda
tigervnc-server-minimal.x86_64               1.3.1-9.el7               @anaconda
[admin@centos70 ~]$ 

[admin@xrdptest ~]$ dnf list installed tigervnc*
Installed Packages
tigervnc-license.noarch                     1.8.0-1.fc26               @anaconda
tigervnc-server-minimal.x86_64              1.8.0-1.fc26               @anaconda
[admin@xrdptest ~]$


Comment 35


Bojan Smojver



2017-08-03 05:30:10 UTC

Try:

systemctl set-default multi-user.target

Then reboot. Then try an RDP connection. See if that works.


Comment 36


Dean Hunter



2017-08-04 19:44:11 UTC

[admin@xrdptest ~]$ sudo systemctl get-default 
graphical.target
[admin@xrdptest ~]$ sudo systemctl set-default multi-user.target
Removed /etc/systemd/system/default.target.
Created symlink /etc/systemd/system/default.target → /usr/lib/systemd/system/multi-user.target.
[admin@xrdptest ~]$ sudo systemctl get-default 
multi-user.target
[admin@xrdptest ~]$ sudo reboot

And I get no Gnome shell!!!


Comment 37


Dean Hunter



2017-08-04 19:50:39 UTC

[admin@xrdptest ~]$ systemctl list-units --type target
UNIT                   LOAD   ACTIVE SUB    DESCRIPTION                  
basic.target           loaded active active Basic System                 
cryptsetup.target      loaded active active Encrypted Volumes            
getty.target           loaded active active Login Prompts                
graphical.target       loaded active active Graphical Interface          
local-fs-pre.target    loaded active active Local File Systems (Pre)     
local-fs.target        loaded active active Local File Systems           
multi-user.target      loaded active active Multi-User System            
network-online.target  loaded active active Network is Online            
network-pre.target     loaded active active Network (Pre)                
network.target         loaded active active Network                      
nfs-client.target      loaded active active NFS client services          
nss-lookup.target      loaded active active Host and Network Name Lookups
nss-user-lookup.target loaded active active User and Group Name Lookups  
paths.target           loaded active active Paths                        
remote-fs-pre.target   loaded active active Remote File Systems (Pre)    
remote-fs.target       loaded active active Remote File Systems          
rpc_pipefs.target      loaded active active rpc_pipefs.target            
slices.target          loaded active active Slices                       
sockets.target         loaded active active Sockets                      
sound.target           loaded active active Sound Card                   
spice-vdagentd.target  loaded active active Agent daemon for Spice guests
swap.target            loaded active active Swap                         
sysinit.target         loaded active active System Initialization        
timers.target          loaded active active Timers                       

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

24 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
[admin@xrdptest ~]$


Comment 38


Bojan Smojver



2017-08-05 03:19:06 UTC

(In reply to Dean Hunter from comment #36)
> [admin@xrdptest ~]$ sudo systemctl get-default 
> graphical.target
> [admin@xrdptest ~]$ sudo systemctl set-default multi-user.target
> Removed /etc/systemd/system/default.target.
> Created symlink /etc/systemd/system/default.target →
> /usr/lib/systemd/system/multi-user.target.
> [admin@xrdptest ~]$ sudo systemctl get-default 
> multi-user.target
> [admin@xrdptest ~]$ sudo reboot
> 
> And I get no Gnome shell!!!

Hmm, interesting. I set up an F26 VM and installed xrdp on it. Originally it was set to boot in graphical.traget and the logs were showing Gnome Shell errors when I tried to connect to it (probably some kind of clash with gdm's shell). Once I switched to multi-user.target (i.e. non-graphical), I could connect to it using remote desktop client in Windows over RDP.


Comment 39


Bojan Smojver



2017-08-05 05:40:25 UTC

Just to avoid confusion, I blew away the F26 VM I created earlier and set it up again. I did that on Windows 10 with VMware Player 12 something (the free download from their site). I use x86_64 live image of F26 workstation to set up the VM, all defaults. I added user test (with password).

Once I booted into the installed VM, I switched to VT2 and did the following (paraphrasing here):

- systemctl set-default multi-user.target
- dnf install xrdp-selinux (this installs xrdp as well)
- dnf -y update
- cut/pasted TigerVNC stuff from README.Fedora into Xvnc stanza of sesman.ini
- edited /etc/pam.d/xrdp-sesman and enabled gdm stuff instead of standard
- firewall-cmd --add-service=ms-wbt --permanent (or something to that effect)

Then I rebooted and used remote desktop client from Windows 10 to connect to the address of the VM. You will see the result in the image I'll attach. Basically, Gnome ran just fine.


Comment 41


Dean Hunter



2017-08-14 17:49:48 UTC

Thank you for your patience.  I have verified that it is necessary to shut down the graphical interface for the console on the machine running Xrdp.  This is something new to me on Fedora, although it has been a few years since I have tried this.  And it is not necessary on CentOS 7 running the same version of Xrdp.  Can you spare a few more minutes to explain why it is necessary?


Comment 42


Dean Hunter



2017-08-14 18:37:26 UTC

I feel I must apologize for being an idiot.  Shutting off the graphical interface to the console worked because it forced me to use another VM workstation to test the connection instead of trying to connect to localhost, as I have been able to do with CentOS.


Comment 43


Sampson Fung



2018-03-19 13:47:46 UTC

I followed instruction on comment #39, so that the Vnc username and password can pass.

But then the RDP session will got cut immediately afterwards.  

I can see the Gnome desktop wallpaper show up for a while before connect is cut.

login successful for display 10. VNC error — problem connecting some problem #1459

Comments

YuriyTigiev commented Dec 13, 2019

I have installed and used xrdp on a centos 7.0 + gnome. I used this resource https://draculaservers.com/tutorials/install-xrdp-centos/ for install xrdp.
I always used session Xorg for login because of xrdp never worked with Xvnc session

A few days ago I have updated a linux with command sudo yum update
After the update, the menu Xorg disappeared from Session list and when I used Xvnc session I get an error — Login successful for display 10. VNC error — problem connecting some problem

I googled a lot and read and tried a lot of solutions for the fix issue but without success.

The text was updated successfully, but these errors were encountered:

matt335672 commented Dec 16, 2019

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.

I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.

I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

YuriyTigiev commented Dec 17, 2019

The issue was not solved.

]# rpm -q centos-release
centos-release-7-7.1908.0.el7.centos.x86_64

]# getenforce
Enforcing
[root@localhost

]# sestatus
SELinux status: enabled
SELinuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: targeted
Current mode: enforcing
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Max kernel policy version: 31
[root@localhost

I have installed:
xrdp-selinux.x86_64 1:0.9.11-5.el7

I have added the sesman.ini file to this post.
sesman.txt

Output for Xvnc :10
[root@localhost

Xvnc TigerVNC 1.8.0 — built Aug 9 2019 03:04:19
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12001000, The X.Org Foundation

Tue Dec 17 11:24:38 2019
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5910
vncext: created VNC server for screen 0

Where and how can I change the colour depth?

Xorg still is not available in the session list.

I’m using Mate desktop. Gnome desktop worked under root account without any issue till yum update.

matt335672 commented Dec 17, 2019

I just realized I gave you some duff info about the session list — apologies. The session list is stored in /etc/xrdp/xrdp.ini , and not /etc/xrdp/sesman.ini .

If you look in xrdp.ini at around line 181, you should find the following commented-out section:-

Remove the ‘#’ line prefixes and restart the xrdp service. That should give you your Xorg session back.

To run Xorg, you’ll need xorgxrdp installed, but you probably already have that if it was working before.

Colour depth is available (in the Windows client) on the ‘Display’ tab:-

Let us know if that’s useful.

YuriyTigiev commented Dec 17, 2019

  1. I have edit the /etc/xrdp/xrdp.ini and uncommented this strings
    #[Xorg]
    #name=Xorg
    #lib=libxup.so
    #username=ask
    #password=ask
    #ip=127.0.0.1
    #port=-1
    #code=20

I have restarted the server

When I’m trying connect by rdp — I see an only a black screen. Doesn’t matter which color I use -15 or 32 bits.

  1. I have added the new logs.
    Xorg.0.log
    xrdp.log
    xrdp-sesman.log
    yum.log

matt335672 commented Dec 17, 2019

I wasn’t familiar with MATE, so I’ve gone away and had a look at it.

Can you try the following:-

  • Make sure the whole MATE desktop is installed with yum groupinstall «MATE Desktop» . It’s possible you’ve only got the mate-desktop RPM installed which isn’t enough.
  • Issue this command as the user you’re trying to log in as to set your default session.

Then have another go.

If you’re still having problems, post the output of the file

/.xsession-errors. This file is (or should be) created when the user logs on and runs the session.

Let us know how it goes.

YuriyTigiev commented Dec 18, 2019

We have a small progress.

List of installed Groups
Installed Environment Groups:
MATE Desktop
Available Environment Groups:
Minimal Install
Compute Node
Infrastructure Server
File and Print Server
Cinnamon Desktop
Basic Web Server
Virtualization Host
Server with GUI
GNOME Desktop
KDE Plasma Workspaces
Development and Creative Workstation
Installed Groups:
MATE
Available Groups:
Cinnamon
Compatibility Libraries
Console Internet Tools
Development Tools
Educational Software
Electronic Lab
Fedora Packager
General Purpose Desktop
Graphical Administration Tools
Haskell
LXQt Desktop
Legacy UNIX Compatibility
Milkymist
PostgreSQL Database Server 10 PGDG
PostgreSQL Database Server 11 PGDG
PostgreSQL Database Server 12 PGDG
PostgreSQL Database Server 9.4 PGDG
PostgreSQL Database Server 9.5 PGDG
PostgreSQL Database Server 9.6 PGDG
Scientific Support
Security Tools
Smart Card Support
System Administration Tools
System Management
TurboGears application framework
Xfce

Sessions files
-rwxr-xr-x. 1 root root 13 Dec 18 09:42 /root/.Xclients


-rwxr-xr-x. 1 root root 13 Dec 18 09:43 /root/.xsession

After run command bellow I saw the normal RDP screen with Xvnc, Xorg. I tried to login, but the login process stuck. After a few minutes the rdp returned the error

ln -sf /usr/bin/mate-session

  1. Xsession log files
    xsession-errors.txt

matt335672 commented Dec 18, 2019

The session log shows the desktop is starting. The RDP log shows that XRDP is unable to connect to the X server.

  • Does the same thing happen with both Xvnc and Xorg back ends?
  • For Xorg, have you definitely got the xorgxrdp RPM installed?
  • Xorg generates a log file in

/.xorgxrdp. .log . So for the above example where display 11 is being used, the log file is in

/.xorgxrdp.11.log . If you’re having problems with Xorg, please post the contents of this file.
On CentOS 7, the Xvnc log is stored by journalctl along with stderr from xrdp-sesman (which is not the same as /var/log/xrdp-sesman.log ). If you’re having problems with Xvnc, please post the output of the following command (run as root), which displays the last 3 minutes of this output:-

YuriyTigiev commented Dec 18, 2019

I have installed xorgxrdp and now everything works properly .
Thank you for your attention and support.

matt335672 commented Dec 18, 2019

Thanks for letting us know — I’m glad we got there between us.

I’ll just summarize and expand on this thread for anyone else reading this, who is trying to get an alternative desktop working on a fresh install of the latest CentOS 7. The webpage you linked to is pretty good, but it’s missing some small details like SELinux support and the need for xorgxrdp . I’ve also added some of my own sysadmin experiences.

At the time of writing, the following versions apply:-

Software Version
CentOS 7.7
xrdp RPM 0.9.11-5
xorgxrdp RPM 0.2.11-1

Ensure the OS is up to date with sudo yum update

Install EPEL repository with sudo yum install epel-release

Install and enable XRDP with:-

If you’re using the firewall, allow external access to TCP port 3389 with:-

If you’re using SELinux, sudo yum install xrdp-selinux

If you want to use the Xorg backend in addition to (or instead of) the Xvnc backend, do the following. The differences between the two backends are covered elsewhere.

  • sudo yum install xorgxrdp
  • Edit /etc/xrdp/xrdp.ini . If the [Xorg] section is commented out, uncomment it.
  • If you changed xrdp.ini , sudo systemctl restart xrdp to pick up the changes.

Install your desktop(s), making sure that you use a command to install the whole desktop rather than a subset of it. This will probably be a yum groupinstall command. For example, for MATE, use sudo yum groupinstall «MATE Desktop» .

The default desktop for XRDP on CentOS 7 is GNOME. If you want the default desktop for all XRDP users to be something else, create the file /etc/sysconfig/desktop and set the PREFERRED variable to the command to start the desktop. For example, this /etc/sysconfig/desktop sets the default desktop to MATE for all XRDP users:-

XRDP users who want to use a desktop other than the default will need to soft-link the command to start the correct session in to

/.Xclients . For MATE, this command is adequate:-

As an aside, some websites suggest creating a vanilla file

/.xsession containing the command to start the desktop. That’s OK too, but you have to remember to make the file executable. The soft-link method avoids this pitfall.

That should get the desktop running. Here are a couple of gotchas:-

    Some desktops expect GDM to be running to provide some of their functionality over DBUS. For example, the GNOME lock screen is implemented in GDM. If you’re using one of these desktops you may need to enable GDM on the machine console (if it isn’t enabled already):-

I think that’s it, but please let me know if I’ve left anything out.

Does anyone think this would be useful as a Wiki page by the way?

YuriyTigiev commented Dec 18, 2019

What if you add this instruction into Readme file — at the paragraph troubleshooting?

matt335672 commented Dec 19, 2019

I see what you mean — there are very brief instructions in the README.md which appears on the front page on Github.

What might make more sense is to link from the README.md to the Wiki, as the Wiki can be updated more easily than README.md. I’ll do some more research (after Xmas probably) and try to get something together which has instructions for all desktops.

peddanet commented Jan 10, 2020 •

Maybe it is interesting, but on Fedora 30/31, I am facing the same issue (exact same displayed message), but only for corporate users.
With local created users, it works.
I am using Xvnc.

herreradimas commented Jan 29, 2021

Hello,
I had the same situation, Xvnc broken when rendering NVIDIA didn’t work through VNC for old technology.
I installed tigerVnc and running this command:
tigervncserver -localhost no
Viewer Vnc:
vncviewer ip:1
e.g. 192.168.1.1:1

rja1972 commented Oct 26, 2021

Hello, I am facing a RDP issue from Windows 10 to RHEL8 trying both Xvnc and Xorg. Using either option, after entering credentials and selecting OK, the RDP session immediately closes. For users who were on the system previously and had their sessions time out, they can still RDP into the machine, but all other users can not start a RDP session successfully. Any ideas?

matt335672 commented Oct 29, 2021

@rja1972 — please start a new thread. I can’t see any similarities between this issue and what you are describing.

Knowing what OS you are on, and what your xrdp version is would be useful.

I’m closing this thread now, as the issue raised by the OP was addressed. Please feel free to raise a new issue if you’ve posted above and you still need help getting something working.

yudonglin commented Sep 23, 2022

A couple of questions for you:-

  • Looking at your yum logs, you appear to be running CentOS 7.7 rather than 7.0. Can you confirm this? You can find out your minor release version with the command cat /etc/redhat-release ?
  • Is SELinux enabled on this system? If so, you will need to install the xrdp-selinux package in addition to the xrdp package.

And a few other things:-

  • The sessions which are presented to the user on the login screen are stored in the file /etc/xrdp/sesman.ini . On a fresh install, this file should contain the following sections (amongst other things):-

These sections should add Xorg and Xvnc as the options on your session list.

  • When using Xvnc, the sesman log indicates that the VNC server is having trouble running the Xvnc command. You could try running Xvnc :10 on the command line to see if we get any more information.
  • I see from the sesman log you’re trying to run with a colour depth of 15. This confuses some software as the MESA-based 3d acceleration won’t work. Try setting a depth of 32 in your RDP client.
  • I see from the log you’re trying to log in as root. GNOME in particular doesn’t like this. I don’t think this is the source of the problem you’re describing here, but in general things will work a bit better if you log in as a non-privileged user.

I hope that’s useful. Let us know how you get on.

You are right. I am running CentOS Stream 9 and encounter the same problem. Able to connect after setting the depth to 32 in my RDP client despite the fact that I am connecting as root.

Источник

Hi,

Im trying to connect to my Debian machine from my Windows host but I cant get it to work, I have installed both xrdp and x11vnc. I don’t know the reason as to why I can’t connect. The machine is listening on the TCP ports.

xrdp.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp.log
[20180219-19:34:37] [INFO ] starting xrdp with pid 2189
[20180219-19:34:37] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:34:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55533
[20180219-19:34:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:53] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:34:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:53] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:34:54] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55534
[20180219-19:34:54] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:34:54] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:34:54] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:34:54] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:34:54] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:34:54] [DEBUG] xrdp_000009d7_wm_login_mode_event_00000001
[20180219-19:34:54] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:34:54] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:35:08] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:35:08] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:35:08] [DEBUG] xrdp_wm_log_msg: started connecting
[20180219-19:35:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:44] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:51] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:35:58] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:05] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:12] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:19] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:26] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:33] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:40] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:47] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:54] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:36:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:01] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:08] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:39] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55550
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:39] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:39] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:39] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:37:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:37:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:41] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55551
[20180219-19:37:41] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:37:41] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:37:41] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:37:41] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:37:41] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:37:41] [DEBUG] xrdp_00000a3a_wm_login_mode_event_00000001
[20180219-19:37:41] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:37:41] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:37:43] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:46] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:50] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:53] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:37:57] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:00] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:04] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:07] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:11] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:15] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:18] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:22] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:25] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:29] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:32] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:35] [INFO ] A connection received from: ::ffff:172.10.88.6 port 57082
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:35] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:35] [DEBUG] Closed socket 16 (AF_INET6 ::ffff:172.10.88.6 port 57082)
[20180219-19:38:35] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:35] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:36] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: connection problem, giving up
[20180219-19:38:39] [DEBUG] Closed socket 17 (AF_UNIX)
[20180219-19:38:39] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51520)
[20180219-19:38:39] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:39] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:38:39] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:52] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55557
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:52] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:52] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:38:52] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:52] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:38:53] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55558
[20180219-19:38:53] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:38:53] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:38:53] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:38:53] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:38:53] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:38:53] [DEBUG] xrdp_00000a62_wm_login_mode_event_00000001
[20180219-19:38:53] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:38:53] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:43:56] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:43:57] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:43:57] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:43:57] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:44:00] [DEBUG] VNC error 1 after security negotiation
[20180219-19:44:00] [DEBUG] VNC error before sending share flag
[20180219-19:44:00] [DEBUG] VNC error before receiving server init
[20180219-19:44:00] [DEBUG] VNC error before receiving pixel format
[20180219-19:44:00] [DEBUG] VNC error before receiving name length
[20180219-19:44:00] [DEBUG] VNC error before receiving name
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:44:00] [DEBUG] Closed socket 17 (AF_INET6 :: port 40824)
[20180219-19:44:00] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:44:00] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:44:00] [DEBUG] VNC mod_exit
[20180219-19:44:00] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51526)
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:47:42] [DEBUG] xrdp_wm_log_msg: VNC connecting to 172.10.88.6 3350
[20180219-19:47:45] [DEBUG] VNC error 1 after security negotiation
[20180219-19:47:45] [DEBUG] VNC error before sending share flag
[20180219-19:47:45] [DEBUG] VNC error before receiving server init
[20180219-19:47:45] [DEBUG] VNC error before receiving pixel format
[20180219-19:47:45] [DEBUG] VNC error before receiving name length
[20180219-19:47:45] [DEBUG] VNC error before receiving name
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:47:45] [DEBUG] Closed socket 16 (AF_INET6 :: port 57536)
[20180219-19:47:45] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:47:45] [ERROR] xrdp_wm_log_msg: Error connecting to: 172.10.88.6
[20180219-19:47:45] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:45] [DEBUG] VNC mod_exit
[20180219-19:47:45] [DEBUG] return value from xrdp_mm_connect 1
[20180219-19:47:51] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:47:51] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:47:51] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:07] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55674
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:07] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:07] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:07] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:48:07] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:07] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:48:08] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55675
[20180219-19:48:08] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:08] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:48:08] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:48:08] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:48:08] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:48:08] [DEBUG] xrdp_00000cbd_wm_login_mode_event_00000001
[20180219-19:48:08] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:48:08] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:48:30] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:48:31] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:48:31] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:48:31] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:48:32] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:48:32] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:32] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 51540)
[20180219-19:48:56] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:48:56] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:48:56] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:49:01] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:24] [INFO ] starting xrdp with pid 654
[20180219-19:50:24] [INFO ] listening to port 3389 on 0.0.0.0
[20180219-19:50:34] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55696
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:34] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:34] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:34] [DEBUG] Security layer: requested 11, selected 0
[20180219-19:50:34] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:34] [ERROR] Listening socket is in wrong state, terminating listener
[20180219-19:50:35] [INFO ] A connection received from: ::ffff:172.10.88.2 port 55697
[20180219-19:50:35] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.10.88.6 port 3389)
[20180219-19:50:35] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389)
[20180219-19:50:35] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20180219-19:50:35] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20180219-19:50:35] [DEBUG] Security layer: requested 0, selected 0
[20180219-19:50:35] [DEBUG] xrdp_000004aa_wm_login_mode_event_00000001
[20180219-19:50:35] [INFO ] Loading keymap file /etc/xrdp/km-0000041d.ini
[20180219-19:50:35] [WARN ] local keymap file for 0x0000041d found and doesn't match built in keymap, using local keymap file
[20180219-19:50:51] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:50:52] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:50:52] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:50:52] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:50:54] [INFO ] xrdp_wm_log_msg: login failed for display 0
[20180219-19:50:54] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:50:54] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34254)
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: sesman connect ok
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...
[20180219-19:51:32] [DEBUG] return value from xrdp_mm_connect 0
[20180219-19:51:32] [INFO ] xrdp_wm_log_msg: login successful for display 10
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC started connecting
[20180219-19:51:32] [DEBUG] xrdp_wm_log_msg: VNC connecting to 127.0.0.1 5910
[20180219-19:51:35] [DEBUG] VNC error 1 after security negotiation
[20180219-19:51:35] [DEBUG] VNC error before sending share flag
[20180219-19:51:36] [DEBUG] VNC error before receiving server init
[20180219-19:51:36] [DEBUG] VNC error before receiving pixel format
[20180219-19:51:36] [DEBUG] VNC error before receiving name length
[20180219-19:51:36] [DEBUG] VNC error before receiving name
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: VNC error - problem connecting
[20180219-19:51:36] [DEBUG] Closed socket 17 (AF_INET6 :: port 43916)
[20180219-19:51:36] [DEBUG] xrdp_wm_log_msg: some problem
[20180219-19:51:36] [DEBUG] xrdp_mm_module_cleanup
[20180219-19:51:36] [DEBUG] VNC mod_exit
[20180219-19:51:36] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 34268)

xrdp-sesman.log:

Code: Select all

dave@hal9000:/var/log$ sudo cat xrdp-sesman.log
[20180219-19:34:35] [DEBUG] libscp initialized
[20180219-19:34:35] [INFO ] starting xrdp-sesman with pid 2177
[20180219-19:34:35] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:35:08] [INFO ] A connection received from ::1 port 51520
[20180219-19:35:08] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55534 - socket: 12
[20180219-19:35:08] [INFO ] starting Xorg session...
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:35:08] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:35:08] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:35:08] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [INFO ] starting xrdp-sessvc - xpid=2534 - wmpid=2533
[20180219-19:35:18] [ERROR] X server for display 10 startup timeout
[20180219-19:35:18] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:35:18] [DEBUG] aborting connection...
[20180219-19:35:18] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 2532, ip 0.0.0.0:55534 - socket: 12
[20180219-19:43:56] [INFO ] A connection received from ::1 port 51526
[20180219-19:43:57] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55558 - socket: 12
[20180219-19:43:57] [INFO ] starting Xvnc session...
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:43:57] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:43:57] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:43:57] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:43:57] [CORE ] error starting X server - user dave - pid 3131
[20180219-19:43:57] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:43:57] [DEBUG] execve parameter list size: 17
[20180219-19:43:57] [DEBUG]         argv[0] = Xvnc
[20180219-19:43:57] [DEBUG]         argv[1] = :10
[20180219-19:43:57] [DEBUG]         argv[2] = -auth
[20180219-19:43:57] [DEBUG]         argv[3] = .Xauthority
[20180219-19:43:57] [DEBUG]         argv[4] = -geometry
[20180219-19:43:57] [DEBUG]         argv[5] = 3440x1440
[20180219-19:43:57] [DEBUG]         argv[6] = -depth
[20180219-19:43:57] [DEBUG]         argv[7] = 32
[20180219-19:43:57] [DEBUG]         argv[8] = -rfbauth
[20180219-19:43:57] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:43:57] [DEBUG]         argv[10] = -bs
[20180219-19:43:57] [DEBUG]         argv[11] = -nolisten
[20180219-19:43:57] [DEBUG]         argv[12] = tcp
[20180219-19:43:57] [DEBUG]         argv[13] = -localhost
[20180219-19:43:57] [DEBUG]         argv[14] = -dpi
[20180219-19:43:57] [DEBUG]         argv[15] = 96
[20180219-19:43:57] [DEBUG]         argv[16] = (null)
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [INFO ] starting xrdp-sessvc - xpid=3131 - wmpid=3130
[20180219-19:44:07] [ERROR] X server for display 10 startup timeout
[20180219-19:44:07] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:44:07] [DEBUG] aborting connection...
[20180219-19:44:07] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 3129, ip 0.0.0.0:55558 - socket: 12
[20180219-19:48:30] [INFO ] A connection received from ::1 port 51540
[20180219-19:48:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:49:01] [INFO ] shutting down sesman 1
[20180219-19:49:01] [WARN ] receiving SIGHUP 1
[20180219-19:49:01] [CORE ] shutting down log subsystem...
[20180219-19:49:01] [INFO ] configuration reloaded, log subsystem restarted
[20180219-19:49:01] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:50:22] [DEBUG] libscp initialized
[20180219-19:50:22] [INFO ] starting xrdp-sesman with pid 627
[20180219-19:50:22] [INFO ] listening to port 3350 on 127.0.0.1
[20180219-19:50:51] [INFO ] A connection received from ::1 port 34254
[20180219-19:50:54] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] A connection received from ::1 port 34268
[20180219-19:51:32] [INFO ] ++ created session (access granted): username dave, ip 0.0.0.0:55697 - socket: 12
[20180219-19:51:32] [INFO ] starting Xvnc session...
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 5910)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6010)
[20180219-19:51:32] [DEBUG] Closed socket 9 (AF_INET6 :: port 6210)
[20180219-19:51:32] [DEBUG] Closed socket 8 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [DEBUG] Closed socket 7 (AF_INET6 ::1 port 3350)
[20180219-19:51:32] [INFO ] Xvnc :10 -auth .Xauthority -geometry 3440x1440 -depth 32 -rfbauth /home/dave/.vnc/sesman_dave_passwd:10 -bs -nolisten tcp -localhost -dpi 96
[20180219-19:51:32] [CORE ] error starting X server - user dave - pid 1600
[20180219-19:51:33] [DEBUG] errno: 2, description: No such file or directory
[20180219-19:51:33] [DEBUG] execve parameter list size: 17
[20180219-19:51:33] [DEBUG]         argv[0] = Xvnc
[20180219-19:51:33] [DEBUG]         argv[1] = :10
[20180219-19:51:33] [DEBUG]         argv[2] = -auth
[20180219-19:51:33] [DEBUG]         argv[3] = .Xauthority
[20180219-19:51:33] [DEBUG]         argv[4] = -geometry
[20180219-19:51:33] [DEBUG]         argv[5] = 3440x1440
[20180219-19:51:33] [DEBUG]         argv[6] = -depth
[20180219-19:51:33] [DEBUG]         argv[7] = 32
[20180219-19:51:33] [DEBUG]         argv[8] = -rfbauth
[20180219-19:51:33] [DEBUG]         argv[9] = /home/dave/.vnc/sesman_dave_passwd:10
[20180219-19:51:33] [DEBUG]         argv[10] = -bs
[20180219-19:51:33] [DEBUG]         argv[11] = -nolisten
[20180219-19:51:33] [DEBUG]         argv[12] = tcp
[20180219-19:51:33] [DEBUG]         argv[13] = -localhost
[20180219-19:51:33] [DEBUG]         argv[14] = -dpi
[20180219-19:51:33] [DEBUG]         argv[15] = 96
[20180219-19:51:33] [DEBUG]         argv[16] = (null)
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [ERROR] X server for display 10 startup timeout
[20180219-19:51:43] [INFO ] starting xrdp-sessvc - xpid=1600 - wmpid=1599
[20180219-19:51:43] [ERROR] another Xserver might already be active on display 10 - see log
[20180219-19:51:43] [DEBUG] aborting connection...
[20180219-19:51:43] [INFO ] ++ terminated session:  username dave, display :10.0, session_pid 1598, ip 0.0.0.0:55697 - socket: 12
dave@hal9000:/var/log$

Netstat -l:

Code: Select all

dave@hal9000:/var/log$ netstat -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 localhost:smtp          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:ssh             0.0.0.0:*               LISTEN
tcp6       0      0 localhost:smtp          [::]:*                  LISTEN
tcp6       0      0 [::]:3389               [::]:*                  LISTEN
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN
tcp6       0      0 localhost:3350          [::]:*                  LISTEN
udp        0      0 0.0.0.0:43335           0.0.0.0:*
udp        0      0 0.0.0.0:mdns            0.0.0.0:*
udp        0      0 0.0.0.0:bootpc          0.0.0.0:*
udp        0      0 0.0.0.0:1900            0.0.0.0:*
udp6       0      0 [::]:53584              [::]:*
udp6       0      0 [::]:mdns               [::]:*
raw6       0      0 [::]:ipv6-icmp          [::]:*                  7
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     15104    /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25192    /tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22591    /tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     18395    /tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     19220    /run/user/1000/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     11186    /tmp/ssh-FBYJ1rlvvmr2/agent.1241
unix  2      [ ACC ]     STREAM     LISTENING     25238    /tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     22551    /run/user/118/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     25237    @/tmp/.ICE-unix/1241
unix  2      [ ACC ]     STREAM     LISTENING     1307     /run/lvm/lvmetad.socket
unix  2      [ ACC ]     STREAM     LISTENING     22556    /run/user/118/pulse/native
unix  2      [ ACC ]     STREAM     LISTENING     1310     /run/systemd/journal/stdout
unix  2      [ ACC ]     STREAM     LISTENING     22559    /run/user/118/bus
unix  2      [ ACC ]     STREAM     LISTENING     25191    @/tmp/.X11-unix/X0
unix  2      [ ACC ]     STREAM     LISTENING     22561    /run/user/118/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     22564    /run/user/118/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     22566    /run/user/118/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     22568    /run/user/118/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     25132    /var/run/minissdpd.sock
unix  2      [ ACC ]     STREAM     LISTENING     1330     /run/systemd/fsck.progress
unix  2      [ ACC ]     STREAM     LISTENING     1332     /run/lvm/lvmpolld.socket
unix  2      [ ACC ]     STREAM     LISTENING     20320    @/tmp/dbus-UfzVMsQcvB
unix  2      [ ACC ]     SEQPACKET  LISTENING     1351     /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     25185    @/tmp/dbus-6ofjyHR1
unix  2      [ ACC ]     STREAM     LISTENING     18245    @/tmp/dbus-lxvYA6gm
unix  2      [ ACC ]     STREAM     LISTENING     11869    /var/run/avahi-daemon/socket
unix  2      [ ACC ]     STREAM     LISTENING     11872    /var/run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     23907    /run/user/1000/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     18249    @/tmp/dbus-DUt4Gudv
unix  2      [ ACC ]     STREAM     LISTENING     23912    /run/user/1000/gnupg/S.gpg-agent.extra
unix  2      [ ACC ]     STREAM     LISTENING     23915    /run/user/1000/gnupg/S.gpg-agent.ssh
unix  2      [ ACC ]     STREAM     LISTENING     13163    /var/run/bumblebee.socket
unix  2      [ ACC ]     STREAM     LISTENING     23917    /run/user/1000/gnupg/S.gpg-agent
unix  2      [ ACC ]     STREAM     LISTENING     23919    /run/user/1000/gnupg/S.gpg-agent.browser
unix  2      [ ACC ]     STREAM     LISTENING     23921    /run/user/1000/bus
unix  2      [ ACC ]     STREAM     LISTENING     22590    @/tmp/.ICE-unix/693
unix  2      [ ACC ]     STREAM     LISTENING     22647    /run/user/118/wayland-0
unix  2      [ ACC ]     STREAM     LISTENING     11177    /run/user/1000/keyring/control
unix  2      [ ACC ]     STREAM     LISTENING     23750    /var/run/NetworkManager/private-dhcp
unix  2      [ ACC ]     STREAM     LISTENING     19850    @/tmp/dbus-hOFBHWJFqv
unix  2      [ ACC ]     STREAM     LISTENING     18248    @/tmp/dbus-N9OBLlTV
unix  2      [ ACC ]     STREAM     LISTENING     18394    @/tmp/.X11-unix/X1024
unix  2      [ ACC ]     STREAM     LISTENING     25186    @/tmp/dbus-7hAWJESu
unix  2      [ ACC ]     STREAM     LISTENING     22245    /run/user/1000/keyring/pkcs11
unix  2      [ ACC ]     STREAM     LISTENING     18246    @/tmp/dbus-EdXm47V8
unix  2      [ ACC ]     STREAM     LISTENING     22249    /run/user/1000/keyring/ssh

The error message upon connecting to the linux machine is just «some problem» :D

Понравилась статья? Поделить с друзьями:
  • Volvo xc90 ошибка p0700
  • Vnc error 1 after security negotiation
  • Volvo xc90 ошибка dem p188914
  • Vmwgfx error failed to send host log message
  • Volvo xc90 ошибка 9c03