x2go-dev September 2020

x2go-dev@lists.x2go.org

10 participants
86 discussions

Bug#1475: Fwd: Error on iconize
by Max V 11 Sep '20

11 Sep '20

Package: x2goclient Version: 4.0.5.1 Hello, my x2go server run on LXDE server, all ok. My client is Cinnamon, When I start all is ok, when I minimize the window, clicking in the top right, the windows is minimized, but it's dimension become about 2x25 pixels, so even I restore, I can't see anything and I can't maximize it anymore. I made a screenshot, it's that sort of capital I in the center of the screen. My Cinnamon version is 3.4.6 My x2goclient is 4.0.5.1 Best regards Max

3 4

Bug#1493: Fullscreen client gets minimized when switching virtual desktops on Windows 10
by Tyler Anderson 06 Sep '20

06 Sep '20

Package: x2go-client Version: 4.1.2.2 I am using the x2go client in full-screen mode on one of my virtual desktops on windows 10. I can swipe through my virtual desktops with a four-fingered swipe on the trackpad or by pressing Win+ctrl+left/right. When I have the client in fullscreen, if I swipe to a different desktop and then back to the desktop containing the client, it has become minimized. It does not maintain its full-screen mode when switching virtual desktops. The same also occurs if I enter task view with a four-finger swipe up, the window is minimized when I return.

1 0

Windows 7 x2go Client Access Violation Connecting to CentOS 6 server using GNOME - Crashes in Latest Version Only
by OwN-3m-All 03 Sep '20

03 Sep '20

Hi All, I recently upgraded my x2go client from version 4.1.2.0 (Qt - 4.8.6) to 4.1.2.2 (Qt - 4.8.6). When I try to connect to one of my servers running CentOS 6 with the latest updates, my x2go client on Windows 7 x64 SP1 immediately crashes. In fact, the connection never even makes it to the remote server for processing according to the logs on the remote server, as the client forces the connection closed (due to it crashing). I even installed the debug version of the x2go client, and it doesn't output anything of value before it crashes either. Plus, it doesn't appear to log anything to a file either? After installing the old version of x2go in a different directory than the newest version, I am able to connect just fine to the server using the old x2go client version. Something broke from the update. What I can tell you is that I get this error message when debugging the crash through Visual Studio: https://serv1.dragndropz.com/user_images/2020_09_03/2256_oERSXY_2020-09-031… Also, I was able to replicate this issue in a virtualized instance of Windows 7 x64 SP1 via VirtualBox. The CentOS 6 server I'm trying to connect to isn't running anything special. However, it is one of my oldest servers, and as a result, it is the only server that is still running GNOME (usually I use MATE or XFCE). I'm using a non-standard ssh port, a private key that uses a passphrase, and "Session type" is set to GNOME. I've disabled sound support and client side printing support to make sure the crash didn't have anything to do with these features. Any chance someone could look into this further? For now, I will just run both versions of x2go side-by-side. Thanks OwN

1 0

Bug#1476: x2goclient interface code needs refactoring to make it more accessible and make improvements easier to implement and test
by Dave Chamberlin-Kidd 03 Sep '20

03 Sep '20

Package: x2goclient Version: 4.1.2.3 Severity: wishlist Tag: patch There are a number of minor issues, oddities and limitations with the current x2goclient gui which would be good to fix, resolve and improve on. Like all projects however the core team have more important issues to resolve. The code in its current state is difficult to understand and amend and as it has no tests it is risky for developers to make functional changes unless they spend a lot of time getting to know the code and doing extensive manual testing. Attached are 10 small refactorings which start extracting out some of the code into smaller functions. As the code is separated out it becomes easier to understand and change. There are no functional changes in these patches, nor do they attempt or claim to fix any known issues. On their own the benefit of these patches is limited however the hope is that over time I will be able to submit more refactorings as I learn more and then start fixing issues and improving the UI. Extracting out functions is just one of many techniques that can be used to make code cleaner but in my experience it's a good one to start with. It should also be noted that sometimes code is extracted "as is" even when it is clear further refactoring can be done to improve things, this is by design in order to keep risk and size of patches to a minimum. Cheers Dave

2 3

Bug#1492: Package: Multiple monitors / Xinerama crashes
by John Watson 02 Sep '20

02 Sep '20

Package: x2goserver-xsession Version: 4.1.0.3-5 NOTE: this is CentOS8's epel8.playground.noarch package Remove server environment: OS: CentOS 8 - 8.1.1911 (Core) x2goserver-xsession: x2goserver-xsession-4.1.0.3-5.epel8.playground.noarch nx-libs: nx-libs-3.5.99.23-1.epel8.playground.x86_64 Local server environment: OS: MacOS Catalina 10.15.6 x2go: X2Go Client v. 4.1.2.2 (Qt -4.8.7) When I invoke `xterm` or any other X11 app over x2go client on the laptop alone (not connected to any external monitors), everything works without any hiccups. With multiple monitors connected, however, an existing session will only render a blank screen locally, and the mouse pointer will disappear. When *creating* a new session, the remote server process crashes with the following in /var/log/messages (CentOS equivalent of /var/log/syslog) Aug 30 14:08:39 <server host> kernel: [62624.705481] x2goagent[2960736]: segfault at 0 ip 0000000000000000 sp 00007ffd426f92e8 error 14 in nxagent[5655328cb000+437000] This looks strikingly similar to the bug described in https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=943, but it's now 2020 and I'm on the latest yum repo available to CentOS 8... I've added "+xinerama" to X2GO_NXAGENT_DEFAULT_OPTIONS in /etc/x2go/x2goagent.options and enabled it in the x2go client as well. Should I attempt playing with building nx-libs from source myself and installing?

1 0

x2goclient resumes session with wrong X-Server options
by Maarten Boekhold 02 Sep '20

02 Sep '20

Hi all, (I tried to sent this twice to x2go-user, but after more than 24 hours it still hasn't shown up there) Windows 10, x2goclient 4.1.2.2 When resuming a "paused" x2Go session, x2goclient is using the wrong X-Server settings. I have configured my x2goclient with the following settings for X.Org Server settings: **X.Org Server settings** [X] use custom X-Server Executable: C:/Program Files (x86)/x2goclient/VcXsrv/vcxsrv.exe [ ] start X-Server on X2Go Client start Window mode: -screen 0 %wx%h -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error Fullscreen mode: -fullscreen -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error Single application: -multiwindow -notrayicon -clipboard \ -keyhook -nowinkill -nopn -silent-dup-error Whole display: -nodecoration -notrayicon -clipboard -keyhook \ -nopn -silent-dup-error -screen 0 @ My x2goclient session is configured as: **Session preferences: Input/Output** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [X] Use whole display [ ] Maximum available Display: 2 When I start a new x2Go session, it correctly runs the X-Server with the "Whole display" command: "C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" \ -nodecoration -notrayicon -clipboard -keyhook -nowinkill \ -nopn -silent-dup-error screen 0 @2 :0 But if I then "pause" this session and reconnect, x2goclient uses the "Window mode" command line options instead: "C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" \ -screen 3696x2160 -notrayicon -clipboard -keyhook \ -nowinkill -nopn -silent-dup-error :0 This is really annoying. I suspect this has something to do with the code around line 4442 in onmainwindow.cpp, but I've not been able to figure out the exact details yet. I've tried to debug this by running x2goclient.debug.exe --debug, but there's an issue here. When running the debug version, the "Use whole display" option is not available in the session settings tab: **Session Input/Output with x2goclient.debug.exe --debug** [ ] Fullscreen [ ] Custom Width (greyed out 3696) Height (greyed out 2160) [ ] Maximum available See the "Use whole display" option missing in front of the "Maximum available" radio box. It's almost as if the debug build included in this distribution is of an older x2goclient version (but it shows the correct version number in the About dialog). I hope that based on the provided information a fix can be created for this issue? Regards, Maarten

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev September 2020