From unknown Sat Apr 18 07:54:45 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1557: [X2Go-Dev] Bug#1557: Windows client crashes when connecting to RHEL8 Reply-To: Adam Dorsey - NOAA Affiliate , 1557@bugs.x2go.org Resent-From: Adam Dorsey - NOAA Affiliate Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Wed, 25 Aug 2021 13:25:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1557 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: References: <372b7f8e-8d40-8fc7-6789-cab8db717cf4@geo.uio.no> <372b7f8e-8d40-8fc7-6789-cab8db717cf4@geo.uio.no> Received: via spool by 1557-submit@bugs.x2go.org id=B1557.162989761410228 (code B ref 1557); Wed, 25 Aug 2021 13:25:01 +0000 Received: (at 1557) by bugs.x2go.org; 25 Aug 2021 13:20:14 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FROM_GOV_DKIM_AU,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id D632C5DC3C for <1557@bugs.x2go.org>; Wed, 25 Aug 2021 15:20:03 +0200 (CEST) Received: by mail-qt1-x82c.google.com with SMTP id t32so4506326qtc.3 for <1557@bugs.x2go.org>; Wed, 25 Aug 2021 06:20:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=noaa.gov; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=t80XNBr1UE7YqBAiGbrYy2B286nETHFQSbTN4hp5/vU=; b=l2RYD2s7qDhxx1iKDl/uy0CkxjQjpfnNKWc1WbrzWb+QHpIpe8xnk75iZgwdWO0xfd h414WFxFAwJsC5iMGwJi52Nca+kGbMVA9DADx700LtWoSNolqAzG9MvKQDrKwWeaF00+ tZfwAIsl295RxE1V0LBZWbEh+z8Q6JOp/osalQd8blwDQ/p0yRVoIEk2+b2Hgtd4GNHE UmPBX4eAYrMwiS87owixRi5juPf8axfCquOnjzuRD6sCzMx35cvB13DYP10D+957K0dF pXPRdzxKPHtQ9yTzpa1DuhMCbemPjJAtC6PF4abZYRlToncKmjh54TLeZAdPEYz9C2Nq hQ8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=t80XNBr1UE7YqBAiGbrYy2B286nETHFQSbTN4hp5/vU=; b=oqk3uy0aR/iFZWNt1FElGVv+n5GtcoDATV9VATtJPCPsWnrVkfqlrsBUB49xd83vKw a7yAuw9q/MKcxfXJSDZziJXgw1W6zMDvAIWJxpofDNQjkUAnctEE41+qAbKYOrip9J0H v17kb5uXe/lgMzq4GVwUIpSPMEVVvtnoYcF4CVno03BKQ9QhD15tU7NdYXTt7iaapLSZ /qnVOi6yT6rB53fLhcCLTdNMyCBAiUGlpfIXJGneonCNoRSgeKXgdTmtt8TPJGRBXHp/ FQRMAZawQ3K71p41ABf7u4+8XhO0gBBl/znsfD17TB9yahGFXpszEvldlZa6S2/W6psK A0dw== X-Gm-Message-State: AOAM533JU1fBI31LEQR58hOOUo+L+G/pL0msYQLXDY5LZrbVn6pTduq9 0YwtijcvWY+41qP+Ckvg/3VCMtMp6j74qDT+29j7/6DPtI1K4Q== X-Google-Smtp-Source: ABdhPJzLaS8i+lFVkq8C5HTYvj3Rmf+BS04oXIY5bDgzh68NQj0+o1XU0QZCt2U+4kxK3hLfcDPOxx+LpjPpAWTC9Mw= X-Received: by 2002:ac8:424c:: with SMTP id r12mr30632881qtm.183.1629897601765; Wed, 25 Aug 2021 06:20:01 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <372b7f8e-8d40-8fc7-6789-cab8db717cf4@geo.uio.no> From: Adam Dorsey - NOAA Affiliate Date: Wed, 25 Aug 2021 09:19:50 -0400 Message-ID: To: 1557@bugs.x2go.org Content-Type: multipart/alternative; boundary="00000000000093157505ca621b1d" --00000000000093157505ca621b1d Content-Type: text/plain; charset="UTF-8" Hans, I wonder if this is the same issue that is described in bug report #1520 ( https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1520). Can you try the workaround from that bug report? Thanks, Adam On Wed, Aug 25, 2021 at 6:03 AM Hans Peter Verne wrote: > Package: x2goclient > Version: 4.1.2.2 > > Hello, devs! > > I'm afraid this is not a very precise bug report. Any assistance in > how to investigate this is appreciated. > > We're running x2goclient 4.1.2.2 on Windows-10 machines, this has served > us well up to now. With our new RedHat Enterprise Server 8.4 in > production, > we see the client crashing very often. > > When the client crashes, it does so shortly after trying to log in to a > new or existing session. The clients "show details" window pane is > activated, > but the client dies before anything can be seen there. > > On the server, just these entries in the system logs appears: > > Aug 05 14:42:56 mimi.uio.no sshd[2421324]: Connection from > 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101 > port 22 > Aug 05 14:42:59 mimi.uio.no sshd[2421324]: Connection reset by > 2001:700:100:4028:9462:e3c7:21c5:ec1c port 49763 [preauth] > > If I disable IPv6: > > Aug 05 14:45:30 mimi.uio.no sshd[2421601]: Connection from 193.157.161.44 > port 57619 on 129.240.118.101 port 22 > Aug 05 14:45:33 mimi.uio.no sshd[2421601]: Connection reset by > 193.157.161.44 port 57619 [preauth] > > Note the absence of the "Fail password for ..." log entry. It looks like > it never gets to even try authenticating. > > There is no problem logging in with putty from the same client machine, > both with IPv6 and IPv4. Neither have I had this problem (at least > not so frequent) with the Linux client. > > The server is running sshd and x2goserver from the RHEL8/EPEL repos, > packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively. > > I eventually tried to run sshd -ddd on the server and catch the output. > The typescripts are attached (slightly edited): one where the client > crashed; > and one where it didn't (but couldn't authenticate, bad password). I'm no > expert on ssh, but it seems like the difference appears after the key > exchange > ("KEX done"), when the instance that crashed never reaches the bit with > userauth-request. > > I also tried "setenforce 0" on the server, i.e. disable SELinux, but the > client still crashed. > > As it is, I can't clearly provide a procedure to reproduce the problem, > as it doesn't always happen. > > If more information is required, or there are suggested steps to take, > please let me know. > > > Thanks in advance, and best regards, > -- > Hans Peter Verne -- IT-drift Geofag. > > In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a > court > in West Berlin overturned the 1933 verdict, and posthumously changed Van > der > Lubbe's sentence to eight years in prison. -- "Reichstag fire" on > Wikipedia. > _______________________________________________ > x2go-dev mailing list > x2go-dev@lists.x2go.org > https://lists.x2go.org/listinfo/x2go-dev > -- Adam Dorsey NOAA RDHPCS Systems Administrator Site Lead CSRA / RedLine Performance Solutions, LLC NOAA NESCC 1000 Galliher Drive, Suite 333, Fairmont, WV 26554 office: (304) 367-2882 cell: (304) 685-9345 adam.dorsey@noaa.gov --00000000000093157505ca621b1d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hans,
I wonder if this is the same issue th= at is described in bug report #1520 (https://bugs.x2go.org/cgi-bin/bugreport.cgi?bu= g=3D1520).=C2=A0 Can you try the workaround from that bug report?
=

Thanks,
Adam

On Wed, Aug 25, 2021 at= 6:03 AM Hans Peter Verne <h.p.v= erne@geo.uio.no> wrote:
Package: x2goclient
Version: 4.1.2.2

Hello, devs!

I'm afraid this is not a very precise bug report.=C2=A0 Any assistance = in
how to investigate this is appreciated.

We're running x2goclient 4.1.2.2 on Windows-10 machines, this has serve= d
us well up to now.=C2=A0 With our new RedHat Enterprise Server 8.4 in produ= ction,
we see the client crashing very often.

When the client crashes, it does so shortly after trying to log in to a
new or existing session.=C2=A0 The clients "show details" window = pane is activated,
but the client dies before anything can be seen there.

On the server, just these entries in the system logs appears:

Aug 05 14:42:56 mimi.uio.no sshd[2421324]: Connection from 2001:700:100:4028:9= 462:e3c7:21c5:ec1c port 49763 on 2001:700:100:118::101 port 22
Aug 05 14:42:59 mimi.uio.no sshd[2421324]: Connection reset by 2001:700:100:40= 28:9462:e3c7:21c5:ec1c port 49763 [preauth]

If I disable IPv6:

Aug 05 14:45:30 mimi.uio.no sshd[2421601]: Connection from 193.157.161.44 port= 57619 on 129.240.118.101 port 22
Aug 05 14:45:33 mimi.uio.no sshd[2421601]: Connection reset by 193.157.161.44 = port 57619 [preauth]

Note the absence of the "Fail password for ..." log entry.=C2=A0 = It looks like
it never gets to even try authenticating.

There is no problem logging in with putty from the same client machine,
both with IPv6 and IPv4.=C2=A0 Neither have I had this problem (at least not so frequent) with the Linux client.

The server is running sshd and x2goserver from the RHEL8/EPEL repos,
packages openssh-server-8.0p1-6 and x2goserver-4.1.0.3-9, respectively.

I eventually tried to run sshd -ddd on the server and catch the output.=C2= =A0
The typescripts are attached (slightly edited): one where the client crashe= d;
and one where it didn't (but couldn't authenticate, bad password).= =C2=A0 I'm no
expert on ssh, but it seems like the difference appears after the key excha= nge
("KEX done"), when the instance that crashed never reaches the bi= t with
userauth-request.

I also tried "setenforce 0" on the server, i.e. disable SELinux, = but the
client still crashed.

As it is, I can't clearly provide a procedure to reproduce the problem,=
as it doesn't always happen.

If more information is required, or there are suggested steps to take,
please let me know.


Thanks in advance, and best regards,
--
Hans Peter Verne=C2=A0 --=C2=A0 IT-drift Geofag.

In 1934, Van der Lubbe was beheaded in a German prison yard. In 1967, a cou= rt
in West Berlin overturned the 1933 verdict, and posthumously changed Van de= r
Lubbe's sentence to eight years in prison.=C2=A0 -- "Reichstag fir= e" on Wikipedia.
_______________________________________________
x2go-dev mailing list
x2go-dev@lists= .x2go.org
https://lists.x2go.org/listinfo/x2go-dev


--
Adam Dorsey
NOAA RDHPCS Systems Administrator Site Lead
CSRA / RedL= ine Performance Solutions, LLC

NOAA NESCC
1000 Galliher Drive, Su= ite 333, Fairmont, WV 26554
office: (304) 367-2882
cell: (304) 685-93= 45
adam.dorsey= @noaa.gov
--00000000000093157505ca621b1d--