Arch Linux User Repository

@Ta180m done: thanks for pointing that out.

Can the maintainer add the line --with-imlib2=yes to the PKGBUILD when running ./configure? This enables support for non-BMP backgrounds for the login screen.

It would be very nice if the dependency to "tigervnc" could be removed. VNC is not a real dependency. Its possible to use i.e. Xorg instead. Since I do not use VNC I have to edit PKGBUILD every build time...

To point to all optional dependencies you can add:

optdepends=('tigervnc: vnc support'
            'xorgxrdp: Xorg drivers'
            'xorgxrdp-glamor: Xorg xrdp drivers with glamor enabled'
            'xorgxrdp-nvidia: Xorg xrdp drivers with nvidia GPU support'
            'pulseaudio-module-xrdp: pulseaudio sound support')

For me I can still not login to Xvnc via xrdp.

But xrdp-sesman spawns a Xvnc server that you can connect to with vnc if you set a password in ~/.vnc/sesman_passwd-user@host:display

Still the same situation as @JoeColl [Xvnx] not working [Xorg] is working, if you install xorgxrdp too. (Tried to connect with Remmina)

Same situation/journal errors as @JoeCool [Xvnc] not working (need revert to 0.9.16-3) [Xorg] is OK

Is the depend on tigervnc for supporting a VNC backend? If so could it be made optional please? Tigervnc does not appear as a dependency in the compiling instructions for xrdp. I also was able to compile without it, after editing the pkgbuild.

Since updating last week I get this error for all VNC connections:

[20211004-11:12:58] [ERROR] xrdp_wm_log_msg: error loading libvnc.so specified in xrdp.ini, please add a valid entry like lib=libxrdp-vnc.so or similar
[20211004-11:12:58] [INFO ] error loading libvnc.so specified in xrdp.ini, please add a
[20211004-11:12:58] [INFO ] valid entry like lib=libxrdp-vnc.so or similar

libxup still works fine

before it looked like this:

[20211001-01:22:39] [INFO ] loaded module 'libvnc.so' ok, interface size 4072, version 4

I have two libvnc.so on my system: xrdp: /usr/lib/xrdp/libvnc.so
tigervnc: /usr/lib/xorg/modules/extensions/libvnc.so

which one should it be using? ldd shows no trouble for both of them.

Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Window manager (pid 63273, display 10) exited quickly (0 secs). This could indicate a window manager config problem

Maybe a window manager config problem?

Xrdp connected with blank screen after update. In to logs writed this:

Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Socket 8: AF_INET6 connection received from ::1 port 36028
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: pam_systemd_home(xrdp-sesman:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Terminal Server Users group is disabled, allowing authentication
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] ++ created session (access granted): username hopyres, ip ::ffff:192.168.1.8:34116 - socket: 12
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] starting Xorg session...
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Starting session: session_pid 63272, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff:192.168.1.8:34116 - socket: 12, user name hopyres
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: [INFO ] [session start] (display 10): calling auth_start_session from pid 63272
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [ERROR] sesman_data_in: scp_process_msg failed
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_unix(xrdp-sesman:session): session opened for user hopyres(uid=1000) by (uid=0)
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_systemd(xrdp-sesman:session): Failed to create session: No child processes
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_env(xrdp-sesman:session): deprecated reading of user environment enabled
Oct 04 09:03:30 htsrv xrdp-sesman[63274]: [INFO ] Starting X server on display 10: /usr/lib/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Timed out waiting for X server on display 10 to startup
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Session started successfully for user hopyres on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63280]: [INFO ] Starting the xrdp channel server for display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Session in progress on display 10, waiting until the window manager (pid 63273) exits to end the session
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [WARN ] Timed out waiting for X server on display 10 to startup
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] There is no X server active on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Window manager (pid 63273, display 10) exited quickly (0 secs). This could indicate a window manager config problem
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Calling auth_stop_session and auth_end from pid 63272
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: pam_unix(xrdp-sesman:session): session closed for user hopyres
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Terminating X server (pid 63274) on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Terminating the xrdp channel server (pid 63280) on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] X server on display 10 (pid 63274) returned exit code 1 and signal number 0
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] xrdp channel server for display 10 (pid 63280) exit code 0 and signal number 0
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] cleanup_sockets:
Oct 04 09:03:40 htsrv xrdp-sesman[63179]: [INFO ] ++ terminated session:  username hopyres, display :10.0, session_pid 63272, ip ::ffff:192.168.1.8:34116 - socket: 12

Where correct this troubles?