x2go-dev January 2019

x2go-dev@lists.x2go.org

12 participants
100 discussions

Bug#1359: Tooltips, pull-down menus, and context menus too far away
by Tristan Miller 01 Feb '19

01 Feb '19

Package: x2goclient Version: 4.1.1.1 I've recently started experiencing a problem when running single applications over X2Go. Quite often small windows such as tooltips, pull-down menus, and context menus get positioned far, far away from where they are supposed to be. For example, I'm currently writing this message in Claws Mail; when I activate the "Edit" pull-down menu, the menu doesn't appear under the menu bar but rather way over on my second screen. (I use a dual-monitor setup.) The problem happens with a lot of different applications, but not always consistently. For instance, sometimes I might hover my pointer over a widget that causes a tooltip to display halfway across the screen, and a minute or two later I'll do the same thing but this time the tooltip will display right over the widget like it's supposed to. I'm not sure if this is a bug in X2Go or in my window manager, and if it is in X2Go, whether its the client or server that's at fault. I'm running the X2Go Server 4.1.0.4 on openSUSE Tumbleweed, and connecting from X2Go Client 4.1.1.1 on openSUSE Leap 15.0, using KDE Plasma 5.12.6. (I can't upgrade the client due to Bug #1358.)

3 2

x2go great piece of software
by Hakan Malmstrom 26 Jan '19

26 Jan '19

Hi, I've been using x2go for a very long time and found it to be a great tool, but now I've run into problems due to that it requires an very old version of perl 5.10.1, will there be an update that will be able to use perl 5.16.3? Thanks, Hakan Malmstrom

1 0

Folder sharing in ThinClient mode - server-side situation after umount
by Stefan Baur 23 Jan '19

23 Jan '19

Hi $LIST, over on X2Go-User one of our new users is wondering why in ThinClient mode, X2Go doesn't remove the empty directory on the server when portable media is removed from the ThinClient. In other words, we see a ~/media/disk/KINGSTON folder on the server for a Kingston usb flash disk, and we can see all of its contents. Unplugging the device leads to an empty ~/media/disk/KINGSTON folder, but the folder "KINGSTON" itself is not removed. Is this intentional, or an oversight? Or technically impossible? Or is something wrong with the user's server/client setup? Or is the user merely "holding it wrong", i.e. would they have to use a server-side umount command like "fusermount -u mountpoint" instead of simply removing the media from the ThinClient without warning? Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

2 3

Bug#1367: Drop update-mate-menu-x2go for MATE 1.20 (Debian) and possibly MATE 1.22 upstream
by Mike Gabriel 22 Jan '19

22 Jan '19

Package: x2gomatebindings Severity: minor In Debian unstable already now and hopefully in MATE 1.22 (to be released in spring 2019), MATE has become aware of being run inside an X2Go session. A first adaptation measure in X2Go's MATE bindings would be to drop the update-mate-menu-x2go script. It injects the "Suspend X2Go" menu item into MATE's system menu. Starting with the above named MATE version, this won't be required anymore. In fact, it would create a double "Suspend X2Go" menu item, because mate-panel already shows that. The integration in MATE [1] has been done (in Debian) / will be done (in upstream) by the RDA shared library [2]. There also is a patch for mate-screensaver in the pipeline that shows a "Disconnect X2Go" button in MATE screensaver's dialog [3]. Greets, Mike [1] https://github.com/mate-desktop/mate-panel/pull/824 [2] https://github.com/ArcticaProject/librda/ [3] https://github.com/mate-desktop/mate-screensaver/pull/159 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de

1 0

Bug#1366: Upgrade to Windows 10 version 1809 break X2Go, can't read user name with space
by Khoa Tran 21 Jan '19

21 Jan '19

Package: <X2GoClient-4.1.2.0-2018.06.22-setup.exe> Version: <4.1.2.0> 1-After updating from Window 10 Ver 1803 to 1809; x2go doesn't work any more. 2- It fails with the following messages: Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, abortingLoop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, aborting Looking at the "options" files now generated under Ver 1809, they look like: nx/nx,root=/cygdrive/C/Users/Barry Pangrle/.x2go,connect=localhost,cookie=064e8b5bdd350e061f76b243b8d5b5e5,port=35936,errors=/cygdrive/C/Users/Barry Pangrle/.x2go/S-bpangrle-51-1546910140_stDMATE_dp32/sessions:51 An "options" file generated under Ver 1803 looks like: nx/nx,root=/cygdrive/C/Users/BARRYP~1/X2GO~1,connect=localhost,cookie=e8a3a18f683a68163533a911fad81985,port=45490,errors=/cygdrive/C/Users/BARRYP~1/X2GO~1/S-bpangrle-51-1545005939_stDMATE_dp32/sessions:51 It looks like the old version used to use "BARRYP~1" in the path instead of "Barry Pangrle" and based on the error messages, it seems to not be able to trace through the " " in the path name. 3. Expect to read folder with space and replace with ~ instead of space. 4. X2go can't read space, can't replace with ~ and failed. Also, please list the following info: 1. The client machine's OS (e.g., “Windows 10 pro version 1809”) 2. The client machine's version of X2GoClient: 4.1.2.0 3. The server's OS: CentOS 7, worked with Windows 10 version 1803

1 0

X2Go-TCE-MATE-Minidesktop, Contents of x2gothinclient-minidesktop Debian package
by Stefan Baur 21 Jan '19

21 Jan '19

Hi $LIST, dpkg -L x2gothinclient-minidesktop | grep -i ".svg$" tells me there are two SVG files in this package: /etc/x2go/x2gothinclient-minidesktop_background.svg /usr/share/backgrounds/x2go/x2gothinclient-minidesktop_background.svg And according to md5sum, they have the same hash (0f71c9af27b94364625047c0675c69a0), so they are identical. Is this file really needed in two locations, and why isn't one of them a symlink? Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

3 5

X2Go-TCE-MATE-Minidesktop
by Stefan Baur 21 Jan '19

21 Jan '19

Dear $LIST, I seem to be stuck in a rather deep rabbit hole, and in dire need of an adult, err, developer with C++ skills. Originally, I was merely trying to track down a race condition regarding the sessions file in MATE-Minidesktop-Mode. In doing so, I noticed some other things going wrong during the X2GoClient startup in MMD. So what I'm looking at right now is the source of X2GoClient, where it says: if (param == "--thinclient") { thinMode=true; startMaximized=true; return true; } and if ( param=="--maximize" ) { startMaximized=true; return true; } So startMaximized is already triggered by "--maximize" (which is set in the MMD X2GoClient startup script "/etc/x2go/x2gothinclient-minidesktop_start"). Great. One thing less to worry about. The only occurrences of thinMode in src/onmainwindow.cpp are: if (thinMode) { QTimer *timer = new QTimer(this); connect(timer, SIGNAL(timeout()), this, SLOT(slotSyncX())); timer->start(200); } and if (thinMode) { x2goDebug<<"Thin Mode is active."; showMaximized(); activateWindow(); raise(); } The second one is easy, it's some magic to make the Window appear in fullscreen and in the foreground, and this is probably how it needs to be done so it works even when there's no window manager present (as in TCE-NFS). But what is that timer thing in the first if clause about??? The reason why I need to know this is so I can determine if the "--thinclient" parameter should be set when calling X2GoClient in MATE-MiniDesktop mode, should be unset, or is irrelevant. (Note: TCE-NFS is not affected as it uses a different start script.) Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

2 5

Bug#1364: X2Go issue (in src:x2gothinclient) has been marked as pending for release
by Mike Gabriel 18 Jan '19

18 Jan '19

tag #1364 pending fixed #1364 1.5.0.1 thanks Hello, X2Go issue #1364 (src:x2gothinclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2gothinclient.git;a=commitdiff;h=25bef95 The issue will most likely be fixed in src:x2gothinclient (1.5.0.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 25bef951bd5a3bb13c49dc45992ca594a99de656 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Fri Jan 18 13:51:39 2019 +0100 19_x2gothinclient-minidesktop.gschema.override: Explicitly use MATE-specific theming of the desktop UI. (Closes: #1364). diff --git a/debian/changelog b/debian/changelog index 1cac657..6ba6b2d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -13,6 +13,11 @@ x2gothinclient (1.5.0.1-0x2go1) UNRELEASED; urgency=medium * usbmount/x2gousbmount: - Pull (most) changes from doc:howto:tce wiki page. + [ Mike Gabriel ] + * New upstream release (1.5.0.1): + - 19_x2gothinclient-minidesktop.gschema.override: Explicitly use MATE- + specific theming of the desktop UI. (Closes: #1364). + -- X2Go Release Manager <git-admin(a)x2go.org> Sun, 02 Dec 2018 06:49:42 +0100 x2gothinclient (1.5.0.0-0x2go1) unstable; urgency=low

1 0

Bug#1349: Fwd: Bug#1349: x2goclient not connecting after upgrade
by Javier Almasoft 18 Jan '19

18 Jan '19

From: Javier Almasoft <javier.almasoft(a)gmail.com> Date: jue., 10 ene. 2019 a las 10:25 Subject: Re: [X2Go-Dev] Bug#1349: x2goclient not connecting after upgrade I did a bit of testing today, and managed to set it running. I happen to have a non-standard port declared as default for ssh connections in my .ssh/config file, in the form: Host * Port NNNNN at the end of the file, because I have the custom of setting my installed servers apart from the default 22, to minimize attacks from port scanners. And not all my remote machines are declared in the config file, so this line takes care of the forgotten ones. If I comment out that line, x2goclient works again, both connecting to the default port 22 or to a non-standard port. It didn't matter before if I was connecting to a standard setup in port 22, or a custom one. It always choked at that line. This line doesn't give problems in my ssh connections, though. Perhaps there is a problem somewhere in the parsing of the ssh config file? Where should I report that? Thanks for taking your time in answering (and motivating me in digging more on this... ;-) ). It was really a nuisance, i use x2go in a lot if machines. -- Un saludo, Javier Martínez ALMASOFT, S.L.

1 0

Bug#1360: Works for me now
by Tristan Miller 17 Jan '19

17 Jan '19

The RPM is installable for me now. Either some X2Go developer changed the Perl dependency in the X2Go packages, or openSUSE changed its Perl RPMs so that they satisfy X2Go's requirements. Either way, this bug can probably be closed.

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev January 2019