x2go-dev July 2020

x2go-dev@lists.x2go.org

7 participants
90 discussions

Bug#1403: Add packages for openSUSE Leap 15.1
by Tristan Miller 30 Jul '20

30 Jul '20

Package: x2goclient Version: 4.1.2.2 Tags: rpm-packages The repository at <http://packages.x2go.org/> contains packages for openSUSE Leap 15.0, which has end of life on 2019-11-25. Please consider adding packages for the current version of the OS, openSUSE Leap 15.1, which was released on 2019-05-22 and will be supported until 2020-11-22. I've filed this bug against x2goclient but the same request applies to x2goserver and ancillary x2go packages.

1 3

Bug#1358: x2goclient for openSUSE 15.0 is missing
by Tristan Miller 30 Jul '20

30 Jul '20

Package: x2goclient Version: 4.1.2.2 The x2goclient package for openSUSE Leap 15.0 seems to have gone missing from the official repository at <http://packages.x2go.org/opensuse/15.0/main/x86_64/>. It has been gone since at least December 2018.

1 2

Bug#1491: Add packages for openSUSE Leap 15.2
by Tristan Miller 29 Jul '20

29 Jul '20

Package: x2goclient Version: 4.1.2.2 Tags: rpm-packages The repository at <http://packages.x2go.org/opensuse> contains packages for openSUSE Leap 15.1, which has end of life on 2020-11-22. Please consider adding packages for the current version of the OS, openSUSE Leap 15.2, which was released on 2020-07-02 and will be supported until 2021-12-31. I've filed this bug against x2goclient but the same request applies to x2goserver and ancillary x2go packages.

1 0

KDrive does not seem to honor compression settings in X2GoClient?
by Stefan Baur 27 Jul '20

27 Jul '20

Hi List, hi Alex, Same environment as for the ten previous issues/oddities ... This time, I tried out "Connect to Windows Terminal Server". In NX mode, I can set the compression to "nopack", and it does have an effect. But it looks like choosing "nopack" when KDrive is selected has no effect. With "16m-jpeg" in NX mode, but not with "nopack", I am getting nasty JPEG artifacts when moving a window around. In KDrive, these artifacts are always there, no matter what I select. I have attached two screenshots, one with the contrast enhanced so the issue is easier to spot. Is this intentional? If so, "compression" should be greyed out in KDrive mode. But, on the other hand, those artifacts are annoying, so we need to make them go away somehow. Should I file a bug? 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 1

Ten X2Go-KDrive bugs/oddities
by Stefan Baur 27 Jul '20

27 Jul '20

Hi List, hHi Alex, Lately I was able to test a few more things with X2Go-KDrive, and I encountered some bugs/oddities with it. Maybe you could comment below which issues I should file as a bug, and what further info (like, screenshots, package versions, content of certain config files, ...) I should try to gather before filing it, to make debugging/fixing it easier? All tests were performed with an Ubuntu 18.04 LTS Client; and X2GoClient from the stable repository. The host ran on Debian 10.4, and was using the X2Go heuler repository, with the following X2Go-related packages: ii libx2go-log-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all Perl X2Go::Log package ii libx2go-server-db-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 Perl X2Go::Server:DB package ii libx2go-server-perl 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all Perl X2Go::Server package ii x2go-keyring 2019.08.21~git20190824.119+11.heuler.1 all GnuPG keys of all X2Go developers and the X2Go archive ii x2goserver 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go server ii x2goserver-common 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server (common files) ii x2goserver-extensions 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (extension support) ii x2goserver-fmbindings 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (file manager bindings) ii x2goserver-printing 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go server (printing support) ii x2goserver-x2goagent 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server's X2Go Agent Xserver ii x2goserver-x2gokdrive 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 amd64 X2Go Server's X2Go KDrive Xserver ii x2goserver-xsession 4.1.0.4-0x2go1.2~git20200228.1815+10.heuler.1 all X2Go Server (Xsession runner) ii xserver-x2gokdrive 0.0.0.1-0x2go1~git20200120.183+10.heuler.1 amd64 KDrive graphical server backend for X2Go Server ii libnx-x11-6:amd64 2:3.5.99.22-0~git20190928.3526+10.heuler.1 amd64 nxagent's libNX_X11 client-part library ii nx-x11-common 2:3.5.99.22-0~git20190928.3526+10.heuler.1 all nx-X11 (common files) ii nxagent 2:3.5.99.22-0~git20190928.3526+10.heuler.1 amd64 Nested Xserver (aka NX Agent) supporting the NX compression protocol First issue/oddity: No matter which Desktop Environment is being used on the remote end, the local client window seems to snap to the top left position in an 800x600 resolution (or maybe even smaller, like 640x480), then it resizes to the requested size. This can be seen during resume, where the resume happens on the 800x600 (or whatever) resolution, then the screen is resized, and you see "garbage" on the screen (cloned sections of the client window content), until it redraws the entire screen after resizing it properly. This takes about a second or so. This may also be the reason why in one particular situation (during another test, on a different setup) I saw the KDrive window getting stuck at that small size in the upper left corner - probably the "maximize" command didn't reach the window manager, or there was no window manager present, or something like that. Second issue/oddity: Only roughly every second attempt to resize the client-side KDrive window using the mouse works. The other attempts have it snap back to where it originally was, once you let go of the mouse button. Third issue: At least in most of the desktop environments tested, both keyboard autodetection AND keyboard manual selection fails, so you're stuck with a US keyboard inside the session. The notable exception is GNOME, here, keyboard settings work, even in autodetection mode! Fourth ... well, oddity: In Fullscreen sessions, the top-of-the-screen Config Bar's Minimize Button does not work unless fullscreen mode has been toggled off and on again. Fifth issue: The modes "Published Application" and "XDMCP" are selectable with KDrive, but do not do anything useful; "Single Application" is only useful together with KDrive when the application in question has a fullscreen mode (like "rdesktop -f") Sixth issue: The top-of-the-screen Config Bar has a button "Disconnect". This should be named "Suspend" (or "Disconnect and suspend"), to be more in line with current X2Go terminology, and to make it more clear to the user that this isn't terminating the session, but rather suspending it. Also, Ctrl-Alt-T should suspend the session just like in classic NX mode, but currently does nothing. Seventh issue: LXQt complains on session startup that "global keyboard shortcut Ctrl-Alt-D for Desktop could not be registered" (Popup message) Eight issue: In Fullscreen mode (but not in windowed mode!), when using LXQt, MATE, XFCE or KDE, clicking the "Disconnect" button in the top-of-the-screen Config Bar does suspend the session, but any attempts at reconnecting lead to a client-side abort. The only way to recover is to either start X2GoClient with --no-autoresume, and terminating the session from the session chooser, or to log in via ssh and issue a x2goterminate-session command with the corresponding session ID. Ninth issue: KDE complains on session startup that I should enter Admin credentials for configuring a system update proxy? Tenth issue: GNOME complains on session startup that I should enter Admin credentials to update system repositories. (This popup appears even twice.) 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 1

Bug#1225: x2goclient / pyhoca does not honor ProxyJump in .ssh/config
by Filip Krikava 27 Jul '20

27 Jul '20

Package: x2goclient; Version: 4.1.0.0 Due to the configuration of the university network, I have to first connect to a frontend, then to a node and then to a VM. To make this easy to use, I set ProxyJump in my .ssh/config. This works really well for ssh. However, it does not seem to be recognized by x2go. I have to manually tunnel the ssh port from the VM on my localhost to be able to connect there via x2go. The same is for pyhoca-cli 0.5.0.3.

5 5

x2goclient for windows with libssh 0.9.4
by Ulrich Sibiller 27 Jul '20

27 Jul '20

Hi, can anybody please rebuild x2goclient with libssh 0.9.4 for windows? And maybe with libssh 0.8.9. I still cannot use the latest version because of problems as described in bug #1460... Uli

1 0

Bug#1489: Windows x2go client ignores ProxyJump
by Carsten Bockelmann 27 Jul '20

27 Jul '20

Package: x2goclient Version: 4.1.2.2-2020.02.13 Similiar to this old bug https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1225 ProxyJump is ignored under windows 10. However, the underlying libssh 0.9.3 now supports ProxyJump and at least in ubuntu 20.04 it works out of the box. This is especially frustrating as host certificates are not supported in libssh which currently blocks any config in x2goclient that directly configures the bastion host as proxy (kex exchange method unsupported).

1 0

extend x2gopath
by Ulrich Sibiller 10 Jul '20

10 Jul '20

Hi, I would like to fix the long-standing bug that x2gostartageni sets NX_CLIENT to x2gosuspend-agent, which is simply wrong. I would like to point it to nxdialog, if available. The best way to find out the correnct nxdialog path is probably using x2gopath. But I am not really sure how all that x2gopath stuff is supposed to work. I mean, depending on the distribution, nxdialog might be on different locations. E.g. the nx-libs Makefile(s) install nxdialog to $BINDIR, which is $PREFIX/bin by default. The packager can redefine BINDIR and/or PREFIX. x2gopath does not know about BINDIR, it only knows PREFIX. So how can I determine the BINDIR used during packaging of nxdialog? Can anyone shine a light on this? Uli PS: nx-libs.spec does not build an nxdialog rpm yet, so that's needs to be fixed, too.

2 1

x2goClient code refactoring
by Dave Chamberlin-Kidd 07 Jul '20

07 Jul '20

Hi, Whilst digging through the code in the x2goClient I've come across void ONMainWindow::processSessionConfig() in onmainwindow.cpp but I can't see anywhere where this code is called. Commenting it out along with a stack of associated code doesn't seem to have any affect. So my question is, is there something obvious I'm missing? If not I'll root through the code and find any other associated bits, rip them out and submit a patch. Cheers Dave

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev July 2020