Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and Windows client related to the problem.
From: x2go-user <x2go-user-bounces@lists.x2go.org> on behalf of Joe W <jsw140@hotmail.com> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
Oh, damn. The only thing I can imagine is a problem with the Windows X server. In the menu of the x2goclient you can configure to use an existing X server. We can try that and switch to the mobaxterm X server. Please download mobaxterm, start a ssh connection to your server (ensure that X11 is enabled) and THEN start x2goclient on windows as before, disable the X server in the menu and start your session. Is that working?
Uli
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com> wrote:
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and Windows client related to the problem.
From: x2go-user <x2go-user-bounces@lists.x2go.org> on behalf of Joe W <jsw140@hotmail.com> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
I just see option to use custom xserver. Do I choose that and then mobaxterm?
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 12:12 PM To: Joe W <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Oh, damn. The only thing I can imagine is a problem with the Windows X server. In the menu of the x2goclient you can configure to use an existing X server. We can try that and switch to the mobaxterm X server. Please download mobaxterm, start a ssh connection to your server (ensure that X11 is enabled) and THEN start x2goclient on windows as before, disable the X server in the menu and start your session. Is that working?
Uli
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com> wrote:
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and Windows client related to the problem.
From: x2go-user <x2go-user-bounces@lists.x2go.org> on behalf of Joe W <jsw140@hotmail.com> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
Yes, should work
Joe W <jsw140@hotmail.com> schrieb am Fr., 26. Feb. 2021, 18:29:
I just see option to use custom xserver. Do I choose that and then mobaxterm?
*From:* Ulrich Sibiller <uli42@gmx.de> *Sent:* Friday, February 26, 2021 12:12 PM *To:* Joe W <jsw140@hotmail.com> *Cc:* x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> *Subject:* Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Oh, damn. The only thing I can imagine is a problem with the Windows X server. In the menu of the x2goclient you can configure to use an existing X server. We can try that and switch to the mobaxterm X server. Please download mobaxterm, start a ssh connection to your server (ensure that X11 is enabled) and THEN start x2goclient on windows as before, disable the X server in the menu and start your session. Is that working?
Uli
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com> wrote:
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS
columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and
From: x2go-user <x2go-user-bounces@lists.x2go.org> on behalf of Joe W < jsw140@hotmail.com> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
I realize on my linux systems I am running 4.1.1.1. Using X2GO form one
Windows client related to the problem. linux system to the other is stable anad also does not crash.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com> Cc: x2go-user@lists.x2go.org <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke the "crash"
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
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
output: then my X2GO session window crashes. The start window where I pick which session to start stays running.
There is a horizontal scroll bar to move the columns sideways.
When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console
output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you
confirm?
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. > > > > > >>> Is there some way to fix this or is it a bug that I should report? > > >> > > >> It is a bug - nx should not crash. > > >> > > >>> Is there any additional information that I should gather? > > >> > > >> Well, you could try the following: > > >> 1. start the session as always. > > >> 2. start an additional ssh session to the server as the same user or > > >> root to the server > > >> 3. run pgrep x2goagent and note the resulting PID (if you have > > >> multiple session running you will find multiple PIDs and need to > > >> identify the correct one) > > >> 4. attach the debugger to the PID: gdb -p PID > > >> 5. then try to provoke the crash. If it happens the debugger should > > >> kick in and show a prompt. Run the "bt" in command in the debugger and > > >> post the output you see. > > >>> > > > > > > I will try this in the next few days. > > > > > >>> Anything I should ask the software developer? > > >> > > >> Well, as written above a test version that triggers the problem would help. > > >> > > >> Uli > > > > I tried your debugger suggestion. > > > > The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that. > > > > Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything. > > > > When I quit the debugger then the x2go window crashes. > >
I chose custom x-server and browsed to select mobaxterm.exe as the executable. start X-server on X2go client start is not checked. I did nrestrt X2GO after changing the settings.
I have a mobaxterm ssh session to my linux system going.
I can run commands like gedit test& and a gedit window pops up on my windows system so I think -X is working.
When I start my session then I eventually get a pop up window saying X2GO server did not launch correctly after 4 tries. Please check your installation.
If I check "start X-server on X2go client" then the msg about not tarting after 4 tries pops up before I even start my session.
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 1:12 PM To: Joe W <jsw140@hotmail.com> Cc: x2go users <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Yes, should work
Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> schrieb am Fr., 26. Feb. 2021, 18:29: I just see option to use custom xserver. Do I choose that and then mobaxterm?
From: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Sent: Friday, February 26, 2021 12:12 PM To: Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Oh, damn. The only thing I can imagine is a problem with the Windows X server. In the menu of the x2goclient you can configure to use an existing X server. We can try that and switch to the mobaxterm X server. Please download mobaxterm, start a ssh connection to your server (ensure that X11 is enabled) and THEN start x2goclient on windows as before, disable the X server in the menu and start your session. Is that working?
Uli
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and Windows client related to the problem.
From: x2go-user <x2go-user-bounces@lists.x2go.org<mailto:x2go-user-bounces@lists.x2go.org>> on behalf of Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
I tried starting SOS from the MobiXterm terminal window.
It starts fine.
I then tried resizing the columns and moving the slider and everything works properly. No crashes.. So MObiXterm Xserver is OK at least.
Is there another program that uses the same x-server as X2go that I could try? Xming?
From: Ulrich Sibiller <uli42@gmx.de> Sent: Friday, February 26, 2021 1:12 PM To: Joe W <jsw140@hotmail.com> Cc: x2go users <x2go-user@lists.x2go.org> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Yes, should work
Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> schrieb am Fr., 26. Feb. 2021, 18:29: I just see option to use custom xserver. Do I choose that and then mobaxterm?
From: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Sent: Friday, February 26, 2021 12:12 PM To: Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
Oh, damn. The only thing I can imagine is a problem with the Windows X server. In the menu of the x2goclient you can configure to use an existing X server. We can try that and switch to the mobaxterm X server. Please download mobaxterm, start a ssh connection to your server (ensure that X11 is enabled) and THEN start x2goclient on windows as before, disable the X server in the menu and start your session. Is that working?
Uli
On Fri, Feb 26, 2021 at 5:59 PM Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
I tried using X2GO 4.1.1.1 on my Windows machine but resizing the SOS columns still crashes the X2GO window.
It seems therefore that there is some difference between the Linux and Windows client related to the problem.
From: x2go-user <x2go-user-bounces@lists.x2go.org<mailto:x2go-user-bounces@lists.x2go.org>> on behalf of Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Sent: Friday, February 26, 2021 11:37 AM To: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
I went through your procedure using ssh from one Linux system to another and tried resizingI cannot make anything crash.
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.
I get the crashes when using 4.1.2.2 on my windows machine.
From: Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>> Sent: Friday, February 26, 2021 2:48 AM To: Joe <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> Cc: x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org> <x2go-user@lists.x2go.org<mailto:x2go-user@lists.x2go.org>> Subject: Re: [X2Go-User] X2GO Crash When Resizing columns in Cliosoft Sos
The debugger "solution" was not successful - which is logical given that fact that nxagent does not crash. Thinko of mine.
Here's a way to reduce complexity a bit and possibly get a bit more output: the "crash"
- Instead of starting an x2go session run ssh -X to the server in two terminals
- in the first ssh connection run "nxagent -ac :55" (55 is the one I use normally, you can use any number here). An empty window should appear
- in the second ssh session run "xterm -display :55". The empty window will now show you an frameless xterm
- start the desktop environment by entering "startxfce4" into the xterm. If that doesn't work try startlxde or just run a window manager, e.g. "openbox &"
- in the desktop environment run your application and try to provoke
- post the end of nxagent's output from the first terminal
This way you will take libXcomp out of the equation (well, mostly). If the crash happens I hope for some more output. If not, we can generate a new nxagent with some debugging output enabled
Let me know the results,
Uli
On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>>:
Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de<mailto:uli42@gmx.de>>:
On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com<mailto:jsw140@hotmail.com>> wrote:
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.
There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
Is that program available for testing?
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.
I have attached the session log and the client debug console output showing a few of these crashes.
The session log looks like a reconnect should be possible. Can you confirm?
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.
Is there some way to fix this or is it a bug that I should report?
It is a bug - nx should not crash.
Is there any additional information that I should gather?
Well, you could try the following: post the output you see.
- start the session as always.
- start an additional ssh session to the server as the same user or root to the server
- run pgrep x2goagent and note the resulting PID (if you have multiple session running you will find multiple PIDs and need to identify the correct one)
- attach the debugger to the PID: gdb -p PID
- then try to provoke the crash. If it happens the debugger should kick in and show a prompt. Run the "bt" in command in the debugger and
I will try this in the next few days.
Anything I should ask the software developer?
Well, as written above a test version that triggers the problem would help.
Uli
I tried your debugger suggestion.
The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
When I quit the debugger then the x2go window crashes.
-
Joe -
Joe W
-
Ulrich Sibiller