Excellent, however: downloading the PKGBUILD, updating it and makepkg-ing it creates an error about a missing install file. Will have to find a more detailed manual somewhere…
I seem to have the source tarball. Can’t easily find a download link from the packages page. https://aur.archlinux.org/packages/xrdp/
There is a snapshot tarball, but that only holds some scripts.
I can confirm that xrdp, xorgxrdp and pulseaudio-module-xrdp all work when compiled for aarch64, update the arch line as Strit mentions and makepkg compiles to working code.
Remember to set the file /etc/X11/Xwrapper.config to read:
allowed_users = anybody
Or something more secure. You will likely have to create that file.
Also, you might have to setup the /etc/xrdp/startwm.sh to have this:
as the wm_start contents. Not sure what the eval … thing does.
Also, once connected, remember to enable the sound on the server by running to start pulseaudio on the server:
pulseaudio -D
That streams audio to the client using the xrdp sink. If you go back to normal non-xrdp use, you have to rescan the audio devices / sinks to find the normal audio devices again.
Which is what is needed to build the package. It contains all the PKGBUILD needs, that it does not download from other places. Like scripts and .install files.
Thanks Strit. I got it working.
Perhaps you could (suggest someone to) update the xrdp package on AUR to mark it for aarch64 as well.
The xrdp package works for me on aarch64, with the provided PKGBUILD and other scripts as-is with the exception of the arch aarch64 parameter.
Freerdp looks like a somewhat user-unfriendly RDP client, but appears very, very, very configurable and seems feature rich /feature complete. As in, there is quite a few options.
And it appears you can use it as a server as well! (Which explains freerdp as an alternative solution to xrdp.)
Also, there seems to be some kind of WebConnect / HTML5 server as well, perhaps in a way a little like Apache Guacamole.
Which means you could host the RDP server and a WebConnect / HTML5 server, all from a Manjaro ARM device (if it is all supported). And then connect from anywhere using a browser.
So, in theory that all seems nice.
Documentation however, is quite another issue.
Plenty of options and configuration, but not much accessible documentation I could find. And quite a bit of what I found seems fairly dated.
Interesting possibilities, but requires quite a bit of time to investigate.
Thanks for mentioning it 0n0w1c ! Seems like the possibilities here are bountiful.