Package Details: xrdp 0.10.6-1

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: 152
Popularity: 0.51
First Submitted: 2008-01-15 15:02 (UTC)
Last Updated: 2026-04-19 11:59 (UTC)

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.

Latest Comments

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 20 Next › Last »

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

FYI, the PAM issue is being discussed here: https://github.com/neutrinolabs/xrdp/issues/1684

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/startwm.sh, 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 .... 

[Xorg]
; Manjaro               :  param=/usr/lib/Xorg
param=/usr/lib/Xorg
param=-config
param=/etc/X11/xrdp/xorg.conf
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.

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 20 Next › Last »