mobmarcus Posted February 4, 2023 Share Posted February 4, 2023 (edited) SBC Client Armbian : 22.11.4 Jammy SBC : RockPro64 Kernel : 5.15.0-rockchip64 aarch64 Windows Host Windows 10 Windows Remote Desktop Connecting through LAN (No wifi) Hi, I followed this simple ,great guide here to get remote desktop access from Windows working. sudo apt install xrdp xorgxrdp sudo systemctl enable xrdp sudo reboot When I use the root account to log in to an Armbian session it works seemlessly, however if I use a normal (non su) then I get the log in password screen pop up, but the desktop doesnt appear ir blinks and crashes. Tailing the live system log, with dmesg -W and I get these errors root@rockpro64:~# dmesg -W [ 1057.390095] hdmi-audio-codec hdmi-audio-codec.5.auto: Only one simultaneous stream supported! [ 1057.390855] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 1057.391983] ff8a0000.i2s-i2s-hifi: soc_pcm_open() failed (-22) Anyone know how I can login as non root ? Edited February 5, 2023 by mobmarcus Added more details on systems in post 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted February 5, 2023 Share Posted February 5, 2023 Maybe the user account needs to be added to xrdp or similar usergroup for permission? 0 Quote Link to comment Share on other sites More sharing options...
Prax Posted February 22, 2023 Share Posted February 22, 2023 Im having the same problem. I only can login with root using xrdp. AlwaysGroupCheck in sesman.ini already is on false. Group shouldnt matter. 0 Quote Link to comment Share on other sites More sharing options...
audioz Posted February 26, 2023 Share Posted February 26, 2023 yes i have the same problem please help i dont want login on root 0 Quote Link to comment Share on other sites More sharing options...
Prax Posted February 27, 2023 Share Posted February 27, 2023 Which GUI are you using? I deinstalled xrdp and Im using gnome remote desktop without problems now. 0 Quote Link to comment Share on other sites More sharing options...
GianniDPC Posted March 12, 2023 Share Posted March 12, 2023 I have the same problem. Does anyone have a solution? I'm using Armbian 23.02 btw. This is really annoying.. If there isn't any fix does anyone know a version where I could downgrade to were this issue wasn't present? 0 Quote Link to comment Share on other sites More sharing options...
unspecified Posted March 13, 2023 Share Posted March 13, 2023 (edited) I also have encountered this problem and have some additional information to share. I have found that I can only log in to Armbian (from Windows) using RDP from an account that has never logged in to the Armbian console before, for example, the root account. However, once I log in to such an account at the Armbian console, I am no longer able to log in to Armbian via that account using RDP. Interestingly, this limitation persists even if I delete and re-add the account without logging in via the console. As a workaround I could create a local and a remote account and never log in to the remote account from the console. I've added some system information from the inxi command output. Ubuntu jammy based Armbian for Le Potato Armbian 23.02.2 stable, 10.9.2.243 inxi -Fxz System: Kernel: 6.1.11-meson64 aarch64 bits: 64 compiler: N/A Desktop: Xfce 4.16.0 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish) Machine: Type: ARM System: Libre Computer AML-S905X-CC details: N/A CPU: Info: quad core model: ARMv8 v8l variant: cortex-a53 bits: 64 type: MCP arch: v8l rev: 4 Speed (MHz): avg: 1512 min/max: 100/1512 cores: 1: 1512 2: 1512 3: 1512 4: 1512 bogomips: N/A Features: Use -f option to see features Graphics: Device-1: meson-gxl-dw-hdmi driver: meson_dw_hdmi v: N/A bus-ID: N/A Device-2: meson-gxl-vpu driver: meson_drm v: N/A bus-ID: N/A Device-3: meson-gxl-mali driver: lima v: kernel bus-ID: N/A Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev gpu: meson_dw_hdmi,meson_drm,lima resolution: 1364x768~50Hz OpenGL: renderer: llvmpipe (LLVM 15.0.6 128 bits) v: 4.5 Mesa 22.2.5 direct render: Yes Network: Device-1: meson-gxbb-dwmac driver: meson8b_dwmac v: N/A port: N/A bus-ID: N/A IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Info: Processes: 192 Uptime: 19m Memory: 1.89 GiB used: 752.4 MiB (38.9%) Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 clang: 14.0.0-1ubuntu1 Packages: 1569 Shell: Zsh v: 5.8.1 inxi: 3.3.13 Edited March 13, 2023 by unspecified clarification, additional information 0 Quote Link to comment Share on other sites More sharing options...
Igor Posted March 13, 2023 Share Posted March 13, 2023 On 2/27/2023 at 8:36 PM, Prax said: Im using gnome remote desktop without problems now. 10 hours ago, GianniDPC said: Does anyone have a solution? I also use it with Jammy / Gnome, image with preinstalled desktop, and it works. 10 hours ago, GianniDPC said: I'm using Armbian 23.02 btw. This tells nothing. Logs or at least telling a lot more then "i am using Armbian". Besides different HW properties that could cause troubles, there are different package releases and different DEs. 0 Quote Link to comment Share on other sites More sharing options...
GianniDPC Posted March 13, 2023 Share Posted March 13, 2023 @Igor Log from armbian monitor: https://paste.armbian.com/riqawabuxu I'm using this image:https://redirect.armbian.com/orangepipc/Jammy_current_xfce. FYI: I have deleted the user that was created the first time just to test, and recreated that user myself. Only difference is it doesn't close my Remote Desktop application like before but instead i get a blueish screen with the message "connection problem, giving up" after some time. I tried different things to get it working but I'm at a loss here.. /var/log/xrdp-sesman.log: When logging in as root (working): [20230313-20:42:02] [INFO ] Socket 8: AF_INET6 connection received from ::1 port 54042 [20230313-20:42:03] [INFO ] Terminal Server Users group is disabled, allowing authentication [20230313-20:42:03] [INFO ] ++ created session (access granted): username root, ip ::ffff:192.168.0.171:61132 - socket: 12 [20230313-20:42:03] [INFO ] starting Xorg session... [20230313-20:42:03] [INFO ] Starting session: session_pid 2490, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:192.168.0.171:61132 - socket: 12, user name root [20230313-20:42:03] [INFO ] [session start] (display 10): calling auth_start_session from pid 2490 [20230313-20:42:03] [ERROR] sesman_data_in: scp_process_msg failed [20230313-20:42:03] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans [20230313-20:42:03] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20230313-20:42:03] [INFO ] Found X server running at /tmp/.X11-unix/X10 [20230313-20:42:03] [INFO ] Found X server running at /tmp/.X11-unix/X10 [20230313-20:42:03] [INFO ] Session started successfully for user root on display 10 [20230313-20:42:03] [INFO ] Found X server running at /tmp/.X11-unix/X10 [20230313-20:42:03] [INFO ] Session in progress on display 10, waiting until the window manager (pid 2491) exits to end the session [20230313-20:42:03] [INFO ] Starting the default window manager on display 10: /etc/xrdp/startwm.sh [20230313-20:42:03] [INFO ] Starting the xrdp channel server for display 10 Log file when logging in as gianni (not working) [20230313-20:32:29] [INFO ] shutting down sesman 1 [20230313-20:32:29] [INFO ] starting xrdp-sesman with pid 2383 [20230313-20:32:36] [INFO ] Socket 8: AF_INET6 connection received from ::1 port 47732 [20230313-20:32:37] [INFO ] Terminal Server Users group is disabled, allowing authentication [20230313-20:32:37] [INFO ] ++ created session (access granted): username gianni, ip ::ffff:192.168.0.171:60180 - socket: 12 [20230313-20:32:37] [INFO ] starting Xorg session... [20230313-20:32:37] [INFO ] Starting session: session_pid 2396, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:192.168.0.171:60180 - socket: 12, user name gianni [20230313-20:32:37] [INFO ] [session start] (display 10): calling auth_start_session from pid 2396 [20230313-20:32:37] [ERROR] sesman_data_in: scp_process_msg failed [20230313-20:32:37] [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans [20230313-20:32:38] [INFO ] Starting X server on display 10: /usr/lib/xorg/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log [20230313-20:32:48] [WARN ] Timed out waiting for X server on display 10 to startup [20230313-20:32:48] [INFO ] Session started successfully for user gianni on display 10 [20230313-20:32:48] [INFO ] Starting the xrdp channel server for display 10 [20230313-20:32:48] [INFO ] Session in progress on display 10, waiting until the window manager (pid 2410) exits to end the session [20230313-20:32:48] [WARN ] Timed out waiting for X server on display 10 to startup [20230313-20:32:48] [ERROR] There is no X server active on display 10 [20230313-20:32:48] [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection [20230313-20:32:48] [WARN ] Window manager (pid 2410, display 10) exited quickly (0 secs). This could indicate a window manager config problem [20230313-20:32:48] [INFO ] Calling auth_stop_session and auth_end from pid 2396 [20230313-20:32:48] [INFO ] Terminating X server (pid 2411) on display 10 [20230313-20:32:48] [INFO ] Terminating the xrdp channel server (pid 2425) on display 10 [20230313-20:32:48] [INFO ] X server on display 10 (pid 2411) returned exit code 1 and signal number 0 [20230313-20:32:48] [INFO ] xrdp channel server for display 10 (pid 2425) exit code 1 and signal number 0 [20230313-20:32:48] [INFO ] cleanup_sockets: [20230313-20:32:48] [INFO ] ++ terminated session: username gianni, display :10.0, session_pid 2396, ip ::ffff:192.168.0.171:60180 - socket: 12 0 Quote Link to comment Share on other sites More sharing options...
Kostiantyn Posted March 30, 2023 Share Posted March 30, 2023 I solve this problem. You need to disable user autologin in ligthtDM. Configure /etc/lightdm/lightdm.conf file, or create him if they not exist. Content of lightdm.conf: [Seat:*] autologin-guest=false autologin-user= autologin-user-timeout=0 0 Quote Link to comment Share on other sites More sharing options...
Solution unspecified Posted April 2, 2023 Solution Share Posted April 2, 2023 (edited) I have it working now. I tested it on a fresh installation. The issue was resolved by installing the 'xauth' command: sudo apt-get update sudo apt install xauth After installing 'xauth', RDP connections from Windows worked as expected. I'm not entirely sure why this fixed the problem, but my hypothesis is that 'xauth' is required to add the authorization information used to connect to the X server and stored in the '.Xauthority' file. Edited April 3, 2023 by unspecified retracted workaround, added solution 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.