Package Details: xrdp 0.9.1-5

Git Clone URL: https://aur.archlinux.org/xrdp.git (read-only)
Package Base: xrdp
Description: An open source remote desktop protocol (RDP) server
Upstream URL: https://github.com/neutrinolabs/xrdp
Licenses: Apache
Submitter: None
Maintainer: bidulock
Last Packager: bidulock
Votes: 86
Popularity: 2.957277
First Submitted: 2008-01-15 15:02
Last Updated: 2017-01-07 08:42

Pinned Comments

bidulock commented on 2017-01-05 09:04

The PKGBUILD was not removing /etc/xrdp/rsakeys.ini and therefore it was getting overwritten each time. This may have caused problems with cached credentials on the client side. The PKGBUILD and install script will leave /etc/xrdp/rsakeys.ini alone now: install the latest package and then clear your credentials cache on the client side.

Latest Comments

SanskritFritz commented on 2017-01-05 22:07

nasm is still needed, please include it for the makedepends.

colinkeenan commented on 2017-01-05 12:07

You need to add a makedepends to the PKGBUILD. I discovered this trying to build it in a clean chroot:

makedepends=('nasm')

bidulock commented on 2017-01-05 09:04

The PKGBUILD was not removing /etc/xrdp/rsakeys.ini and therefore it was getting overwritten each time. This may have caused problems with cached credentials on the client side. The PKGBUILD and install script will leave /etc/xrdp/rsakeys.ini alone now: install the latest package and then clear your credentials cache on the client side.

lnicola commented on 2017-01-02 17:54

After downgrading from xrdp-git to xrdp, I can't use this anymore. When connecting with cached credentials I get a black screen which turns green if I minimize the RDP client window. Without credentials, I get:

sesman connect ok
sending login info to session manager, please wait...
xrdp_mm_process_login_response: login failed

instead of the credentials prompt.

SanskritFritz commented on 2016-11-02 16:33

bidulock could you please review this thred?
https://bbs.archlinux.org/viewtopic.php?id=218545

dumphblooz commented on 2016-02-08 09:30

$ LC_ALL=C yaourt -S xrdp
...
Generating 512 bit rsa key...

ssl_gen_key_xrdp1 ok

saving to /etc/xrdp/rsakeys.ini

problem opening /etc/xrdp/rsakeys.ini, maybe no rights
error 1 in key_gen, save_all
error: command failed to execute correctly

mabra commented on 2015-12-04 15:18

Hi !

Thanks for your investigation - but nothing changes.
Have you seen my log ?? I am not sure, that all dependencies are really met.
For other distros, I know, that the connecting user must be in some groups,
like 'tsusers' or something like this. This is not the case with my arch setup.
I say this, because the log shows:
>XRDP-sesman[30667]: pam_unix(xrdp-sesman:session): session opened for user mba by (uid=0)
The mba user has uid=1000.

Just an amateurs note.

bidulock commented on 2015-12-04 13:48

Give 0.8.0-4 a try.

mabra commented on 2015-12-04 12:40

Hi !
I re-installed and this time, it builds. But then, I get the same as
>>1. Whenever I connect to the server, a dialog pops up complaining "VNC error - problem connecting", forces me to click "OK" button, then it allows me to enter.<<
For my case, pressing the OK button, just repeats the sequence,
no login possible.
If I specify no password at the client, no dialog appears
at all and login fails.
What I know from other installations is, that there should be a login dialog, where I can additionally specify the module to use [found as sections in the xrdp.ini].

I see some weird entry in the logs and could provide them for both cases,
but where to post ? Here ??

Put my logs into this forum post:
https://bbs.archlinux.org/viewtopic.php?pid=1583667#p1583667

albertnguyen commented on 2015-06-25 02:40

Thanks bidulock. The services are working like a charm now. But there're still some minor issues.

1. Whenever I connect to the server, a dialog pops up complaining "VNC error - problem connecting", forces me to click "OK" button, then it allows me to enter.

2. Some garbage appears in my home directory: thinclient_drives & xrdp-chansrv.log

I don't know if you can resolve it, or that's upstream matter?

Thanks again.

All comments