Arch Linux User Repository

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.

Why not raise an issue on xorgxrdp for the answer from the devs? We can only speculate on the AUR comments.

Thankfully, someone has already asked and the answer is: "It's not out yet, but it's pretty imminent." https://github.com/neutrinolabs/xorgxrdp/issues/360#issuecomment-2545158754

@Abzie - how did they test-build this release without xrdp 0.10.2? Either this wasn't test-built - which is bad - or there's a version 0.10.2 of xrdp out there nobody can find - also bad.

Not sure how this could possibly be updated without xrdp-0.10.2.

@unclehook there’s not much I can do until upstream releases xrdp 0.10.2 to satisfy the hard dependency.

xorgxrdp has been updated to "xorgxrdp 0.10.3-1" and broke this package:

checking for xrdp >= 0.10.2... no
configure: error: Package requirements (xrdp >= 0.10.2) were not met:

Package dependency requirement 'xrdp >= 0.10.2' could not be satisfied.
Package 'xrdp' has version '0.10.1', required version is '>= 0.10.2'

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XRDP_CFLAGS
and XRDP_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
==> ERROR: A failure occurred in build().
    Aborting...

There is definitely a work around (which I have not yet searched for, or found).

I just wanted to point this out.

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.

I was originally hesitant to update to 0.10, but xorgxrdp was updated to 0.10.0 as a full stable release and requires xrdp 0.10.x - so I made changes to the packaging for XRDP and pulled to the same version as xorgxrdp :)

@Abtie Ok, I don't really like seeing the word beta in version. But since I don't know the details of the xrdp code and you are the maintainer, I'll leave it to you to make the right choices.

0.9.x is reaching EOL as hinted at by the developers of XRDP and is less maintained and 900 commits behind the current development branch for 0.10.x which include the same fixes and other improvements over 0.9.x

0.9.25 does not include anything new that is missing from 0.10.x, and the bugfix is a backport from 0.10.x to the 0.9.x branch.

The AUR's guidelines are the same as the official repos i.e. the most recent release that upstream regard as stable should be packaged. As of yesterday, at the time of writing this comment, 0.10.0_beta.1 was the latest release available on GH and was uploaded to the AUR appropriately.

Any bugs or issues found should be reported upstream wherever possible.

Why provide a beta version with the xrdp package?

It would be better to use an xrdp-dev or xrdp-git package.

The latest version is 0.9.25

i have the same problem with xorgxrdp on all my pcs, but at least xvnc - tigervnc works fine

edit: xorgxrdp-glamor was updated and now it works fine