x2go-dev May 2020

x2go-dev@lists.x2go.org

19 participants
104 discussions

Bug#581: VirtualBox Clipboard Sharing does not work when accessing the host over X2Go
by Michael DePaulo 18 Jun '21

18 Jun '21

Package: nx-libs Version: 3.5.0.27 Severity: normal If you run a VirtualBox VM with its display running under X2Go, the VM's clipboard sharing fails to work in either direction. You cannot copy and paste text between the VM and an app running under X2Go server, nor can you copy and paste text between the VM and an app running on the X2Go Client system. (I believe VirtualBox VMs use SDL to interact with the X server, which in this case is nxagent. This differs from the VirtualBox GUI, which is written in QT.) Specifically, when the X sesssion starts on the guest, a VirtualBox-provided script for X calls "VBoxClient --clipboard" to start the clipboard service. The service runs as the user logged into the guest. However, this service fails to stay running, and thus the clipboard sharing does not work. If you launch the VirtualBox VM on the local X.org X server, the guest's clipboard service stays running and clipboard sharing works. You can also launch the VM in RDP headless mode from x2go (so the VM does not render its display to any nxagent). In this use case, the clipboard service stays running and clipboard sharing works. The strange part is that the configuration of the host affects the behavior of the guest. It makes sense though because it's a bug in the guest's code to integrate with the host. Also, when you do call "VBoxClient --clipboard", it returns 0. And if you call it after the X11 session has already started, the problem still occurs. In x2goclient, I tried turning on and off the following setting, but it had no effect: Options -> Settings -> X-Server settings -> do not use primary clipboard My theory is that this is a bug in nx-libs, and that the bug is probably related to nx-libs being forked from such an old X.org codebase. It is worth looking into whether other SDL apps have clipboard trouble with X2Go on Ubuntu 14.04. (It's also worth testing an older release of Ubuntu as the host OS, since it would have an older release of SDL.) Host system: OS: Ubuntu 14.04.1 64-bit with latest bugfix & security updates nxagent: 2:3.5.0.27-0~446~ubuntu14.04.1 x2goserver: 4.0.1.15-0~847~ubuntu14.04.1 x2goserver-xsession: 4.0.1.15-0~847~ubuntu14.04.1 VirtualBox 4.3.14 (from download.virtualbox.org) "Shared Clipboard" is set to "Bidirectional" for the VM $ cat /etc/x2go/x2goagent.options | grep -v '^#' | grep -v '^$' X2GO_NXAGENT_DEFAULT_OPTIONS="" X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension XFIXES" X2GO_NXAGENT_DEFAULT_OPTIONS+=" -nolisten tcp" Guest OS: Ubuntu 12.04.5 64-bit with precise HWE stack, the virtual kernel, and all the latest bugfix & security updates OS-provided XFCE virtualbox-guest-dkms: 4.1.12-dfsg-2ubuntu0.6 virtualbox-guest-utils: 4.1.12-dfsg-2ubuntu0.6 virtualbox-guest-x11: 4.1.12-dfsg-2ubuntu0.6 Configured according to: https://github.com/mikedep333/duckpan-vagrant/tree/duckduckhack-vm The aforementioned script is: /etc/X11/Xsession.d/98vboxadd-xclient (I'm sure a different script would be used for distros like CentOS which lack the /etc/X11/Xsession.d/ folder). Client system: Windows 8.1 64-bit with Update 1 and all the minor/monthly updates available X2GoClient 4.0.2.1+hotfix1+build3

2 1

Bug#1369: Keys do not release when using Emacs in X2GO Client
by Yan Zhang 03 May '21

03 May '21

Package: x2goclient Version: 4.1.2.0 I am using Emacs 24.5.1 with x2go client version 4.1.2.0 in Windows 10. My server OS is Ubuntu 16.04 and the x2goserver comes from the PPA repo. The problem happens if I hit "ctrl+space" to start mark region in Emacs and then press down "ctrl+n" to scroll down the region for a few seconds. Usually after I release "ctrl+n", Emacs will leave the currently marked region for further commands. But in the reported version of client, Emacs keeps scrolling down until it reaches the end of the file. There is no way to stop it within Emacs (e.g., "ctrl+g"). I have tried to move the cursor by keeping "ctrl+n" pressed down. This issue does not happen after I release the key. This issue happens when the session type is either "XFCE" or "published application". I have not tested other session types as I do not have an environment for that. And client version 4.1.1.1 does not seem to have this issue. Thanks and regards, Yan

4 4

Bug#1386: Popup plasmoids flicker and disappear when a remote application is in focus
by Tristan Miller 23 Mar '21

23 Mar '21

Package: x2goclient Version: 4.1.1.1 I use X2Go to run single applications remotely and have them appear on my local Plasma desktop. When such a remote application window has focus, it prevents me from opening most pop-up plasmoids on my local machine. The plasmoids flicker and then disappear. STEPS TO REPRODUCE 1. Use X2Go to launch a single application remotely. 2. Give the remote application focus (for example, by Alt-Tabbing to it or clicking on it). 3. Do some action that causes a local plasmoid window to pop up. For example, click on the Application Launcher to try to show the application list, or click on the Digital Clock to try to show the calendar, or click on a group entry in the Task Manager to try to show the list of windows, or press Alt+F2 to try to bring up KRunner. OBSERVED RESULT 4. The popup window appears for a few milliseconds and then disappears. EXPECTED RESULT 4. The popup window should appear and then persist. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.12.8 KDE Frameworks Version: 5.45.0 Qt Version: 5.9.4 OS: openSUSE Leap 15.0 x2goclient: 4.1.1.1 x2goserver: 4.1.0.4 ADDITIONAL INFORMATION The video at <https://bugs.kde.org/attachment.cgi?id=119625> shows the bug. It shows a portion of my Plasma panel that includes the Application Launcher, the Pager, and part of the Task Manager. Claws Mail is running remotely via X2Go and one of its composer windows has focus. I am clicking repeatedly on the Application Launcher. You can see the pop-up window briefly flickering and disappearing. As far as I can tell, the problem happens only when an application run via X2Go has focus. The problem is not reproducible with applications run remotely via plain SSH. Not sure if this is a KDE/Plasma problem or an X2Go problem, so I have reported this also on the KDE Bugzilla: <https://bugs.kde.org/show_bug.cgi?id=406882>

1 1

Bug#1072: X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks
by Chris Martin 09 Feb '21

09 Feb '21

Package: x2goclient Version: 4.0.5.1 I am trying to start a full screen X2Go session which 1. takes up the entire display, and 2. responds to my mouse clicks everywhere in the session, but cannot accomplish this with any combination of settings. Client OS: Debian Jessie / 8 / Stable, GNOME 3 desktop environment Client X2Go Client: 4.0.5.1 and 4.0.3.1 Server OS: Xubuntu 16.04 LTS Server x2goserver version: 4.0.1.19 Server x2goserver-xsession version: 4.0.1.19 When I choose "fullscreen", I get different behavior intermittently: 1. The client spawns across the entire screen but the *top panel inside the X2Go session* does not respond to any mouse clicks. I suspect the panel in my GNOME session running the X2Go client (which occupies the same pixels behind the panel inside the X2Go session) is stealing mouse focus. My mouse pointer turns black instead of white when I hover over the top 24 pixels or so, inside the X2Go session. 2. The client spawns what I would call a "maximized window". The top of the screen is still consumed by the title bar of the X2Go window, and the panel of the enclosing GNOME session in which the X2Go client is running. I have observed both cases 1 (most common) and 2 with X2Go Client 4.0.5.1, and only case 1 with X2Go client 4.0.3.1. When I choose "Display 1" in the Input/Output settings, the X2Go session displays only in the upper-left quadrant of my display; the rest of the screen is black. Thank you, Chris Martin

4 5

Bug#1464: x2goclient 4.1.2.2 version does not work with Pageant SSH authentication agent
by saion.chatterjee＠siemens.com 04 Aug '20

04 Aug '20

Package: x2goclient Version: 4.1.2.2 With the latest x2goclient version available as of today ( x2goclient 4.1.2.2-2020.02.13 ), user faces authentication error while trying to login using Pageant SSH agent. The error message received is: "Access denied for 'publickey'. Authentication that can continue: publickey Access denied for 'none'. Authentication that can continue: publickey" The error does not happen with the previous version of x2goclient. Tried and tested with x2goclient 4.1.2.0 and it works fine. Pageant version used is: Pageant Release 0.73 The client's OS: 64-bit x86 Windows 10 The server's OS: Ubuntu 19.04 best regards, Saion

2 3

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#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

Fwd: [ArcticaProject/nx-libs] Document compression (#802)
by Ulrich Sibiller 02 Jun '20

02 Jun '20

---------- Forwarded message --------- From: Ulrich Sibiller <uli42(a)gmx.de> Date: Sun, May 31, 2020 at 10:58 PM Subject: Re: [ArcticaProject/nx-libs] Document compression (#802) To: ArcticaProject/nx-libs <reply+ABQHBZHBGIOEJSNWVCG4BAV4372CLEVBNHHBUM3YJI(a)reply.github.com> Cc: ArcticaProject/nx-libs <nx-libs(a)noreply.github.com>, Author <author(a)noreply.github.com> "nopack" in x2go becomes "none" in NX. And it means exactly what it says: do not compress images. This setting saves CPU cycles but required more bandwidth. Images are normally cached this so this is relevant only for the tiem an image must be transferred to the other side. All the things I documented are valid for plain NX sessions (without using x2go but other software). In NX - if you don't specify a compression method explicitly but only a link type - the compression method is derived from the link type. For ADSL you correctly expect adaptive-7 as I listed in the document. Using x2go things are a bit different. The NX code is the same and so are the built-in defaults. For ADSL this is still "adaptive-7". But x2go does always provide a compression type in addition to the link type. So that default is never used but overridden by the compression settings the user specifies in x2go's session configuration. So regarding compression you always get what you select there, in your case it is "nopack" (which becomes "none" at some point because of the internal naming of the parameter). In other words: in x2go you always have to select a clever combination of link speed and compression while using plain NX you can stick with the link speed and use the defaults. If you only touch the link speed setting you will always get 16m-jpeg. I am using an own software for connection (which I cannot make public for legal reasons) and always stick with the defaults. I was not aware of this x2go behaviour. But this might explain why I don't see the performance problems I sometimes hear about from other people. So I consider this a bug. Developers: what's your opinion about this? Uli On Sun, May 31, 2020 at 10:27 PM Anton Driesse <notifications(a)github.com> wrote: > > Sorry, you lost me. > > I think you're saying nopack is the same as "no pack", but did you say what nopack really is? > > Anyway, using nopack I do observe that the choice of link makes a difference. > > ADSL gave me reasonable update speed and quality; > with MODEM I expected quick update and poor quality, but I got slow update and poor quality; > with LAN I expected and got slow update but high quality. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub, or unsubscribe.

4 8

Code formatting
by Dave Chamberlin-Kidd 31 May '20

31 May '20

Hi, I noticed someone else talking about auto code formatting. Is there a house style? If so is there a recommend formatting tool (I'm currently using Vs code and vi to edit)? Cheers Dave

7 18

← Newer
1
...
5
6
7
8
9
10
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev May 2020