Ok, so the reason for the failure is the client side. Btw: Why don't you have a xkeyboard extension loaded on the client?Have you tried installing the font package you mentioned before on the client?UliMatteo Guareschi <matteo.guareschi@gmail.com> schrieb am Di., 18. Mai 2021, 23:56:Thank you Uli,On the client side I get the securitypolicy error followed by:nxagentGetRemoteXkbExtension: WARNING! Faulted to query XKB extension.Unable to query XKEYBOARD extension.Error: Aborting session with 'Could not open default font 'fixed''.On the server side, if I try to run the same command it opens a window which remains black until I close it. Not sure what is the intended behavior.I should also mention that the client on Linux uses a custom keyboard layout, not present on the server, but even after loading more standard ones, or disabling keyboard configuration, there is no difference.I appreciate your help!On Tue, May 18, 2021 at 1:33 PM Ulrich Sibiller <uli42@gmx.de> wrote:On Mon, May 17, 2021 at 12:33 AM Matteo Guareschi
<matteo.guareschi@gmail.com> wrote:
>
> Hello,
> I have been trying to figure this out for a while now. Every time I start a session from my client (arch) to my server (arch xfce), the session seems to start fine, but terminates instantly.
> The client reads:
>
> Loop: WARNING! Overriding auxiliary X11 port with new value '1'.
> Warning: Overriding auxiliary X11 port with new value '1'.
not a problem.
> Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
> Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Also not a problem, rather a bug in x2go that has always been there.
$SOMEONE should fix it..
> Error: keyboard file not created: Is a directory
this is intended behaviour.
> Error: Aborting session with 'Could not open default font 'fixed''.
This is the cause of your trouble.
> error opening security policy file /usr/local/lib/nx/X11/xserver/SecurityPolicy
This is also uncritical but should happen.
Both previous messages indicate that something is not correct in the
way NX was built on your system.
> At this point I have exhausted my resources. I have tried the client from a different OS and the result is the same. From what I understand the fixed font error is most likely a red herring, but I have installed xorg-fonts-misc for what it's worth, with no difference.
It is not a red herring. This code clearly shuts down nxagent when the
font is missing. Need to find out why that is because on my system I
do not have the fixed font installed but it works.
Please try the following: Connect with ssh -X to the server and run
"/bin/nxagent :5 -ac" . Can you start it that way?
Uli
> I would really appreciate any help.
--Matteo Michele Guareschi