The file /etc/xrdp/reconnectwm.sh
is overwritten on each update.
I recommend to add it to the backup=
section of of the PKGBUILD file.
(Like startwm.sh
already is.)
Search Criteria
Package Details: xrdp 0.10.4.1-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/xrdp.git (read-only, click to copy) |
---|---|
Package Base: | xrdp |
Description: | An open source remote desktop protocol (RDP) server |
Upstream URL: | https://github.com/neutrinolabs/xrdp |
Keywords: | rdp vnc xdrp |
Licenses: | Apache-2.0 |
Submitter: | None |
Maintainer: | Abzie |
Last Packager: | Abzie |
Votes: | 149 |
Popularity: | 0.48 |
First Submitted: | 2008-01-15 15:02 (UTC) |
Last Updated: | 2025-07-07 13:39 (UTC) |
Dependencies (12)
- ffmpeg (ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-cudaAUR, ffmpeg-ffplayoutAUR, ffmpeg-headlessAUR, ffmpeg-amd-full-gitAUR, ffmpeg-amd-fullAUR, ffmpeg-obsAUR, ffmpeg-libfdk_aacAUR, ffmpeg-decklinkAUR, ffmpeg-fullAUR, ffmpeg-full-gitAUR, ffmpeg-gitAUR)
- fuse3 (fuse3-gitAUR)
- imlib2
- libfdk-aac (libfdk-aac-gitAUR)
- libxrandr (libxrandr-gitAUR)
- x264 (x264-tmod-gitAUR, x264-gitAUR)
- cmocka (cmocka-gitAUR) (make)
- nasm (nasm-gitAUR) (make)
- check (check-gitAUR) (check)
- realvnc-vnc-serverAUR (optional)
- tigervnc (tigervnc-gitAUR) (optional)
- tightvncAUR (optional)
Required by (6)
- pulseaudio-module-xrdp
- pulseaudio-module-xrdp-git
- xorgxrdp (make)
- xorgxrdp-devel-git (make)
- xorgxrdp-glamor (make)
- xorgxrdp-nvidia (make)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 19 Next › Last »
unruh commented on 2023-09-08 08:58 (UTC)
trainzkid commented on 2023-07-23 03:23 (UTC)
@Abzie, just closing the rdp window. I know the proper way is to log out, but I'm not sure I can easily expect end users to do this, especially windows users.
The bigger worry I have is that xrdp isn't properly handling closing active sessions when it's restarted via systemd from what I can tell. Not sure if this is specific to the Arch version, but I'm not seeing this issue anywhere else according to Google.
Abzie commented on 2023-07-22 21:15 (UTC)
Generally a black screen indicates you are still "logged in" to your previous session.
How are you disconnecting from the first session?
trainzkid commented on 2023-07-22 20:38 (UTC)
Anyone else run into issues logging back into a previously active xrdp session following a restart of the service?
I had some applications open on my xrdp desktop and then logged out of xrdp, restarted the service, and was unable to log in again: plasma would start to load and then I'd get the generic black screen with xorg's massive black X cursor. All my googling tells me xrdp is supposed to clean up sessions when restarting.
To resolve, I went through all plasma and xorg processes and killed them (many were in a defunct state). Then when I tried to log in via xrdp, plasma started up just fine.
I'm using /usr/lib/plasma-dbus-run-session-if-needed startplasma-x11
in the .xinitrc
if that helps.
fow0ryl commented on 2022-12-20 17:42 (UTC)
As described earlier in comments in Manjaro the /usr/bin/Xorg is a script that decides to use /usr/lib/Xorg or /usr/lib/Xorg.wrapper. But when using /usr/lib/Xorg.wrapper you have to allow anybody to start X (Add allowed_users=anybody to /etc/X11/Xwrapper.config). Maybe there are more things to do.
The most easy way is to set param=/usr/lib/Xorg in sesman.ini. This setting will be saved, even with new versions of xrdp, since sesman.ini isn't overwritten by default.
Remember the default configuration is good if you are extendig a simple desktop system with xrdp. But when using a real xrdp server with multiple users and no local desktop its better to create a global xorg.conf https://aur.archlinux.org/packages/xrdp?O=60#comment-762246
chinanuke commented on 2022-12-20 03:03 (UTC) (edited on 2022-12-20 03:10 (UTC) by chinanuke)
Unable to login after upgrading xrdp to 0.9.21.1, here is part of my xrdp-sesman log.
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [INFO ] Socket 12: AF_INET6 connection received from ::1 port 53686
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: pam_systemd_home(xrdp-sesman:auth): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found. Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [INFO ] Terminal Server Users group is disabled, allowing authentication
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [INFO ] ++ created session (access granted): username peng, ip ::1:51522 - socket: 12 Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [INFO ] starting Xorg session...
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [INFO ] Starting session: session_pid 2596, display :10.0, width 1920, height 1080, bpp 24, client ip ::1:51522 - socket: 12, user name peng
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2596]: [INFO ] [session start] (display 10): calling auth_start_session from pid 2596 Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [ERROR] sesman_data_in: scp_process_msg failed
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2596]: pam_unix(xrdp-sesman:session): session opened for user peng(uid=1000) by (uid=0) Dec 20 10:53:13 NukeDesktop xrdp-sesman[2596]: pam_systemd(xrdp-sesman:session): Failed to create session: No child processes
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2109]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
Dec 20 10:53:13 NukeDesktop xrdp-sesman[2598]: [INFO ] Starting X server on display 10: /usr/bin/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -l
ogfile .xorgxrdp.%s.log
Dec 20 10:53:22 NukeDesktop xrdp-sesman[2596]: [WARN ] Timed out waiting for X server on display 10 to startup
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: [INFO ] Session started successfully for user peng on display 10
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2602]: [INFO ] Starting the xrdp channel server for display 10
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: [INFO ] Session in progress on display 10, waiting until the window manager (pid 2597) exits to end the session
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2597]: [WARN ] Timed out waiting for X server on display 10 to startup
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2597]: [ERROR] There is no X server active on display 10
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2597]: [ERROR] A fatal error has occurred attempting to start the window manager on display 10, aborting connection
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: [WARN ] Window manager (pid 2597, display 10) exited quickly (0 secs). This could indicate a window manager config problem
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: [INFO ] Calling auth_stop_session and auth_end from pid 2596
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: pam_unix(xrdp-sesman:session): session closed for user peng
Dec 20 10:53:23 NukeDesktop xrdp-sesman[2596]: [INFO ] Terminating X server (pid 2598) on display 10
I have noticed that this update has some changes in /etc/xrdp/sesman.ini
and the path to Xorg executable is changed from param=/usr/lib/Xorg
to param=Xorg
(which results in /usr/bin/Xorg
). When I tried to change the path back to /usr/lib/Xorg
and restart xrdp.service
, I was able to login to my desktop as before.
What is the difference between /usr/lib/Xorg
and /usr/bin/Xorg
? Or is something wrong with my PATH?
learnedbyerror commented on 2022-12-17 19:46 (UTC) (edited on 2022-12-17 19:52 (UTC) by learnedbyerror)
I am still too new to Arch and AUR to know how to make a pull request to the actual xrdp AUR package. I apologize for my ignorance but hope that someone can use the info below to upgrade their xrdp implementation to 0.9.21.1 - the latest release as of today.
I have updated the PKGBUILD and arch-config.diff from 0.9.19 to 0.9.21.1. They are contained in the following gists:
-
PKGBUILD - https://gist.github.com/lbe/80b17cc2c9acb6a357ad64b2223db491
-
arch-conf.diff - https://gist.github.com/lbe/3c2658466175f9ff8c541566e59ffc0d
Please note that this PKGBUILD does NOT contain a dependency upon tigervnc.
If you wish to use tigervnc, you will need to install it separately.
To use these:
-
git clone https://aur.archlinux.org/xrdp.git
-
Replace PKGBUILD with - https://gist.github.com/lbe/80b17cc2c9acb6a357ad64b2223db491
-
Replace arch-config.diff with - https://gist.github.com/lbe/3c2658466175f9ff8c541566e59ffc0d
-
Run
make -si
- This will sync the xrdp source and build the install package and then install the same if the build is successful
HTH, lbe
kescherAUR commented on 2022-12-10 12:44 (UTC)
0.9.21 was released with a bunch of security fixes.
kescherAUR commented on 2022-12-06 00:52 (UTC)
Here's my diff to simply update this package to 0.9.20: https://0x0.st/okCa.diff
The tigervnc dependency isn't fixed in the diff above, sorry.
@pdynarowski Cleanly rebuild the xrdp package instead, it builds fine with OpenSSL 3.
pdynarowski commented on 2022-11-24 09:52 (UTC) (edited on 2022-11-24 10:05 (UTC) by pdynarowski)
it doesn't work after update my manjaro (2022-11-2022)
journalctl -xe
lis 24 10:26:38 manjaro systemd[1]: xrdp.service: Job xrdp.service/start failed with result 'dependency'.
xrdp-sesman -ns
xrdp-sesman: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
xrdp -ns
xrdp: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
SOLUTION :)
pacman -Syu openssl-1.1
Pinned Comments
Abzie commented on 2024-05-10 14:40 (UTC)
If upgrading from 0.9.x, please read the 'User Changes' section from the release page:https://github.com/neutrinolabs/xrdp/releases/tag/v0.10.0
There is one breaking change that require manual intervention but there are three other changes that will continue to work for now.
xRDP states: Users are urged to heed any generated configuration warnings and update their configurations. Later major versions of xrdp may remove these warnings, or introduce other behaviours for the affected parameters.