Replies: 2 comments
-
You need to solve this:-
As you say, it's unlikely to be permissions on the file itself (if you're sure sesman is running as root). However:-
|
Beta Was this translation helpful? Give feedback.
-
Brilliant, thanks so much. I had completely forgotten about SELinux. (I use Ubuntu the most) But now, I've changed SELinux to Permissive and it's now working! The current installation is now as per your .10.2 release, with the addition of dbus-launch in startwm.sh
I got a blank screen after the splash screen without this line, in spite of me using a separate login account. Xsession/Xinitrc support is a bit vague in Tumbleweed, so I created a .xsession with this one line in it:
Now files are:
For completeness, after building via my user account, I installed with " As MicroOS is an immutable OS, a better way would be to create a RPM package on a conventional machine first. Thanks very much PS: |
Beta Was this translation helpful? Give feedback.
-
I have the following error message in /var/log/xrdp-sesman.log when I try to run using systemd services.
But if I run on the command line,
#xrdp -n --dump-config
#xrdp-sesman -n --dump-config
it works fine and I can get a login
The server is a derivative of Tumbleweed, called MicroOS Kalpa (ie running Plasma6)
The problem is present with the version from the Tumbleweed repository
xrdp 0.9.23.1
xrdp-sesman 0.9.23.1
of course, these run as root
I have build xrdp and xorgxrdp from source with versions
xrdp 0.10.2
xrdp-sesman 0.10.2
and problem is same whether I run using user xrdp or as root.
However, using Tumbleweed itself (not MicroOS) the versions in the repository work fine.
I can't see this is a simple Unix permission issue as I'm sure I would have found it.
What could be upsetting Xrdp/Xorgxrdp when run via Systemd?
Beta Was this translation helpful? Give feedback.
All reactions