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 Fri, Feb 26, 2021 at 10:40 PM Ulrich Sibiller <ul...@gmx.de> wrote:
>
> 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]))
> {
> failedStep = FONT_STEP;
> goto nxagentReconnectError;
> }
> else
> {
> #ifdef WARNING
> fprintf(stderr, "nxagentReconnectSession: WARNING! Unable to
> retrieve all the fonts currently in use. "
> "Missing fonts have been replaced.\n");
> #endif
>
> nxagentLaunchDialog(DIALOG_FONT_REPLACEMENT);
> }
> }
>
> What version of the nxagent package do you have on the server? And
> what distribution do you have on the server? Please post the lines
> before and after the messages you posted (from
> /tmp/.x2go-<user>/C..../session.log)
>
> Update: after thinking for some time you probably suffer from a bug
> that is old indeed: dialogs are displayed using the binary that is
> referred to by the NX_CLIENT variable. This variable is set wrong
> inside x2go and will call a binary that suspends the session. So to
> fix this
> do the following on the server (as I don't know what distribution you
> are using I do not know where the x2gosuspendagent binary resides, so
> please adapt the path accordingly):
> 1. mv /usr/bin/x2gosuspendagent /usr/bin/x2gosuspendagent.orig
> 2. ln -s /usr/bin/true /usr/bin/x2gosuspendagent
>
> Unfortunately you will have to fix it again after an update of the x2go stuff.
>
> Alternatively you can change the line in x2gosuspendagent that sets
> the NX_CLIENT variable. But this will only affect future sessions
> while above change will also work for running sessions. You will have
> to fix this after an update again, too.
>
> Hope that helps,
>
> Uli
>
>
> On Fri, Feb 26, 2021 at 10:07 PM Michael Ashley <m.ash...@unsw.edu.au> wrote:
> >
> > Hi folks,
> >
> > Last week I connected to a long-running x2go session using a different
> > computer than I normally do. It worked fine. But later that day when I
> > returned to my usual computer, I ran into the bug where the session would
> > start up, but then disconnect within about a second, with the error
> > messages:
> >
> > > nxagentReconnectFailedFonts: WARNING! Font server tunneling not retrieved.
> > > nxagentReconnectSession: WARNING! Unable to retrieve all the fonts
> > > currently in use. Missing fonts have been replaced.
> >
> > A google search shows that this bug was reported 7 years ago, but no
> > solution appears to be forthcoming, apart from trying to adding fonts. But
> > with over 1000 fonts on the server, I have no idea how to find which ones
> > need adding.
> >
> > Are there any ideas out there for how to address this problem? It is
> > certainly frustrating to be unable to connect to a running x2go session,
> > and having to terminate it on the server.
> >
> > Regards,
> > Michael
> > _______________________________________________
> > x2go-user mailing list
> > x2go-user@lists.x2go.org
> > https://lists.x2go.org/listinfo/x2go-user
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user
