sbstn Posted October 26, 2018 Posted October 26, 2018 Hello. I've installed the newest Armbian Bionic Ubuntu with the Desktop on my Cubietruck. In the past i had Debian Wheezy running on it with working remote desktop connection over Windows 10 (sesman-xvnc). Now with the new Ubuntu i cant connect anymore to my Cubietruck. If i open the Remote Desktop Tool on Windows 10 i get a connection to my Cubietruck and i can see the login Screen. But there is no more an option (sesman-xvnc). I can only see (xvnc). If i connect through this option i can login to my cubietruck. If login is successful i see only an empty desktop without elements and without a background-image. How can i solve this issue? I have installed "tightvncserver" and "xrdp" used this tutorial: http://www.microdev.it/wp/en/2016/08/11/remote-desktop-setup-for-armbian-on-orange-pi-pc/
Igor Posted October 26, 2018 Posted October 26, 2018 You can connect with root user while it doesn't work as a normal one. Fixing 3rd party user applications bugs is not a part of support and since unrelated to Cubietruck - moving to Peer to peer section.
sbstn Posted October 26, 2018 Author Posted October 26, 2018 I logged in as root user. But desktop is empty. No taskbar, nothing.
Igor Posted October 26, 2018 Posted October 26, 2018 I just happen to install Debian Stretch on Cubietruck http://ix.io/1q4l and I can login as a root, while user login gives this in the logs: Spoiler root@cubietruck:/var/log# tail /var/log/xrdp.log [20181026-10:35:22] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20181026-10:35:22] [DEBUG] Closed socket 18 (AF_UNIX) [20181026-10:35:26] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20181026-10:35:26] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20181026-10:35:26] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 49494) [20181026-10:35:26] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:35:26] [DEBUG] xrdp_mm_module_cleanup [20181026-10:35:26] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:35:26] [DEBUG] Closed socket 18 (AF_UNIX) [20181026-10:35:26] [ERROR] Listening socket is in wrong state, terminating listener root@cubietruck:/var/log# tail -f /var/log/xrdp.log [20181026-10:35:22] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20181026-10:35:22] [DEBUG] Closed socket 18 (AF_UNIX) [20181026-10:35:26] [ERROR] xrdp_mm_connect_chansrv: connect failed trying again... [20181026-10:35:26] [ERROR] xrdp_mm_connect_chansrv: error in trans_connect chan [20181026-10:35:26] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 49494) [20181026-10:35:26] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:35:26] [DEBUG] xrdp_mm_module_cleanup [20181026-10:35:26] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:35:26] [DEBUG] Closed socket 18 (AF_UNIX) [20181026-10:35:26] [ERROR] Listening socket is in wrong state, terminating listener [20181026-10:37:44] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:37:44] [DEBUG] xrdp_mm_module_cleanup [20181026-10:37:44] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:37:44] [DEBUG] Closed socket 18 (AF_UNIX) [20181026-10:37:44] [ERROR] Listening socket is in wrong state, terminating listener [20181026-10:37:50] [INFO ] A connection received from: ::ffff:172.16.100.185 port 59268 [20181026-10:37:50] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:37:50] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389) [20181026-10:37:50] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20181026-10:37:50] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20181026-10:37:50] [DEBUG] Security layer: requested 11, selected 0 [20181026-10:37:50] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:37:50] [ERROR] Listening socket is in wrong state, terminating listener [20181026-10:37:51] [INFO ] A connection received from: ::ffff:172.16.100.185 port 59270 [20181026-10:37:51] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:37:51] [DEBUG] Closed socket 11 (AF_INET6 :: port 3389) [20181026-10:37:51] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem [20181026-10:37:51] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem [20181026-10:37:51] [DEBUG] Security layer: requested 0, selected 0 [20181026-10:37:52] [DEBUG] xrdp_00000f36_wm_login_mode_event_00000001 [20181026-10:37:52] [INFO ] Cannot find keymap file /etc/xrdp/km-00000424.ini [20181026-10:37:52] [INFO ] Cannot find keymap file /etc/xrdp/km-00000424.ini [20181026-10:37:52] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini [20181026-10:37:52] [WARN ] local keymap file for 0x00000424 found and doesn't match built in keymap, using local keymap file [20181026-10:38:06] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350 [20181026-10:38:06] [INFO ] xrdp_wm_log_msg: sesman connect ok [20181026-10:38:06] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait... [20181026-10:38:06] [DEBUG] return value from xrdp_mm_connect 0 [20181026-10:38:06] [INFO ] xrdp_wm_log_msg: login successful for display 11 [20181026-10:38:06] [DEBUG] xrdp_wm_log_msg: started connecting [20181026-10:38:10] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:13] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:17] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:20] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:24] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:27] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:31] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:34] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:38] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:41] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:45] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:48] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:52] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:55] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:38:59] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:02] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:06] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:09] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:13] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:17] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:20] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:24] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:27] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:31] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:34] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:38] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:41] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:45] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:48] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:52] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:55] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:39:59] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:02] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:06] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:09] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:13] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:16] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:20] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:23] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:27] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:30] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:34] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:37] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:41] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:44] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:48] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:51] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:55] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:40:58] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:02] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:05] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:09] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:12] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:16] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:19] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:23] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:26] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:30] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:33] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:36] [DEBUG] xrdp_wm_log_msg: connection problem, giving up [20181026-10:41:36] [DEBUG] Closed socket 17 (AF_UNIX) [20181026-10:41:36] [DEBUG] xrdp_wm_log_msg: some problem [20181026-10:41:36] [DEBUG] xrdp_mm_module_cleanup [20181026-10:41:36] [DEBUG] Closed socket 16 (AF_INET6 ::1 port 49502) [20181026-10:41:36] [DEBUG] Closed socket 12 (AF_INET6 ::ffff:172.16.100.179 port 3389) [20181026-10:41:36] [DEBUG] xrdp_mm_module_cleanup [20181026-10:41:36] [ERROR] Listening socket is in wrong state, terminating listener I experience the same problem in x86 Ubuntu and already wasted time on this ... and since it's impossible to fix all upstream problems, I won't proceed. Try VNC server or look deeper into the problem ...
sbstn Posted October 26, 2018 Author Posted October 26, 2018 Okay so then i install debian again when im home. Thanks Which vnc server do you mean?
Igor Posted October 26, 2018 Posted October 26, 2018 1 hour ago, sbstn said: Which vnc server do you mean? https://www.realvnc.com/en/connect/download/vnc/raspberrypi/ But don't have any experiences. I use CLI most of the time.
tenwiser Posted February 24, 2019 Posted February 24, 2019 Hi, I’ve found a fix for xrdp. The permissions required fixing! For a non-root user, Xorg is not starting because it is not able to write the Xorg.10.log file to the location /home/{user}/.local/share/xorg This xorg directory needs to be created with user ownership not root! i.e. sudo mkdir /home/user/.local/share/xorg sudo chown user:user /home/user/.local/share/xorg FWIW, I found out this by connecting to the xrdp and sesman services, having them running in the foreground to see the diagnostic output. window 1. sudo systemctl stop xrdp.service sudo mkdir -p /var/run/xrdp/sockdir sudo xrdp -ns window 2. sudo /usr/sbin/xrdp-sesman -ns When connecting from the client (in my case xfreerdp) window 2 showed -[20190224-19:06:54] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp (EE) Fatal server error: (EE) Cannot open log file "/home/adrian/.local/share/xorg/Xorg.10.log" (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) BTW, on my desktop build I’ve installed xorgxrdp and done “dpkg-reconfigure xserver-xorg-legacy” to configure xorg access for anybody rather than console. You shouldn’t need to install VNC services (tightvncserver etc…) for your xrdp experience! Hope this helps. -- Adrian C 2
sbstn Posted October 13, 2019 Author Posted October 13, 2019 On 2/24/2019 at 8:27 PM, tenwiser said: Hi, I’ve found a fix for xrdp. The permissions required fixing! For a non-root user, Xorg is not starting because it is not able to write the Xorg.10.log file to the location /home/{user}/.local/share/xorg This xorg directory needs to be created with user ownership not root! i.e. sudo mkdir /home/user/.local/share/xorg sudo chown user:user /home/user/.local/share/xorg FWIW, I found out this by connecting to the xrdp and sesman services, having them running in the foreground to see the diagnostic output. window 1. sudo systemctl stop xrdp.service sudo mkdir -p /var/run/xrdp/sockdir sudo xrdp -ns window 2. sudo /usr/sbin/xrdp-sesman -ns When connecting from the client (in my case xfreerdp) window 2 showed -[20190224-19:06:54] [INFO ] Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp (EE) Fatal server error: (EE) Cannot open log file "/home/adrian/.local/share/xorg/Xorg.10.log" (EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) BTW, on my desktop build I’ve installed xorgxrdp and done “dpkg-reconfigure xserver-xorg-legacy” to configure xorg access for anybody rather than console. You shouldn’t need to install VNC services (tightvncserver etc…) for your xrdp experience! Hope this helps. -- Adrian C Thank you! This fixed my problems!
Recommended Posts