Package: <x2goserver>
Version: <a.b.c.d>
Severity: wishlist
Hi guys, it would be great to add "--all-servers" to x2golistsessions_root man page would be:
SYNOPSIS
x2golistsessions_root [<server_hostname>|--all-servers]
thanks
J.
Package: Pyhoca
Version: 0.6.0.1
I tested all combinations of the following recent releases of the
following software from the ppa:x2go/stable and ubuntu repositories:
+ x2goserver
+ 4.1.0.0-3 (ubuntu)
+ 4.1.0.3-0~1708~ubuntu18.04.1 (ppa:x2go/stable)
+ x2goclient
+ 4.1.1.1-2 (ubuntu)
+ 4.1.2.1-0~1788~ubuntu18.04.1 (ppa:x2go/stable)
+ pyhoca-cli
+ 0.5.0.4-1 (ubuntu)
+ 0.6.0.1 (ppa:x2go/stable)
There is one combination that did not work:
x2goserver 4.1.0.3-0~1708~ubuntu18.04.1 (ppa:…
[View More]x2go/stable) with
pyhoca-cli 0.6.0.1 (ppa:x2go/stable)
It failed with the following message, which I assume is a bug:
"
a bytes-like object is required, not 'str'
pyhoca-cli: error: the remote server does not have the X2Go Server
software installed
"
[View Less]
Package: x2goserver
Version: 4.0.1.20
Summary:
As stated in the wiki https://wiki.x2go.org/doku.php/wiki:advanced:nx-keyboard-shortcuts
The action "close_session" should terminate the session.
But, pressing Ctrl-Alt-t in a "local desktop" session does not "terminate" the session.
Steps to reproduce:
0. Create a new session profile in x2goclient with session type "Connect to local desktop";
1. Connect to remote computer using this session profile;
2. Press Ctrl-Alt-t at the client.
Expected …
[View More]behaviour:
The remote desktop window on the client should close, the connection should be terminated.
Actual behaviour:
The remote desktop window on the client does not close, the connection is not terminated.
The following log entries appears in the server's system journal:
```
Oct 26 13:50:39 localhost /usr/bin/x2gosuspend-session[31790]: session with ID alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24 has been suspended successfully
Oct 26 13:50:45 localhost su[31900]: Successful su for alex by root
Oct 26 13:50:45 localhost su[31900]: + ??? root:alex
Oct 26 13:50:45 localhost su[31900]: pam_unix(su:session): session opened for user alex by (uid=0)
Oct 26 13:50:45 localhost systemd-logind[508]: New session c99 of user alex.
Oct 26 13:50:45 localhost systemd[1]: Started Session c99 of user alex.
Oct 26 13:50:46 localhost su[31900]: pam_unix(su:session): session closed for user alex
Oct 26 13:50:46 localhost su[31923]: Successful su for alex by root
Oct 26 13:50:46 localhost su[31923]: + ??? root:alex
Oct 26 13:50:46 localhost su[31923]: pam_unix(su:session): session opened for user alex by (uid=0)
Oct 26 13:50:46 localhost systemd-logind[508]: Removed session c99.
Oct 26 13:50:46 localhost systemd-logind[508]: New session c100 of user alex.
Oct 26 13:50:46 localhost systemd[1]: Started Session c100 of user alex.
Oct 26 13:50:49 localhost /usr/bin/x2gosuspend-session[32026]: session with ID alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24 has been suspended successfully
Oct 26 13:50:50 localhost su[31923]: pam_unix(su:session): session closed for user alex
Oct 26 13:50:50 localhost systemd-logind[508]: Removed session c100.
Oct 26 13:50:53 localhost /usr/sbin/x2gocleansessions[12745]: alex-50-1508997021_stS1XSHADalexXSHADPP0_dp24: session status S desynchronized with current status (R) and session suspend already tried unsuccessfully
```
Other infomation:
0. Executing x2gosuspend-session <ID> on the server has the same effect as pressing C-A-t at the client.
1. Execuitng x2goterminate-session <ID> on the server does terminates the session and closes the client window.
3. Server-side /etc/x2go/keystrokes.cfg: http://paste.debian.net/plain/992795
-- System Information (server and client):
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
[View Less]
Package: x2goclient for windows
Version: 4.0.5.0
Downloaded new version of x2goclient for a new Dell Laptop. Screen resolution 3200x1800. OS Windows 10 (just checked, same problem on similar machine in Windows 8.1)
When I open the main program, the fonts and windows do not scale well in the session selection boxes
When I create a new session and try to open it, I can not see the list of open sessions to connect to.
This appears to be a scaling issue for high DPI systems.
I tried Windows …
[View More]7, Windows 8 compatibility modes. I tries to disable display scaling on high DPI systems (see attached images)
[View Less]
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
…
[View More]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
[View Less]
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 …
[View More]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
[View Less]
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 …
[View More]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>
[View Less]
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 …
[View More]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
[View Less]
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.