X2Go Bug report logs - #1385
Windows x2go menu bar does not appear in client

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: "David DeMoney" <david@demoney.org>

Date: Mon, 15 Apr 2019 21:40:02 UTC

Severity: normal

Full log

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

Received: (at submit) by bugs.x2go.org; 15 Apr 2019 21:36:08 +0000
From david@demoney.org  Mon Apr 15 23:36:07 2019
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,HTML_MESSAGE,
	SPF_HELO_PASS autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 258645DAED
	for <submit@bugs.x2go.org>; Mon, 15 Apr 2019 23:36:07 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lhyOSGPyI6dH for <submit@bugs.x2go.org>;
	Mon, 15 Apr 2019 23:36:00 +0200 (CEST)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.197])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id F25D75DA8B
	for <submit@bugs.x2go.org>; Mon, 15 Apr 2019 23:35:59 +0200 (CEST)
Received: from DeMoneyX1 ([72.132.190.180]) by mrelay.perfora.net (mreueus001
 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LjKvJ-1gijej0fap-00dMNE for
 <submit@bugs.x2go.org>; Mon, 15 Apr 2019 23:35:58 +0200
From: "David DeMoney" <david@demoney.org>
To: <submit@bugs.x2go.org>
References: <000001d4f3cc$8251e4b0$86f5ae10$@demoney.org> 
In-Reply-To: 
Subject: Windows x2go menu bar does not appear in client
Date: Mon, 15 Apr 2019 14:35:56 -0700
Message-ID: <001801d4f3d3$36ab1de0$a40159a0$@demoney.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0019_01D4F398.8A4D5750"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFrOCxWkOHCjjpxUg+gn81Et495Q6cRL4NAgAAGJOA=
Content-Language: en-us
X-Provags-ID: V03:K1:NmWcchnxSfhFG/8dTWO+fuwD/5eDqXw9cOlI2uuwlyJfK9het+F
 0yTvib+RB0MR36i42kK85CslxXjBeOi+IWGiK+/vMsKJi73lEr0Wf9t5W1JHYzLcU4o2BwE
 Q6fMgdP68XrEeL3kOSDy9TwWInxL2DZD9N6oVkXVjuN3yZ3dxPoDBGrWLbw7skB6DOWNB5e
 EPGSLq9SfNCe/Q0K15hBA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Wme2lMZJP4o=:2SXSu/Q4HIvDdf5SgPVK8L
 5tk2lCuHA7vaPMXV4FoSasGdE2ayn9dgs8CNfa7+TDKsCnWe8LUgm77KWWFkGw3VCwgw3zhlR
 lNCbulLWCNTFdexwwzfOMXNWV7IHo5t+6eVyMA1Gt3M5GIBDoVgFK8RTu3lOMwndv5qe86pbu
 m/BImqMYH8sjE4rMGT8IhDqbdsvLxTg5C6pgUupDisyzw9lKmEKijielgwVvh4cT/5vTAkVYt
 SBlGf/fmShe2oAbCFcE4jm/OOYP0YTlZgKu+cg+OjrKreDFJMLoNHbYYlO0i1qyr8Ogwjty+5
 idownj1/ak6Ovy1b+JApOC/OpIN/GpzpX748+UANzC8dFt1e+lQGRaJ26MUpr22q34UozmUE7
 Zp8wvA6/yvPbLCbQrJwm2zrUI9i3cwEaWVuti16ZXG2aIhhbaw+740zAv4VptHbITBOjw2uKh
 LHrBVkGfqcQATGEV3YQ91J+24azNSesP4hoWoQjIsaBT26dn0J/bB9ZeKVS9+r872XQbf135h
 EwKQFbD2mTMuLWWQi7pELkd10LO8bYKhjfKqgR7WlJAyjEXKy8c+zi3ykOgEb9Uzd+6A8SX78
 9ONmDn4avX5nSxsLWv9ZzSsBc2xTq4FdoWiek+/NvZ2w95XrJBAhgc17wxNwR5I3cnqCzVf4q
 v+LdOEUJcn1B105Bm/wwW4r+6lmS0skvsvQAEZvllOo/0iBg547PzulU3YuJeNCgPFQT3m52d
 VgJedfdVdVpTYNOcSpAR4ZNy0HeMiAUaM0ORSjI04BLobeGo/lObSCcZ514=

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

Version: 4.1.2.0

 

I am using x2go client v4.1.2.0 (but saw same issue with 4.1.0.0).

 

I start a connection to a Linux host (Knoppix v7.0.5) using LXDE session
type and fullscreen display. Client host is Windows 10.

 

After the fullscreen client is displayed, I cannot access the x2go menu bar
(at the top, center of the window, owned by x2go). I move my mouse to the
top, but it does not appear. The alt keys for switching out of fullscreen
mode do not work either. Only method I have found that works is Windows
alt-tab key.

 

This change in behavior just started recently, and AFAIK, I had not made any
changes to client or host x2go. I did upgrade to latest x2go client (to see
if issue was fixed), but that did not change the behavior.

 

I have tried this from 2 different client hosts (other was Windows 7), and 2
different target hosts. All behaved the same.

 

I would have sent the configuration file, but it is not obvious what file
that is. Would be useful if you added more details on how to find/identify
this file.

 

Is this a known issue? Is there a workaround?


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

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 15:30:43 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.