X2Go Bug report logs - #1502
macOS X2GoClient keyboard map updates crash specific server applications, spike server CPU usage

Full log

Message #15 received at 1502@bugs.x2go.org (full text, mbox, reply):

Received: (at 1502) by bugs.x2go.org; 3 Nov 2020 22:02:46 +0000
From tyearke@buffalo.edu  Tue Nov  3 23:02:37 2020
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,HTML_MESSAGE,
	MIME_QP_LONG_LINE,SPF_HELO_NONE,URIBL_BLOCKED autolearn=unavailable
	autolearn_force=no version=3.4.2
Received: from mtareserve25.acsu.buffalo.edu (mtareserve25.acsu.buffalo.edu [128.205.6.42])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id A55485DAF2;
	Tue,  3 Nov 2020 23:02:33 +0100 (CET)
Received: from appmailb.acsu.buffalo.edu (appmailb.acsu.buffalo.edu [128.205.4.58])
	by mtareserve25.acsu.buffalo.edu (Postfix) with ESMTP id 4CQkKh2Y47zC69pD;
	Tue,  3 Nov 2020 17:02:32 -0500 (EST)
Received: from appmailb.acsu.buffalo.edu (localhost [127.0.0.1])
	by localhost (Postfix) with SMTP id 547531609FF7D;
	Tue,  3 Nov 2020 17:02:32 -0500 (EST)
Received: from appmailb.acsu.buffalo.edu (localhost [127.0.0.1])
	by appmailb.acsu.buffalo.edu (Postfix) with ESMTP id 0D4991609FF76;
	Tue,  3 Nov 2020 17:02:32 -0500 (EST)
Received: from MBX-NR7.itorg.ad.buffalo.edu (mbx-nr7.acsu.buffalo.edu [128.205.7.210])
	by appmailb.acsu.buffalo.edu (Prefixe) with ESMTP id 0A5531609FF75;
	Tue,  3 Nov 2020 17:02:32 -0500 (EST)
Received: from mbx-nr8.itorg.ad.buffalo.edu (128.205.7.211) by
 MBX-NR7.itorg.ad.buffalo.edu (128.205.7.210) with Microsoft SMTP Server (TLS)
 id 15.0.1497.2; Tue, 3 Nov 2020 17:02:30 -0500
Received: from mbx-nr8.itorg.ad.buffalo.edu ([192.168.1.108]) by
 MBX-NR8.itorg.ad.buffalo.edu ([192.168.1.108]) with mapi id 15.00.1497.006;
 Tue, 3 Nov 2020 17:02:30 -0500
From: "Yearke, Thomas" <tyearke@buffalo.edu>
To: "uli42@gmx.de" <uli42@gmx.de>, "1502@bugs.x2go.org" <1502@bugs.x2go.org>
CC: "submit@bugs.x2go.org" <submit@bugs.x2go.org>
Subject: Re: [X2Go-Dev] Bug#1502: macOS X2GoClient keyboard map updates crash
 specific server applications, spike server CPU usage
Thread-Topic: [X2Go-Dev] Bug#1502: macOS X2GoClient keyboard map updates crash
 specific server applications, spike server CPU usage
Thread-Index: AQHWsXo7w0l/NEzdA02/U0PSVaStS6m2RmqAgACwrIA=
Date: Tue, 3 Nov 2020 22:02:30 +0000
Message-ID: <0BA097A7-B63A-4125-8853-8E1D4EFFDFD4@buffalo.edu>
References: <F5B32DA7-8962-4080-9BE2-31E40980B913@buffalo.edu>
 <CANVnVYJvHS+7=wLaT-dOZ5Q5g-ExPnrXp+O+vBtheJzdg=TkDw@mail.gmail.com>
In-Reply-To: <CANVnVYJvHS+7=wLaT-dOZ5Q5g-ExPnrXp+O+vBtheJzdg=TkDw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.21.217]
Content-Type: multipart/signed; protocol="application/pkcs7-signature";
	micalg=sha256; boundary="B_3687267749_1040077208"
MIME-Version: 1.0
X-PM-EL-Spam-Prob: X: 11%

[Message part 1 (text/plain, inline)]

In both the current and patched versions of X2GoClient, changing the X11 keyboard map on the client side seems to have no immediate impact on an active X2Go session. If a session is suspended, though, the session’s keyboard map does get updated when it’s resumed by either version.

 

I believe this is the case because the client only constructs a keyboard map during the first keyboard update in ONMainWindow::slotSetModMap. This map is held in memory and reused by subsequent keyboard updates until it is deleted during a session suspension or termination.

 

(It’s worth noting that macOS uses an entirely-separate mechanism for managing the keyboard layout for non-X11 programs. Changing the keyboard layout in System Preferences affects the Qt components of X2GoClient, but anything X11-based is not affected by those changes. Only the X11 keyboard map as reported by xmodmap is used by local X11 apps and by X2GoClient’s keyboard map builder.)

 

Tom

 

From: Ulrich Sibiller <ulrich.sibiller@gmail.com>
Reply-To: "uli42@gmx.de" <uli42@gmx.de>
Date: Tuesday, November 3, 2020 at 1:30 AM
To: Tom Yearke <tyearke@buffalo.edu>, "1502@bugs.x2go.org" <1502@bugs.x2go.org>
Cc: "submit@bugs.x2go.org" <submit@bugs.x2go.org>
Subject: Re: [X2Go-Dev] Bug#1502: macOS X2GoClient keyboard map updates crash specific server applications, spike server CPU usage

 

Thanks for the patch. Keyboard on MacOS is special. As I do not have/know MacOS I don't know why it was implemented that way.  

 

What happens if you change the MacOS keyboard while a session is running?

 

Uli

 

Yearke, Thomas <tyearke@buffalo.edu> schrieb am Di., 3. Nov. 2020, 01:45:

Package: x2goclient
Version: 4.1.2.2
Tag: patch

When the macOS version of X2GoClient is connected to a server, it updates the session's keyboard map every 10 seconds. Depending on how other programs running on the server respond to keyboard map changes, the repeated updates can cause brief CPU usage spikes or (in the case of one of our applications) they can cause freezes and crashes.

The attached patch modifies the macOS client to only run the keyboard map update once on session startup. Testing done on my devices showed that this change resolved the issue without introducing noticeable side effects. However, I was not able to find the reason why the keyboard map is being updated regularly, so this may (re)introduce a problem I'm not aware of.

Client OS: macOS 10.14.6
Client Software: X2GoClient 4.1.2.2
Server OS: CentOS 7.8
Server Desktop Environment: XFCE 4
Server x2goserver Version: 4.1.0.3
Server x2goserver-xsession Version: 4.1.0.3
Server nxagent Version: 3.5.99.24

Thank you for your consideration!

Tom Yearke
Software Engineer
Science and Engineering Node Services
University at Buffalo


_______________________________________________
x2go-dev mailing list
x2go-dev@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-dev

[Message part 2 (text/html, inline)]

[smime.p7s (application/pkcs7-signature, attachment)]

Send a report that this bug log contains spam.