Hi Uli,
I can't easily reproduce the problem since I have to travel to a different
location to use the computer that triggered the problem, so I haven't been able
to try your fix.
I will upgrade to 3.5.99.26.
Regards, Michael
On Sat, Feb 27, 2021 at 12:09:39AM +0100, Ulrich Sibiller wrote:
>
As you can see the reconnect goes on after the fonts stuff. So have
you tried my suggested fix?
Please ignore the kde stuff, that is irrelevant and caused by some
default setting in x2go.
Please try upgrading to 3.5.99.26, there are more than 380 patches
included since 3.5.99.23...
Uli
On Fri,
Hi Uli,
Thanks for your quick response.
The nxagent version on the server is 3.5.99.23. The server is an ancient Ubuntu
14.04LTS system. I do have /usr/bin/nxdialog.
Here is my full session.log with the failed font problem:
Session: Session resumed at 'Wed Feb 24 10:53:13 2021'.
Info: Screen
On more thing: You can also install the nxdialog package and point the
NX_CLIENT variable to /usr/bin/nxdialog. This way you will even see
the dialogs! This is how it was intended from the beginning and it is
the correct way but unfortunately nobody has fixed that in x2go yet -
for years.
Uli
On
Honestly I have never seen this. Interestingly when those messages
appear it means that the system will NOT stop the reconnect but go
on:
if (!nxagentReconnectAllFonts(reconnectLossyLevel[FONT_STEP]))
{
if (!nxagentReconnectFailedFonts(reconnectLossyLevel[FONT_STEP]))
{
