Closed mallardtheduck closed 4 months ago
@mallardtheduck - I don't have great news for you I'm afraid. After a bit of searching about, this seems to be a known issue with no workarounds. See google/fscrypt#350.
The only way forward I can see is to upgrade to xrdp v0.10.x when it's released. This version does not fork in a way which confuses fscrypt
(and other PAM modules). This was a pretty major architectural change, and can' be back-ported to the v0.9.x series.
v0.10.x is very nearly due for release, but to run it on Ubuntu 22.04 you'll need to build it yourself or find a trusted source for an update.
I'm closing this as there's little else we can do here.
xrdp version
0.9.17
Detailed xrdp version, build options
Operating system & version
Ubuntu 22.04.3 LTS aarch64
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorgxrdp
What desktop environment do you use?
xfce
Environment xrdp running on
OrangePi Zero3
What's your client?
Microsoft Remote Desktop (Mac)
Area(s) with issue?
Session manager (sesman)
Steps to reproduce
Attempt to connect. The problem stated after fscrypt-ing the home directory, but occurs even if the directory is already unlocked (e.g. by opening an SSH session first).
There is no autologin or even so much as a graphical login enabled for the system, so no "double login" issue. Xrdp works fine for another user without an encrypted home directory.
✔️ Expected Behavior
A working login...
❌ Actual Behavior
Black screen for a while, followed eventually by:
Anything else?
As far as I can tell, xrdp-sesman is hanging before getting as far as starting the X server. The instance of it can only be removed with SIGKILL. No ".xorgxrdp.10.log" is created (even modifying sesman.ini to create this outside of the home directory didn't change anything). Switching to Xvnc didn't change things either.
xrdp.log:
xrdp-sesman.log:
xrdp/xorg.conf (although this probably isn't relevant as there's no evidence that any attempt to actually run X is occuring):