<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
I just see option to use custom xserver. <br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">
Do I choose that and then mobaxterm?<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Ulrich Sibiller <uli42@gmx.de><br>
<b>Sent:</b> Friday, February 26, 2021 12:12 PM<br>
<b>To:</b> Joe W <jsw140@hotmail.com><br>
<b>Cc:</b> x2go-user@lists.x2go.org <x2go-user@lists.x2go.org><br>
<b>Subject:</b> Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Oh, damn. The only thing I can imagine is a problem with the Windows X<br>
server. In the menu of the x2goclient you can configure to use an<br>
existing X server. We can try that and switch to the mobaxterm X<br>
server. Please download mobaxterm, start a ssh connection to your<br>
server (ensure that X11 is enabled) and THEN start x2goclient on<br>
windows as before, disable the X server in the menu and start your<br>
session. Is that working?<br>
<br>
Uli<br>
<br>
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com> wrote:<br>
><br>
> I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.<br>
><br>
> It seems therefore that there is some difference between the Linux and Windows client related to the problem.<br>
> ________________________________<br>
> From: x2go-user <x2go-user-bounces@lists.x2go.org> on behalf of Joe W <jsw140@hotmail.com><br>
> Sent: Friday, February 26, 2021 11:37 AM<br>
> To: Ulrich Sibiller <uli42@gmx.de><br>
> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org><br>
> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos<br>
><br>
> I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.<br>
><br>
> I realize on my linux systems I am running 4.1.1.1. Using X2GO form one linux system to the other is stable anad also does not crash.<br>
><br>
> I get the crashes when using 4.1.2.2 on my windows machine.<br>
><br>
> ________________________________<br>
> From: Ulrich Sibiller <uli42@gmx.de><br>
> Sent: Friday, February 26, 2021 2:48 AM<br>
> To: Joe <jsw140@hotmail.com><br>
> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org><br>
> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos<br>
><br>
> The debugger "solution" was not successful - which is logical given<br>
> that fact that nxagent does not crash. Thinko of mine.<br>
><br>
> Here's a way to reduce complexity a bit and possibly get a bit more output:<br>
> 1. Instead of starting an x2go session run ssh -X to the server in two terminals<br>
> 2. in the first ssh connection run "nxagent -ac :55" (55 is the one I<br>
> use normally, you can use any number here). An empty window should<br>
> appear<br>
> 3. in the second ssh session run "xterm -display :55". The empty<br>
> window will now show you an frameless xterm<br>
> 4. start the desktop environment by entering "startxfce4" into the<br>
> xterm. If that doesn't work try startlxde or just run a window<br>
> manager, e.g. "openbox &"<br>
> 5. in the desktop environment run your application and try to provoke<br>
> the "crash"<br>
> 6. post the end of nxagent's output from the first terminal<br>
><br>
> This way you will take libXcomp out of the equation (well, mostly). If<br>
> the crash happens I hope for some more output. If not, we can generate<br>
> a new nxagent with some debugging output enabled<br>
><br>
> Let me know the results,<br>
><br>
> Uli<br>
><br>
><br>
><br>
><br>
> On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:<br>
> ><br>
> ><br>
> > Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:<br>
> ><br>
> > ><br>
> > > Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:<br>
> > ><br>
> > >> On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:<br>
> > >>><br>
> > >>> I am using a program called Cliosoft SOS. It has a window that displays in columns like an Excel file. When I resize one of the columns then my X2GO session window crashes. The start window where I pick which session to start stays running.<br>
> > >>><br>
> > >>> There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.<br>
> > >><br>
> > >> Is that program available for testing?<br>
> > ><br>
> > > I don't know. I will ask them and I will also try your debugger suggestion. The program requires quite a bit of setup before the columns are seen.<br>
> > ><br>
> > >><br>
> > >>> I have attached the session log and the client debug console output showing a few of these crashes.<br>
> > >><br>
> > >> The session log looks like a reconnect should be possible. Can you confirm?<br>
> > >><br>
> > ><br>
> > > I can always reconnect after one of these crashes and see my desktop with ask the programs still running. When I do then I see that my SOS columns have been resized.<br>
> > ><br>
> > >>> Is there some way to fix this or is it a bug that I should report?<br>
> > >><br>
> > >> It is a bug - nx should not crash.<br>
> > >><br>
> > >>> Is there any additional information that I should gather?<br>
> > >><br>
> > >> Well, you could try the following:<br>
> > >> 1. start the session as always.<br>
> > >> 2. start an additional ssh session to the server as the same user or<br>
> > >> root to the server<br>
> > >> 3. run pgrep x2goagent and note the resulting PID (if you have<br>
> > >> multiple session running you will find multiple PIDs and need to<br>
> > >> identify the correct one)<br>
> > >> 4. attach the debugger to the PID: gdb -p PID<br>
> > >> 5. then try to provoke the crash. If it happens the debugger should<br>
> > >> kick in and show a prompt. Run the "bt" in command in the debugger and<br>
> > >> post the output you see.<br>
> > >>><br>
> > ><br>
> > > I will try this in the next few days.<br>
> > ><br>
> > >>> Anything I should ask the software developer?<br>
> > >><br>
> > >> Well, as written above a test version that triggers the problem would help.<br>
> > >><br>
> > >> Uli<br>
> ><br>
> > I tried your debugger suggestion.<br>
> ><br>
> > The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.<br>
> ><br>
> > Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.<br>
> ><br>
> > When I quit the debugger then the x2go window crashes.<br>
> ><br>
</div>
</span></font></div>
</body>
</html>