[X2Go-User] Can't get X2Go connection opened, with error PANIC! The remote NX proxy closed the connection.

[Ulrich Sibiller]

Thanks. So nx is working. To be honest I am out of ideas now. Have you
checked what updates were installed on the server recently? Can you
downgrade and retry?

Uli

On Fri, Mar 10, 2023 at 12:37 PM Kalle Tuulos <kalle at tuulos.net> wrote:
>
> Hi Ulrich
>
> NX Agent appeared and Xterm opened inside it.
>
> BR,
>   Kalle
>
> On Fri, 10 Mar 2023 at 13:20, Ulrich Sibiller <uli42 at gmx.de> wrote:
>>
>> Hi,
>>
>> again I don't see any major problem in libssh related output. But I see these:
>>
>> qt.qpa.xcb: X server does not support XInput 2
>> qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 168,
>> resource id: 309, major code: 130 (Unknown), minor code: 47
>>
>> NX does not support XInput 2. So these errors indicate the session has
>> been opened successfully but some application had a communication
>> problem with the X server (x2goagent in this case).
>>
>> So chances are that xterm, libxcb, libX11 or any accompanying library
>> have been updated recently and are incompatible now. Maybe we can hunt
>> this down by checking this:
>> 1. ssh -X <server> and run "nxagent -D -ac :55" there (nxagent window
>> should open up)
>> 2. ssh server and run "DISPLAY=:55 xterm" there (xterm should open in
>> the nxagent window)
>>
>> Does the xterm come up?
>>
>> Also please repeat with "nxagent -R -ac :55". (no nxagent window will
>> come up, the xterm should open up in its own window in step 2)
>>
>> Uli