Raspberry PI 4 Remotedesktop XRDP funktioniert nicht?

Guten Tag,

ich habe letztens die neue 64-Bit variante des Raspberry Pi OS heruntergeladen und habe seitdem das Problem, dass ich mich nicht über das Windows Remotedesktop - Programm verbinden kann bzw. beim Login ein türkisen Screen zu sehen bekomme (siehe Bild).

Nun wollte ich fragen, ob eine Möglichkeit gibt, das Problem zu lösen.

Würde mich über jede Antwort freuen!
MfG

Answer 1

[Lezurex]

Logge dich via SSH ein und schau mittels

sudo journalctl -xe

was das Problem sein könnte bzw. was da für Fehlermeldungen beim Login kommen.

Comments

[Onid08]

Feb 08 14:47:45 raspberrypi xrdp-sesman[569]: [ERROR] sesman_data_in: scp_process_msg failed
Feb 08 14:47:45 raspberrypi xrdp[959]: [INFO ] xrdp_wm_log_msg: login successful for display 11
Feb 08 14:47:45 raspberrypi xrdp[959]: [INFO ] login successful for display 11
Feb 08 14:47:45 raspberrypi xrdp-sesman[960]: pam_unix(xrdp-sesman:session): session opened for user root(uid=0) by (uid=0)
Feb 08 14:47:45 raspberrypi xrdp-sesman[569]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
Feb 08 14:47:45 raspberrypi systemd-logind[456]: New session c3 of user root.
░░ Subject: A new session c3 has been created for user root
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ Documentation: sd-login(3)
░░
░░ A new session with the ID c3 has been created for the user root.
░░
░░ The leading process of the session is 960.
Feb 08 14:47:45 raspberrypi systemd[1]: Started Session c3 of user root.
░░ Subject: A start job for unit session-c3.scope has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit session-c3.scope has finished successfully.
░░
░░ The job identifier is 1314.
Feb 08 14:47:45 raspberrypi xrdp[959]: [ERROR] xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc>
Feb 08 14:47:45 raspberrypi xrdp[959]: [INFO ] error loading libvnc.so specified in xrdp.ini, please add a
Feb 08 14:47:45 raspberrypi xrdp[959]: [INFO ] valid entry like lib=libxrdp-vnc.so or similar
Feb 08 14:47:45 raspberrypi xrdp-sesman[962]: [INFO ] Starting X server on display 11: Xvnc :11 -auth .Xauthority -geometry 1280x1024 -depth 32 -rfbauth /ro>
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [WARN ] Timed out waiting for X server on display 11 to startup
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] Session started successfully for user root on display 11
Feb 08 14:47:55 raspberrypi xrdp-sesman[965]: [INFO ] Starting the xrdp channel server for display 11
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] Session in progress on display 11, waiting until the window manager (pid 961) exits to end the session
Feb 08 14:47:55 raspberrypi xrdp-sesman[961]: [WARN ] Timed out waiting for X server on display 11 to startup
Feb 08 14:47:55 raspberrypi xrdp-sesman[961]: [ERROR] There is no X server active on display 11
Feb 08 14:47:55 raspberrypi xrdp-sesman[961]: [ERROR] A fatal error has occured attempting to start the window manager on display 11, aborting connection
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [WARN ] Window manager (pid 961, display 11) exited quickly (0 secs). This could indicate a window manager con>
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] Calling auth_stop_session and auth_end from pid 960
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: pam_unix(xrdp-sesman:session): session closed for user root
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] Terminating X server (pid 962) on display 11
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] Terminating the xrdp channel server (pid 965) on display 11
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] X server on display 11 (pid 962) returned exit code 1 and signal number 0
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] xrdp channel server for display 11 (pid 965) exit code 0 and signal number 0
Feb 08 14:47:55 raspberrypi xrdp-sesman[960]: [INFO ] cleanup_sockets:
Feb 08 14:47:55 raspberrypi systemd[1]: session-c3.scope: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit session-c3.scope has successfully entered the 'dead' state.
Feb 08 14:47:55 raspberrypi xrdp-sesman[569]: [INFO ] ++ terminated session:  username root, display :11.0, session_pid 960, ip ::ffff:192.168.178.70:59367 >
Feb 08 14:47:55 raspberrypi systemd-logind[456]: Session c3 logged out. Waiting for processes to exit.
Feb 08 14:47:55 raspberrypi systemd-logind[456]: Removed session c3.
░░ Subject: Session c3 has been terminated
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░ Documentation: sd-login(3)
░░
░░ A session with the ID c3 has been terminated.
Feb 08 14:50:05 raspberrypi sudo[891]: pam_unix(sudo:session): session closed for user root
Feb 08 14:50:12 raspberrypi sudo[973]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Feb 08 14:50:12 raspberrypi sudo[973]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)

-------------------------------
Was könnte es denn sein?

[Lezurex]

@Onid08

xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc

Ich weiss nicht, inwiefern das normal ist, könnte aber eine Ursache sein.

Auf jeden Fall versucht er einen Window-Manager zu starten. Dieser crasht dann. Warum dieser crasht, ist hier nicht ersichtlich.

Kannst du während eines Logins mal mit

sudo journalctl -ef

die Logs während eines RDP-Logins verfolgen? Ohne x wird mehr ausgegeben.

[Onid08]

@Lezurex

Hier sind die Error Codes während eines Logins über das Remotedesktop-Programm:

Feb 08 15:04:45 raspberrypi xrdp[2634]: [WARN ] local keymap file for 0x00000407 found and doesn't match built in keymap, using local keymap file

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] connecting to sesman ip 127.0.0.1 port 3350

Feb 08 15:05:01 raspberrypi xrdp-sesman[569]: [INFO ] Socket 8: AF_INET6 connection received from ::1 port 36386

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] xrdp_wm_log_msg: sesman connect ok

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] sesman connect ok

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] sending login info to session manager, please wait...

Feb 08 15:05:01 raspberrypi xrdp-sesman[569]: [INFO ] ++ reconnected session: username pi, display :11.0, session_pid 999, ip ::ffff:192.168.178.70:61241 - socket: 12

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] xrdp_wm_log_msg: login successful for display 11

Feb 08 15:05:01 raspberrypi xrdp-sesman[569]: [ERROR] sesman_data_in: scp_process_msg failed

Feb 08 15:05:01 raspberrypi xrdp-sesman[2663]: [INFO ] Starting session reconnection script on display 11: /etc/xrdp/reconnectwm.sh

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] login successful for display 11

Feb 08 15:05:01 raspberrypi xrdp-sesman[569]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] loaded module 'libxup.so' ok, interface size 10296, version 4

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] started connecting

Feb 08 15:05:01 raspberrypi xrdp[2634]: [INFO ] lib_mod_connect: connecting via UNIX socket

[Lezurex]

@Onid08

Hast du auf dem Pi überhaupt einen Desktop installiert? Also wenn du deinen Pi an einen HDMI Ausgang anschliesst, hast du dann einen Desktop?

[Traveller5712]

@Onid08

Schau mal, dass ist der erste auftretende Fehler:

Feb 08 14:47:45 raspberrypi xrdp[959]: [ERROR] xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc>

Hast Du diesen Fehler behoben und den Eintrag geändert in der xdrp.ini?

[Onid08]

@Traveller5712

Wie kann ich den Fehler denn beheben, bzw. dieses "valid entry lib=libxrdp-vnc" laden?

[Traveller5712]

@Onid08

Die editierst die Datei xrdp.ini auf dem PI, suchst nach dem Eintrag, in welchem "libvnc.so" vorkommt, kommentierst diesen aus und schreibst einen neuen Eintrag hinein welcher so lautet:

lib=libxrdp-vnc

Der einfachheit halber könntest Du aber auch gleich den VNC-Server einschalten am PI (raspi-config) und mit einem VNC-Viewer arbeiten. Denn tatsächlich scheint xrdp nichts anderes zu tuen, als den VNC-Server zu nutzen.