| 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: | 150 |
| Popularity: | 0.29 |
| First Submitted: | 2008-01-15 15:02 (UTC) |
| Last Updated: | 2025-10-07 19:18 (UTC) |
During installation of this package on a RISC-V machine the following error is displayed:
ERROR: xrdp is not available for the 'riscv64' architecture.
but if you select Try to build them anyway, the package is successfully built, passes its tests, and correctly works (together with xorgxrdp)
Added an issue with compilation here: https://github.com/neutrinolabs/xrdp/issues/3654
Hi I get the following error :
make[2]: Entering directory '/home/admin/.cache/pacaur/xrdp/src/xrdp-0.10.4.1/third_party/tomlc99' CC toml.lo CCLD libtoml.la ../../libtool: line 2536: func_append: command not found ../../libtool: line 2537: func_append: command not found
thanks mane! that really helped https://aur.archlinux.org/packages/xrdp#comment-1042503
In xrdp.ini it is recommended to change the user who runs xrdp from root to an unprivileged user. I added instructions for doing this to the wiki, however when the package is updated the permissions and group ownership on /etc/xrdp/{cert,key}.pem are reset. I guess these files are regenerated during the update.
It would therefore be helpful if the installation script ran '/usr/share/xrdp/xrdp-chkpriv' as root after installation to notify the user when the permissions change after installation.
Thanks lyderic for raising this issue and to matt335672 for feeding back the fix. I have bumped the package version which should resolve this issue.
xrdp maintainer here.
We've got a report that an update to the openx264 package from ABI version 164 to 165 has broken 0.10.4.1-1:-
https://github.com/neutrinolabs/xrdp/issues/3633
I think the correct solution here is to rebuild the xrdp package.
Abzie - feel free to comment on the above issue if you think there's an alternative.
Edit: The above issue has been updated by the OP to include a temporary solution using the 'yay' command.
No worries, shit happens. xrdp 0.10.4.1 fixed it for me. Thanks for the immediate reply.
If you're having problems with v0.10.4, please update to v0.10.4.1
https://github.com/neutrinolabs/xrdp/issues/3560
Sorry about the regression.
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.