I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
When installing x2goclient for windows to can tick a field to install the debugging version. Use that one and try to run the connection. You'll be pointed to the location of the logfile. Post that logfile here.
Uli
On Wed, May 6, 2020 at 7:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
Hello,
we have the same issues using it with CentOS 6 and my colleague has determined that this is due to ssh issues. On the other hand CentOS 7 works just fine for us. Just FYI Thank you Leo
On 5/6/2020 1:44 PM, Ulrich Sibiller wrote:
When installing x2goclient for windows to can tick a field to install the debugging version. Use that one and try to run the connection. You'll be pointed to the location of the logfile. Post that logfile here.
Uli
On Wed, May 6, 2020 at 7:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
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
Hi,
with the 4.1.2.2 client you have an additional --libssh-debug option. Generally you should always use the newest version.
Uli
On Wed, May 6, 2020 at 7:48 PM Danilovich, Leonid <ld@buffalo.edu> wrote:
Hello,
we have the same issues using it with CentOS 6 and my colleague has determined that this is due to ssh issues. On the other hand CentOS 7 works just fine for us. Just FYI Thank you Leo
On 5/6/2020 1:44 PM, Ulrich Sibiller wrote:
When installing x2goclient for windows to can tick a field to install the debugging version. Use that one and try to run the connection. You'll be pointed to the location of the logfile. Post that logfile here.
Uli
On Wed, May 6, 2020 at 7:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
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
Thank you, just confirmed that is what my colleague did to figure out that it was ssh issue... We will not be using it with CentOS 6 for now. Thanks again for responding Leo
On 5/6/2020 2:10 PM, Ulrich Sibiller wrote:
Hi,
with the 4.1.2.2 client you have an additional --libssh-debug option. Generally you should always use the newest version.
Uli
On Wed, May 6, 2020 at 7:48 PM Danilovich, Leonid <ld@buffalo.edu> wrote:
Hello,
we have the same issues using it with CentOS 6 and my colleague has determined that this is due to ssh issues. On the other hand CentOS 7 works just fine for us. Just FYI Thank you Leo
On 5/6/2020 1:44 PM, Ulrich Sibiller wrote:
When installing x2goclient for windows to can tick a field to install the debugging version. Use that one and try to run the connection. You'll be pointed to the location of the logfile. Post that logfile here.
Uli
On Wed, May 6, 2020 at 7:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
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
I'm attaching the debug file from the redhat server connection that doesn't work and a working one to my opensuse server.
Paul
On Wed, May 6, 2020 at 1:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
Hmm, from these logs it seems the session is established. Does it help if you disable printing, sound and file-sharing?
Uli
On Thu, May 7, 2020 at 6:54 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm attaching the debug file from the redhat server connection that doesn't work and a working one to my opensuse server.
Paul
On Wed, May 6, 2020 at 1:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
None of that seems to help. I tired lxqt and xfce as well and all behave the same. I found this file, does it help at all?
On Thu, May 7, 2020, 1:24 PM Ulrich Sibiller <uli42@gmx.de> wrote:
Hmm, from these logs it seems the session is established. Does it help if you disable printing, sound and file-sharing?
Uli
On Thu, May 7, 2020 at 6:54 PM Paul Borowicz <paul@borowicz.org> wrote:
I'm attaching the debug file from the redhat server connection that
doesn't work and a working one to my opensuse server.
Paul
On Wed, May 6, 2020 at 1:22 PM Paul Borowicz <paul@borowicz.org> wrote:
I've been using the 4.1.2.0 windows client with no issues aside from
the clipboard occasionally getting messed up. I usually restart the client and it fixes the problem.
I just tried the 4.1.2.2 client, hoping it fixed this. It works fine
when I access my OpenSuse server, but when I try to access my Red Hat 7 server it drops with no error output. I tried using the debug console and it also crashes. I can't seem to find a way to output the debug info somewhere I can capture it. Can you point me at the files necessary for to submit a bug report?
I see this on the server:
Session: Resuming session at 'Wed May 6 08:56:15 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file
'/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'.
Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. Info: Aborting the procedure due to signal '1'. Session: Display failure detected at 'Wed May 6 08:57:15 2020'. Session: Suspending session at 'Wed May 6 08:57:15 2020'. Session: Session suspended at 'Wed May 6 08:57:15 2020'. Session: Resuming session at 'Wed May 6 09:01:22 2020'. Info: Proxy running in client mode with pid '105652'. Info: Using errors file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/session.log'. Info: Using stats file '/tmp/.x2go-e93313t/C-e93313t-53-1588625310_stDKDE_dp32/C-e93313t-53-1588625310_stDKDE_dp32/stats'. Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Info: Waiting for connection from 'localhost' on socket 'tcp:*:33747'. :
Paul Borowicz
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Fri, May 8, 2020 at 3:20 PM Paul Borowicz <paul@borowicz.org> wrote:
None of that seems to help. I tired lxqt and xfce as well and all behave the same. I found this file, does it help at all?
Well, that file contains all errors happening during an X session. There are a lot of qt related messages and some are missing a newer GLX version.
This is from a KDE session. Please retry with another session type and post the (new created) .xession-errors-File. KDE/QT errors happen all the time so they are not a clear indicator for problems.... However, WHEN you see a xsession-errors-File this means the session must have been up else clients could not create al those messages.... At the end of the log I see some crashing application but I don't really see what crashed...
There also some BadWindow messages. which indicates weird things going on. Have you checked the machine's memory?
Uli
After I deleted that file, it has yet to be recreated with the new client.
I'll see if I can do more testing later today.
Paul
On Fri, May 8, 2020, 12:54 PM Ulrich Sibiller <uli42@gmx.de> wrote:
On Fri, May 8, 2020 at 3:20 PM Paul Borowicz <paul@borowicz.org> wrote:
None of that seems to help. I tired lxqt and xfce as well and all behave
the same. I found this file, does it help at all?
Well, that file contains all errors happening during an X session. There are a lot of qt related messages and some are missing a newer GLX version.
This is from a KDE session. Please retry with another session type and post the (new created) .xession-errors-File. KDE/QT errors happen all the time so they are not a clear indicator for problems.... However, WHEN you see a xsession-errors-File this means the session must have been up else clients could not create al those messages.... At the end of the log I see some crashing application but I don't really see what crashed...
There also some BadWindow messages. which indicates weird things going on. Have you checked the machine's memory?
Uli
-
Danilovich, Leonid -
Paul Borowicz -
Ulrich Sibiller