Package Details: xrdp 0.9.19-2

Git Clone URL: (read-only, click to copy)
Package Base: xrdp
Description: An open source remote desktop protocol (RDP) server
Upstream URL:
Licenses: Apache
Submitter: None
Maintainer: bidulock
Last Packager: bidulock
Votes: 131
Popularity: 0.43
First Submitted: 2008-01-15 15:02 (UTC)
Last Updated: 2022-03-23 05:20 (UTC)

Pinned Comments

Latest Comments

Haystack commented on 2022-05-03 13:44 (UTC)

As others have asked, please remove the tigervnc dependency. fow0ryl's suggested optdepends should be perfect. Dependency on tigervnc is unnecessary and if you have tightvnc or realvnc installed it creates a dependency conflict and you are forced to uninstall them in order to install xrdp which shouldn't be the case.

russkel commented on 2022-03-21 12:09 (UTC) (edited on 2022-03-21 12:10 (UTC) by russkel)

Optional dependencies should typically be marked as optional.

fow0ryl commented on 2022-03-20 02:16 (UTC)

The point is, that tigervnc is not needed for some setups. And tigervnc itself depends on many packages itself. And each dependend package could have dependencies itself. In fact we get a dependency tree, and potential problems without any need. So if someone wants to use thightvnc and xrdp that's not possible because tigervnc blocks installation of tightvnc. The clean way is to define only those packages as dependent which are realy depend. The other packages belong to optdepends.

By the way. What is the answer to this question: Why tigervnc is defined as dependency while xorg-xrdp ist not?

bidulock commented on 2022-03-15 09:31 (UTC)

@Ta180m tigervnc is a small package in community. What is the problem?

Ta180m commented on 2022-03-11 21:19 (UTC)

I also agree with @fow0ryl that the tigervnc dependency should be removed since it isn't necessary when using Xorg. Can the maintainer please make the edit that @fow0ryl suggested?

bidulock commented on 2022-01-13 19:00 (UTC)

@Ta180m done: thanks for pointing that out.

Ta180m commented on 2022-01-12 23:15 (UTC)

Can the maintainer add the line --with-imlib2=yes to the PKGBUILD when running ./configure? This enables support for non-BMP backgrounds for the login screen.

fow0ryl commented on 2021-11-30 15:42 (UTC) (edited on 2021-11-30 15:46 (UTC) by fow0ryl)

It would be very nice if the dependency to "tigervnc" could be removed. VNC is not a real dependency. Its possible to use i.e. Xorg instead. Since I do not use VNC I have to edit PKGBUILD every build time...

To point to all optional dependencies you can add:

optdepends=('tigervnc: vnc support'
            'xorgxrdp: Xorg drivers'
            'xorgxrdp-glamor: Xorg xrdp drivers with glamor enabled'
            'xorgxrdp-nvidia: Xorg xrdp drivers with nvidia GPU support'
            'pulseaudio-module-xrdp: pulseaudio sound support')

JoeCool commented on 2021-11-23 15:40 (UTC)

For me I can still not login to Xvnc via xrdp.

But xrdp-sesman spawns a Xvnc server that you can connect to with vnc if you set a password in ~/.vnc/sesman_passwd-user@host:display

tachtler commented on 2021-11-21 07:08 (UTC) (edited on 2021-11-21 07:16 (UTC) by tachtler)

Still the same situation as @JoeColl [Xvnx] not working [Xorg] is working, if you install xorgxrdp too. (Tried to connect with Remmina)

GeorgeJP commented on 2021-10-14 15:09 (UTC)

Same situation/journal errors as @JoeCool [Xvnc] not working (need revert to 0.9.16-3) [Xorg] is OK

russkel commented on 2021-10-08 03:39 (UTC)

Is the depend on tigervnc for supporting a VNC backend? If so could it be made optional please? Tigervnc does not appear as a dependency in the compiling instructions for xrdp. I also was able to compile without it, after editing the pkgbuild.

JoeCool commented on 2021-10-07 16:30 (UTC) (edited on 2021-10-07 16:34 (UTC) by JoeCool)

Since updating last week I get this error for all VNC connections:

[20211004-11:12:58] [ERROR] xrdp_wm_log_msg: error loading specified in xrdp.ini, please add a valid entry like or similar
[20211004-11:12:58] [INFO ] error loading specified in xrdp.ini, please add a
[20211004-11:12:58] [INFO ] valid entry like or similar

libxup still works fine

before it looked like this:

[20211001-01:22:39] [INFO ] loaded module '' ok, interface size 4072, version 4

I have two on my system: xrdp: /usr/lib/xrdp/
tigervnc: /usr/lib/xorg/modules/extensions/

which one should it be using? ldd shows no trouble for both of them.

bidulock commented on 2021-10-07 06:16 (UTC)

Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Window manager (pid 63273, display 10) exited quickly (0 secs). This could indicate a window manager config problem

Maybe a window manager config problem?

hopyres commented on 2021-10-04 06:15 (UTC)

Xrdp connected with blank screen after update. In to logs writed this:

Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Socket 8: AF_INET6 connection received from ::1 port 36028
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: pam_systemd_home(xrdp-sesman:account): systemd-homed is not available: Unit dbus-org.freedesktop.home1.service not found.
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Terminal Server Users group is disabled, allowing authentication
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] ++ created session (access granted): username hopyres, ip ::ffff: - socket: 12
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] starting Xorg session...
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [INFO ] Starting session: session_pid 63272, display :10.0, width 1920, height 1080, bpp 24, client ip ::ffff: - socket: 12, user name hopyres
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: [INFO ] [session start] (display 10): calling auth_start_session from pid 63272
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [ERROR] sesman_data_in: scp_process_msg failed
Oct 04 09:03:30 htsrv xrdp-sesman[63179]: [ERROR] sesman_main_loop: trans_check_wait_objs failed, removing trans
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_unix(xrdp-sesman:session): session opened for user hopyres(uid=1000) by (uid=0)
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_systemd(xrdp-sesman:session): Failed to create session: No child processes
Oct 04 09:03:30 htsrv xrdp-sesman[63272]: pam_env(xrdp-sesman:session): deprecated reading of user environment enabled
Oct 04 09:03:30 htsrv xrdp-sesman[63274]: [INFO ] Starting X server on display 10: /usr/lib/Xorg :10 -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp -logfile .xorgxrdp.%s.log
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Timed out waiting for X server on display 10 to startup
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Session started successfully for user hopyres on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63280]: [INFO ] Starting the xrdp channel server for display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Session in progress on display 10, waiting until the window manager (pid 63273) exits to end the session
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [WARN ] Timed out waiting for X server on display 10 to startup
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] There is no X server active on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63273]: [ERROR] A fatal error has occured attempting to start the window manager on display 10, aborting connection
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [WARN ] Window manager (pid 63273, display 10) exited quickly (0 secs). This could indicate a window manager config problem
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Calling auth_stop_session and auth_end from pid 63272
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: pam_unix(xrdp-sesman:session): session closed for user hopyres
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Terminating X server (pid 63274) on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] Terminating the xrdp channel server (pid 63280) on display 10
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] X server on display 10 (pid 63274) returned exit code 1 and signal number 0
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] xrdp channel server for display 10 (pid 63280) exit code 0 and signal number 0
Oct 04 09:03:40 htsrv xrdp-sesman[63272]: [INFO ] cleanup_sockets:
Oct 04 09:03:40 htsrv xrdp-sesman[63179]: [INFO ] ++ terminated session:  username hopyres, display :10.0, session_pid 63272, ip ::ffff: - socket: 12

Where correct this troubles?

Ta180m commented on 2021-09-17 01:18 (UTC)

Can the maintainer add the configuration files /etc/pam.d/xrdp-sesman and /etc/xrdp/ to be backed up when updating the package? The ArchWiki suggests making edits to those files, and it's problematic that they get overwritten when this package is updated.

prg commented on 2021-09-14 22:22 (UTC) (edited on 2021-09-30 18:18 (UTC) by prg)

This is likely not a packaging issue, but just an FYI to other users: as of 0.9.17, logins are failing and I'm seeing these errors:

xrdp-sesman[1170]: pam_systemd(xrdp-sesman:session): Failed to create session: No child processes xrdp-sesman[1165]: [ERROR] sesman_data_in: scp_process_msg failed

Reverting back to 0.9.16 with the same configuration fixes the issue - just wanted to give a heads up.

edit: fixed this by upgrading xorgxrdp to the .17 version (missed upgrading xorgxrdp for an unrelated reason)

travnick commented on 2021-08-05 07:34 (UTC)

It simply hits me with build failure:

vnc.c: In function ‘lib_data_in’:
../common/log.h:144:33: error: ‘response_code’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
  144 | #define LOG(log_level, args...) log_message(log_level, args)
      |                                 ^~~~~~~~~~~

marlop352 commented on 2021-06-26 22:18 (UTC)

thanks for adding it @bidulock!

sshaikh commented on 2021-06-20 11:14 (UTC)

For those wondering what @luksab's request was, it was to add base-devel to makedepends.

(Don't mean to overstep, sometimes "uninformed requests" serve as learning exercises for others - like me!)

luksab commented on 2021-06-20 10:04 (UTC)

Thank you! I deleted my uninformed request.

SanskritFritz commented on 2021-06-18 15:36 (UTC)

marlop352 commented on 2021-06-10 02:43 (UTC)

could you add aarch64 to the arch list?

tachtler commented on 2021-06-09 06:36 (UTC)

@bidulock I did another reinstall today and set the port definition to tcp6://:3389. xrdp is now reachable via ipv4 and ipv6. Thanks for your fast support!

bidulock commented on 2021-06-06 02:59 (UTC)

@tachtler done.

I turned on a bunch more features: if this causes problems for anyone, let me know and I will turn them back off.

tachtler commented on 2021-05-29 09:18 (UTC)

@bidulock Would it be possible that the BUILD() option --enable-ipv6 is enabled by default in PKGBUILD?

bidulock commented on 2021-05-12 23:20 (UTC)

Got the /usr/lib/Xorg patched now too.

fow0ryl commented on 2021-05-04 08:30 (UTC)

Since I'm using Manjaro I can only tell about this ... /usr/bin/Xorg is a simple script, which decides to start /usr/lib/Xorg or /usr/lib/Xorg.wrap. So using /usr/lib/Xorg is the recommended way. Starting in fact /usr/lib/Xorg.wrap did not work, even via /usr/bin/Xorg.

sshaikh commented on 2021-05-03 14:04 (UTC) (edited on 2021-05-03 14:06 (UTC) by sshaikh)

@bidulock @for0ryl

I can confirm that I can only establish a connection when I set Param=/usr/lib/Xorg in sesman.ini. Neither Xorg nor /usr/bin/Xorg work.

The fix is to read the wiki of course, where it advises to:

Add allowed_users=anybody to /etc/X11/Xwrapper.config to allow anybody to start X

This however is not required if Param is set as per sesman.ini, so I guess there's a choice here. However I'm not sure there's any harm in setting Param to a setting more specific to Arch so I would support such a change.

Also do you run a login manager? That might also be significant (I don't).

More info:

sshaikh commented on 2021-05-02 20:44 (UTC)

That's great, thank you!

Thanks for the Xorg pointer. I checked and indeed show the same as you. I'll do some more testing to see if I can recreate the issue.

bidulock commented on 2021-05-02 19:42 (UTC)

@sshaikh got your pre_start/post_start included in 0.9.16 update.

bidulock commented on 2021-05-02 19:32 (UTC)

[brian@piggy xrdp]$ which Xorg /usr/bin/Xorg [brian@piggy xrdp]$ pacman -Qo /usr/bin/Xorg /usr/bin/Xorg is owned by xorg-server 1.20.11-1 [brian@piggy xrdp]$

sshaikh commented on 2021-04-28 17:48 (UTC) (edited on 2021-04-29 14:34 (UTC) by sshaikh)


~~That's my point - I don't have the problem anymore. I suspect something has changed in my system as I have an Xorg in my /sbin that wraps the only in /use/lib, so I believe there's no reason the default shouldn't work.~~

~~That said I did have to do it previously, so maybe unfortunately it's a specific Manjaro issue now.~~

I lied - after a reboot I lost the /sbin/Xorg wrapper somehow. Changing semsan manually brought xrdp back.

fow0ryl commented on 2021-04-28 17:39 (UTC)

@sshaikh Same problem with Xorg path as I have reported on 2020-06-02. But no response ....

sshaikh commented on 2021-04-28 16:16 (UTC) (edited on 2021-04-28 16:17 (UTC) by sshaikh)

Separately I also had to previously apply the following change to sesman.ini while using xorg-git, although this isn't needed here which is great.

For my curiosity has another workaround been introduced?

; Specify the path of non-suid Xorg executable. It might differ depending
; on your distribution and version. Find out the appropreate path for your
; environment. The typical path is known as follows:
; Fedora 26 or later    :  param=/usr/libexec/Xorg
; Debian 9 or later     :  param=/usr/lib/xorg/Xorg
; Ubuntu 16.04 or later :  param=/usr/lib/xorg/Xorg
; Arch Linux            :  param=/usr/lib/Xorg
; CentOS 7              :  param=/usr/bin/Xorg or param=Xorg
; CentOS 8              :  param=/usr/libexec/Xorg


sshaikh commented on 2021-04-28 16:15 (UTC) (edited on 2021-04-28 16:17 (UTC) by sshaikh)

I always have to manually add the following to, as this sets up the correct bash variables/startup for my session, similar to all of the other DE starts.

Is there any reason why this isn't part of the Arch package, or why Arch users wouldn't want it?

   # arch user
   if [ -r ~/.xinitrc ]; then
+    pre_start
     . ~/.xinitrc
+    post_start
     exit 0
   # arch

leapofazzam commented on 2021-01-23 16:41 (UTC)

Why this package is still in aur, can we move this package to extra repo

Excalibur commented on 2021-01-04 20:05 (UTC) (edited on 2021-01-04 21:47 (UTC) by Excalibur)

I have updated the package to 0.9.15:

makepkg -si installed the package successfully. Combined with vanilla xorgxrdp from AUR I have a working RDP connection now.

I tried to enable glamor in xorgxrdp and some additional codecs / options in xrdp. It didn't work as-is, so I just stopped.

I have changed the verification from SHA to GPG since the signature is included in the release file, and hopefully this can help speeding up the update of AUR in the future. This is the first time for me to do this so please check if I'm doing it correctly.

weridoarch commented on 2020-12-29 11:54 (UTC) (edited on 2020-12-29 12:02 (UTC) by weridoarch)

kde桌面连接成功显示黑屏 <img alt="" src="" />

yan12125 commented on 2020-12-28 14:17 (UTC)

0.9.14 can be built by pulling a upstream fix. Here is a PKGBUILD that works with xorgxrdp:

shmilee commented on 2020-11-26 17:37 (UTC)

Can we add '--enable-ipv6' flag?

sshaikh commented on 2020-11-21 17:18 (UTC)

In I had to wrap the sourcing of .xinit with calls to the pre_ and post_start in order to have the profile.d scripts called (LANG wasn't set for me).

Perhaps push that into your patch?

DAC324 commented on 2020-09-28 12:07 (UTC)

Does not work with Remmina 1.4.8 - it is simply not found in Remmina :(

Magicloud commented on 2020-09-25 07:34 (UTC)

Upstream has been as 0.9.14 for a while, and this is blocking packages like xorgxrdp to build.

usul0184 commented on 2020-09-15 06:01 (UTC)

I'm the original reporter at If anyone else can chime in with his/her experience over there, that would be great. I don't think I have enough knowledge to provide more help.

On another note, I ended up replacing all of with simply exec /etc/lightdm/Xsession dbus-run-session startxfce4. That solved a lot of problems. The /etc/lightdm/Xsession puts my environment in the same state as if I logged on locally via LightDM (my display manager); I'm guessing you can do something equivalent with other display managers. I think dbus-launch is deprecated and it doesn't terminate when you log out, so dbus-run-session seems preferable.

meop commented on 2020-09-14 21:58 (UTC)

FYI, the PAM issue is being discussed here:

Shatur commented on 2020-09-04 08:35 (UTC)

@tingleby, are you talking about pam_systemd(xrdp-sesman:session): Failed to create session: No child processes in systemctl status xrdp-sesman? Yes, I have the same issue with KDE plasma.

tingleby commented on 2020-09-01 22:13 (UTC)

Yeah it seems the latest pam and pambase updates messes with sesman being about to hand of to systemd-login.

pdynarowski commented on 2020-08-31 07:54 (UTC) (edited on 2020-09-01 21:32 (UTC) by pdynarowski)

01.09.2020 I find solution. In .xinitrc i had: exec startxfce4, now i have: dbus-launch startxfce4 and everythig works fine.

31.08.2020 On last update system ( pacman -Syu ) xrdp doesnt work. Xfce4 works correctly on local machine but xrdp doesn't work. I have message: Unable to contact server settings. Couldnot connect: Connection refused. System is ArchLinux (not Manjaro)

fow0ryl commented on 2020-08-23 21:00 (UTC)

Changing ~/.xinitrc is no clean solution for a real multiuser system. Since everybody has to change it. And if the users are real windows users, most of them did not know how to do that ... And if you did not change the sesman.ini you will get tons of messages.

usul0184 commented on 2020-08-23 18:05 (UTC)

I run Manjaro, and I didn't have to change sesman.ini. That said, I did have to change my .xinitrc to launch xfce4 using "exec dbus-launch startxfce4".

On a different note, in /etc/xrdp/, is there a reason why pre_start and post_start aren't used for arch? Then nothing in /etc/profile.d/ and other files are run, which can cause issues.

fow0ryl commented on 2020-06-02 23:20 (UTC) (edited on 2020-06-02 23:22 (UTC) by fow0ryl)

For use with Manjaro /etc/xrdp/sesman.ini has to be modified. If the path to the Xorg binary and for xorg.conf is not changed, only root logins are possible and you have to handle with Xwrapper.config and you are getting really big logfiles, with many many errors. Maybe it's the same with pure ArchLinux ....

; Manjaro               :  param=/usr/lib/Xorg
Of course you have to change /etc/X11/xinit/xinitrc or ~/.xinitrc and add a line to start your DE. i.e. exec startlxqt

felipefdl commented on 2020-01-31 13:12 (UTC)

Please add support for aarch64, I changed PKGBUILD and it works great.

anandsingh2903 commented on 2019-10-17 08:09 (UTC)

My RDP is not connecting since i have installed latest version. RDP logs in successfully but then it says error.

SESMAN-LOGS : another XServer might already be active on display 10.

I have tried rebooting many times but it is still not working.

ameeno commented on 2019-09-03 09:33 (UTC)

The latest version 0.9.11 broke my xrdp hyper-v enhanced session.

i had to roll back to the previous commit manually

vn158 commented on 2019-01-13 00:00 (UTC)

Replace /etc/default/locale with /etc/locale.conf in /etc/xrdp/ to get session with systemwide locales.

guygma commented on 2018-12-04 13:13 (UTC)

Pretty sure xorgxrdp is a dependency... At least the developers of this software seem to think so: "Connect to a Linux desktop using RDP from anywhere (requires xorgxrdp Xorg module)". For some reason the maintainer of the xorgxrdp PKGBUILD on AUR made this package a dependency of that one, which does not seem technically correct---irrespective of how useful xorgxrdp may or may not be without xrdp.

bidulock commented on 2018-09-26 15:55 (UTC)

fuse is a dependency.

fsmoak commented on 2018-09-25 09:24 (UTC) (edited on 2018-09-25 10:04 (UTC) by fsmoak)

Error when compiling due to missing dependency.

checking jpeglib.h presence... yes checking for jpeglib.h... yes checking for FUSE... no configure: error: please install libfuse-dev or fuse-devel

CAUSE: Error in Package-Database.

Solution: (with sledgehammer method) reinstall everything "sudo pacman --force -Syu $(pacman -Qnq)"

boppbo commented on 2018-03-12 00:02 (UTC)

Would be nice if you could add the configure option "--enable-vsock". It is used for enhanced hyper-v sessions. Documentation is sparse, but more info can be found at

grawity commented on 2017-10-31 18:09 (UTC)

Feature request: Add the configure option "--enable-ipv6" for, well, IPv6 support.

danl commented on 2017-09-27 01:56 (UTC)

Maintainer: this may be related to the comment by hz0885 on 20170326. I had an issue regarding xrdp and pam modules. If I didn't set "session optional" in /etc/pam.d/xrdp-sesman, the dbus configuration did not work properly. See for more info.

bidulock commented on 2017-03-31 20:47 (UTC)

With version 0.9.2 do we still need tigervnc dependency? Or, can it move to optdepends?

hz0885 commented on 2017-03-26 20:03 (UTC)

If you use LXQT as your desktop the xrdp-sesman pam module needs to change from system-auth to system-login. Otherwise the desktop environment will not initialize properly. Maybe its worth while to place that pam module also in the backup list.

celilo commented on 2017-03-12 21:45 (UTC)

Error when compiling due to missing dependency. I have openssl installed. I don't see packages as described in Arch packages or AUR. Thoughts? ______________ configure: error: please install libssl-dev or openssl-devel ==> ERROR: A failure occurred in build(). Aborting... :: failed to build xrdp package(s)

meta commented on 2017-02-24 02:17 (UTC)

Hi, I'm from xrdp team. Can you add "--enable-painter" option in configure? It saves people using Android client from connection issue.

SanskritFritz commented on 2017-01-05 22:07 (UTC)

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

colinkeenan commented on 2017-01-05 12:07 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

bidulock could you please review this thred?

dumphblooz commented on 2016-02-08 09:30 (UTC) (edited on 2016-02-08 09:30 (UTC) by dumphblooz)

$ 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 (UTC)

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 (UTC)

Give 0.8.0-4 a try.

mabra commented on 2015-12-04 12:40 (UTC) (edited on 2015-12-04 12:49 (UTC) by mabra)

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:

albertnguyen commented on 2015-06-25 02:40 (UTC)

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.

bidulock commented on 2015-06-24 13:01 (UTC)

Sorry, typo in --with-systemdsystemunitdir=/usr/lib/systemd/system 0.8.0-3 is corrected.

albertnguyen commented on 2015-06-24 04:31 (UTC)

Since update to 0.8.0-2 I cannot find xrdp.service and xrdp-sesman.service. Have to use /etc/xrdp/ to control the program.

EricT commented on 2015-02-26 09:48 (UTC)

Hello, with this version : xrdp 0.6.1-1 Awesome not started I Have change this : nano /etc/xrdp/ line 6 : SESSIONS="gnome-session blackbox fluxbox startxfce4 startkde xterm" by : SESSIONS="gnome-session blackbox fluxbox startxfce4 startkde awesome xterm" systemctl restart xrdp && systemctl restart xrdp-sesman And so good :) Eric

albertnguyen commented on 2014-12-16 01:22 (UTC)

It works with tigervnc 1.4.0-1.

Esspy commented on 2014-12-02 16:41 (UTC)

Hi. I use Schnouki PKGBUILD, but there are additional steps to be done to get xrdp working again. 1. run xrdp-keygen xrdp > /etc/xrdp/rsakey.ini to generate RSA keys 2. use PAM from gentoo good luck.

frilled commented on 2014-11-27 09:02 (UTC)

Same here. Couldn't yet find out why. If I ssh -X into the box after the failed login attempt, I can start a vncviewer on localhost:9010 just fine - as the VNC server is indeed running correctly.

oaheix commented on 2014-11-27 02:16 (UTC)

@albertnguyen: Same problem, tried your way, and it works, thanks!

albertnguyen commented on 2014-11-25 10:11 (UTC)

Latest upgrade of tigervnc to 1.3.90-1 made me unable to enter xrdp desktop. I had to return to 1.3.1-6. Anyone with similar symptom?

JonnyJD commented on 2014-11-13 15:56 (UTC)

@Schnouki: This is an orphan package. You can just upload the new PKGBUILD (and disown afterwards if you don't want to maintain).

Schnouki commented on 2014-11-13 08:51 (UTC)


tzok commented on 2014-10-20 09:42 (UTC)

I have to disown the package as I no longer use xrdp and have little time to spare unfortunately.

tgc commented on 2014-10-17 14:19 (UTC)

There is a new version ready at

tzok commented on 2013-12-10 18:44 (UTC)

I can fix the SESSIONS variable (I personally use openbox-session also missing on the default list). But I do not get the second part of your request. Manpage for xrdp.ini does not mention "address=..." parameter. Did you mean "ip=..." in the connection section? For each of predefined connection? Regards, tzok

vtanger commented on 2013-12-10 07:19 (UTC)

Not sure whether this is better suited here or for upstream: In /etc/xrdp/ please add "lxsession" to the SESSIONS variable. In /etc/xrdp/xrdp.ini please add the lines "# bind to localhost only, e.g. to tunnel via SSH" followed by "#address=" for those who wish to tunnel xrdp via SSH so they can find it more easily. Thanks! Volker

russo79 commented on 2013-09-22 09:36 (UTC)

@spitfire No, it shouldn't. Take a look at:

spitfire commented on 2013-09-22 09:34 (UTC)

'patch', 'libtool' should be added to make deps.

tzok commented on 2013-09-16 18:27 (UTC)

@arkhad, did you download this tarball? It has all the files required to build xrdp.

commented on 2013-09-11 22:09 (UTC)

Hi @tzok, I'm trying to run the script but it tells me that xrdp.service can't be found, and I assume it'll complaind about the other sources execpt the tar. Thanks in advance for any advice.

tzok commented on 2013-09-11 11:41 (UTC)

@phindela, done! However I have no means to test whether armv6h support is true. I rely on you on this matter. If there are people complaining about problems for this architecture and I would still have no way to help, I will probably make this package orphan so that someone else can adopt it

commented on 2013-09-06 21:19 (UTC)

Hello just built and tried xrdp on Raspberry Pi. works flawless. Please add 'armv6h' to PKGBUILD. thanks in advance

tzok commented on 2013-06-10 13:31 (UTC)

That's right, I forgot to remove it from package(). It is fixed now, thanks for noticing!

russo79 commented on 2013-06-10 13:22 (UTC)

@tzok You seem to have forgot to remove the sed command in the package() function, since it is now done in the prepare function. Otherwise, great!

tzok commented on 2013-06-10 11:30 (UTC)

Hi russo79, thank you very much for your comment! I have adapted the PKGBUILD as suggested. Best regards, tzok

russo79 commented on 2013-06-05 21:54 (UTC)

Hi tzok Nice to see someone taking over this package. Some suggestions to your package: 1. You should move the code that patches xrdp source into a prepare() function. It is now the new standard. I would also do the sed operation in it. prepare() { cd "${pkgname}-v${pkgver}" patch -p1 -i $srcdir/0001-Fix-the-build-with-automake-1.13.patch # Fix path in file sed -i 's|/usr/local/sbin|/usr/bin|' instfiles/ } 2. You should edit the service file so that they point to /usr/bin instead of /usr/sbin. Even if /usr/sbin exists, it is now a symlink that will probably be removed some day xrdp-sesman.service: ExecStart=/usr/bin/xrdp-sesman $SESMAN_OPTIONS ExecStop=/usr/bin/xrdp-sesman $SESMAN_OPTIONS --kill xrdp.service: ExecStart=/usr/bin/xrdp $XRDP_OPTIONS ExecStop=/usr/bin/xrdp $XRDP_OPTIONS --kill

tzok commented on 2013-06-05 18:35 (UTC)

Added version with patch and adjusted to the new filesystem scheme

alex-eri commented on 2013-05-12 22:17 (UTC)

pls add patch to pkgbuild

russo79 commented on 2013-01-16 08:40 (UTC)

bluerider, patch has already been submited upstream.

bluerider commented on 2013-01-16 03:25 (UTC)

The error can be fixed by changing "AM_CONFIG_HEADER" to "AC_CONFIG_HEADERS" in This error should be reported upstream.

bluerider commented on 2013-01-16 03:15 (UTC)

I can't seem to compile this : /usr/bin/autoconf /usr/bin/automake /usr/bin/libtool autoreconf: Entering directory `.' autoreconf: not using Gettext autoreconf: running: aclocal --force error: 'AM_CONFIG_HEADER': this macro is obsolete. You should use the 'AC_CONFIG_HEADERS' macro instead. /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 autoreconf: aclocal failed with exit status: 1

th-fr commented on 2013-01-12 12:48 (UTC)

Yes, it works. Sry for the misunderstanding and thank you for the fix.

russo79 commented on 2013-01-12 12:33 (UTC)

@th-fr Oh, another thing. If you used the download link from pastebin the files may have a CR/LF line end instead of a LF only. I suggest you to do a copy/paste of the contents of the files and save them with your favorite editor. This may solve your problem.

russo79 commented on 2013-01-12 12:26 (UTC)

@th-fr Hi I just tested on my system (again), and the patch worked perfectly. Could you try to remove your src directory and try makepkg again?

th-fr commented on 2013-01-12 12:23 (UTC)

@russo79: Your patch does not work properly, because the file path seems to be wrong. ==> Making package: xrdp 0.6.0-3 (Sa 12. Jan 13:08:50 CET 2013) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving Sources... -> Found xrdp-v0.6.0.tar.gz -> Found xrdp.service -> Found xrdp-sesman.service -> Found fix_for_automake-1.13.patch ==> Validating source files with md5sums... xrdp-v0.6.0.tar.gz ... Passed xrdp.service ... Passed xrdp-sesman.service ... Passed fix_for_automake-1.13.patch ... Passed ==> Extracting Sources... -> Extracting xrdp-v0.6.0.tar.gz with bsdtar ==> Removing existing pkg/ directory... ==> Starting build()... (Patch is indented 8 spaces.) can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |diff -ru xrdp-v0.6.0/ xrdp-v0.6.0-buildfix/ |--- xrdp-v0.6.0/configure.ac2012-02-21 20:00:55.000000000 +0100 |+++ xrdp-v0.6.0-buildfix/configure.ac2013-01-11 00:31:49.349673370 +0100 -------------------------- File to patch: xrdp-v0.6.0/ xrdp-v0.6.0/ patching file patch: **** malformed patch at line 6: AC_PREREQ(2.59)

russo79 commented on 2013-01-10 23:39 (UTC)

th-fr New version of the PKGBUILD that fix the build problem: You will also need to create a file named fix_for_automake-1.13.patch with the content from here:

techryda commented on 2013-01-10 23:10 (UTC)

Builds fine here... I don't use the package anymore though, so let me know if you'd like to maintain it and I'll disown it.

th-fr commented on 2013-01-10 21:22 (UTC)

Did not build, seems like the build script (not the PKGBUILD) of xrdp does is a bit outdated: ==> Starting make... /usr/bin/autoconf /usr/bin/automake /usr/bin/libtool /usr/bin/pkg-config autoreconf: Entering directory `.' autoreconf: not using Gettext autoreconf: running: aclocal --force error: 'AM_CONFIG_HEADER': this macro is obsolete. You should use the 'AC_CONFIG_HEADERS' macro instead. /usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is expanded from... the top level autom4te: /usr/bin/m4 failed with exit status: 1 aclocal: error: echo failed with exit status: 1 autoreconf: aclocal failed with exit status: 1

techryda commented on 2012-10-11 21:04 (UTC)


ShyPixie commented on 2012-10-11 20:49 (UTC)

I get error: cp: can not obtain state "../*. service": File or directory not found Please, replace cp ../*.service usr/lib/systemd/system by cp ${srcdir}/*.service usr/lib/systemd/system

techryda commented on 2012-08-16 17:07 (UTC)

Also updated to use tigervnc

techryda commented on 2012-08-16 16:44 (UTC)

Updated...I was mistaken about 0.7.0 being's actually 0.6.0 Added systemd support

techryda commented on 2012-08-16 13:57 (UTC)

0.7.0 is out Also, please add: --with-systemdsystemunitdir=/usr/lib/systemd/system to the 'configure' line, and: sed -i 's|EnvironmentFile=.*|EnvironmentFile=/etc/xrdp/xrdp.ini|' usr/lib/systemd/system/xrdp.service sed -i 's|EnvironmentFile=.*|EnvironmentFile=/etc/xrdp/xrdp.ini|' usr/lib/systemd/system/xrdp-sesman.servic to the end of the package() function. This will enable systemd support to the package Thanks

JonnyJD commented on 2012-03-13 17:33 (UTC)

I wrote some notes on this setup in

JonnyJD commented on 2012-03-13 03:49 (UTC)

The git version works a lot better for me (especially sesman-vnc, but also the colors are correct with vnc-any)

eworm commented on 2011-12-22 08:12 (UTC)

Can you please add "--prefix=/usr --sysconfdir=/etc" to ./configure? Thanks!

jsteel commented on 2011-10-30 20:36 (UTC)

Disowning... cannot get this to work. Should just require "sudo /etc/xrdp/ start" but I get "error - problem connecting" when trying to connect via RDP.

commented on 2011-08-06 22:58 (UTC)

Another vote for an update, this would rock. I'd help but I'm an arch n00b.

commented on 2011-05-27 12:00 (UTC)

Update, please ... or orphan

commented on 2011-01-19 02:09 (UTC)

Package is too old :(