x2go-dev October 2016

x2go-dev@lists.x2go.org

17 participants
124 discussions

Bug#1103: app rendering (glx)
by Oleg Franchuk 19 Oct '16

19 Oct '16

Package: x2goserver Version: 4.0.1.19 Hi. We are using x2goserver as remote desktop on the work. On some apps we have a problem with rendering via internet, over local lan too, such as google-chrome for example. We try use glx 1.4 on you instruction http://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround, but that does not give effect. Maybe we does do some mistake's when use glx1.4 or badly understand your instruction! OS: debian 8.6 (jessie) amd64 Thanks for the help)

1 0

x2goagent-virtual
by Orion Poplawski 18 Oct '16

18 Oct '16

What's the purpose behind the x2goagent-virtual provides? Are there going to be multiple implementations of the x2goagent that provide it? Also, all Obsoletes should specify a version so that the name can be re-introduced in the future. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

2 2

Bug#1102: Kerberos (GSSAPI) auth fails there is an sshd banner and the client is on Linux (or Mac OS X)
by Mike DePaulo 13 Oct '16

13 Oct '16

Package: x2goclient Version: 4.0.5.2 When the following conditions are met: 1. You are using Kerberos (GSSAPI) auth 2. You are using the Linux client (Mac client is probably affected also, although I have not tested it. Windows is unaffected, I tested it.) 3. A "banner" is enabled on the SSH server 4. `x2golistsessions` lists no sessions. e.g., you do not already have a session running. Kerberos (GSSAPI) auth fails. This is because the x2goclient code considers the connection to have failed if the `ssh` command has 0 length standard output (in between the delimeters), but it does have standard error. A connection is made to the remote system to run `x2golistsessions`, which returns no standard output when there are no existing sessions. However, the `ssh` command outputs the banner on standard error. Note that the banner is outputted in a popup window, as if it were an SSH connection error. This is a separate bug IMHO.

1 0

Bug#1092: X2Go issue (in src:x2gothinclient) has been marked as pending for release
by Oleksandr Shneyder 13 Oct '16

13 Oct '16

tag #1092 pending fixed #1092 1.5.0.0 thanks Hello, X2Go issue #1092 (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=75211b6 The issue will most likely be fixed in src:x2gothinclient (1.5.0.0). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 75211b6e724bd896d85d915c754703cabcf37187 Author: Oleksandr Shneyder <o.shneyder(a)phoca-gmbh.de> Date: Thu Oct 13 16:35:54 2016 +0200 x2gothinclientd: load config file when starting PulseAudio. Fixes: 1092. diff --git a/debian/changelog b/debian/changelog index 0f84002..68a0aba 100644 --- a/debian/changelog +++ b/debian/changelog @@ -106,6 +106,9 @@ x2gothinclient (1.5.0.0-0x2go1) UNRELEASED; urgency=low - Uploaders: add myself. Also, force a rebuild due to the changed versioning. + [ Oleksandr Shneyder ] + * x2gothinclientd: load config file when starting PulseAudio. Fixes: 1092. + -- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Thu, 27 Feb 2014 12:03:00 +0100 x2gothinclient (1.1.0.2-0x2go1) unstable; urgency=low

2 1

Bug#1101: Acknowledgement (x2goserver 4.0.1.19 mouse position reporting under ubuntu)
by Rick Benkstein 11 Oct '16

11 Oct '16

I have a solution: Under curses there is a command mousemask that is used to turn on the mouse. It has a choice "ALL_MOUSE_EVENTS" and another "REPORT_MOUSE_POSITION". Under the Debian system the first choice does both. Under Ubuntu when I chose both (ALL_MOUSE_EVENTS | REPORT_MOUSE_POSTION) the mouse position was captured. Rick Benkstein -----Original Message----- From: X2Go Bug Tracking System [mailto:owner@bugs.x2go.org] Sent: Tuesday, October 11, 2016 11:40 AM To: Rick Benkstein <rbenkstein(a)cendatsys.com> Subject: Bug#1101: Acknowledgement (x2goserver 4.0.1.19 mouse position reporting under ubuntu) Thank you for filing a new Bug report with X2Go. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): X2Go Developers <x2go-dev(a)lists.x2go.org> If you wish to submit further information on this problem, please send it to 1101(a)bugs.x2go.org. Please do not send mail to owner(a)bugs.x2go.org unless you wish to report a problem with the Bug-tracking system. -- 1101: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1101 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#1101: x2goserver 4.0.1.19 mouse position reporting under ubuntu
by Rick Benkstein 11 Oct '16

11 Oct '16

Package: X2goserver Version: 4.0.1.19 Usage: Using ncurses to report position of mouse - Microsoft x2goclient Problem: Works perfectly under Debian7.0 and 7.7 Does not work under Ubuntu 14.04. Program highlights an area based on the position of the mouse. It works if the Shift or Ctrl or Alt keys are held else not - If, for instance, the shift key is held the mouse position is reported. On other Debian systems using Gnome 3.4.2 and Gnome-terminal 3.4.1.1 it works perfectly. Under Ubuntu 14.04 I have tried Gnome-terminal 3.8.4 and xfce desktop with xfce-terminal When clicked, the mouse location is reporting the position perfectly - it just doesn't report the movement. Rick Benkstein Centurion Data Systems 262-524-9290

1 0

Bug#1100: xterm's shell started from x2goclient has wrong PATH
by Mark Dixon 11 Oct '16

11 Oct '16

Package: x2goclient Version: 4.0.5.1 When an xterm is started via the x2goclient (either using the Published Applications feature, or asking for a 'Single application' of 'Terminal'), the PATH environment variable in the environment given to the user is not set as expected. What I see from the xterm's shell: $ echo $PATH /usr/local/bin:/usr/bin:/bin:/opt/puppetlabs/bin:/apps/bin What I see from an ordinary ssh login: $ echo $PATH /apps/mpi/bin:/apps/developers/libraries/openmpi/2.0.0/1/intel-16.0.2/bin:/apps/developers/compilers/intel/16.0.2/1/default/compilers_and_libraries_2016.2.181/linux/bin/intel64:/apps/developers/compilers/intel/16.0.2/1/default/debugger_2016/gdb/intel64_mic/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/puppetlabs/bin:/apps/bin This seems to be triggered by the fix for bug #336 (commit 4eb1fd1), which introduced the following characters into the launch commands in src/sshprocess.cpp: export PATH=\"/usr/local/bin:/usr/bin:/bin\"; This causes a problem because the login scripts are sourced both before and after the PATH is overridden. The way that some ordinary login scripts are written behave badly in this situation - here are some examples on our CentOS 7 system: Example 1, /etc/profile.d/qt.sh (from OS package qt3-3.3.8b-51.el7.x86_64) contains: # Qt initialization script (sh) # In multilib environments there is a preferred architecture, 64 bit over 32 bit in x86_64, # ppc64. When a conflict is found between two packages corresponding with different arches, # the installed file is the one from the preferred arch. This is very common for executables # in /usr/bin, for example. If the file /usr/bin/foo is found in an x86_64 package and in # an i386 package, the executable from x86_64 will be installe if [ -z "${QTDIR}" ]; then case `uname -m` in x86_64 | ia64 | s390x | ppc64) QT_PREFIXES="/usr/lib64/qt-3.3 /usr/lib/qt-3.3" ;; * ) QT_PREFIXES="/usr/lib/qt-3.3 /usr/lib64/qt-3.3" ;; esac for QTDIR in ${QT_PREFIXES} ; do test -d "${QTDIR}" && break done unset QT_PREFIXES if ! echo ${PATH} | /bin/grep -q $QTDIR/bin ; then PATH=$QTDIR/bin:${PATH} fi QTINC="$QTDIR/include" QTLIB="$QTDIR/lib" export QTDIR QTINC QTLIB PATH fi The first time this runs, PATH, QTDIR and the rest of the QT environment is set normally. PATH is then overridden by the x2go client. The second time this runs, $QTDIR is not a zero length string, so $QTDIR/bin is not added back to the PATH. This explains why /usr/lib64/qt-3.3/bin does not appear in xterm's bash PATH environment variable. Example 2, /etc/profile.d/modules.sh We have the 'module' command installed (http://modules.sourceforge.net/) and doing something like this: # Setup 'module' environment case "$0" in -bash|bash|*/bash) . /apps/Modules/default/init/bash ;; -ksh|ksh|*/ksh) . /apps/Modules/default/init/ksh ;; -sh|sh|*/sh) . /apps/Modules/default/init/sh ;; *) . /apps/Modules/default/init/sh ;; # default for scripts esac Followed by /etc/profile.d/zz_modules.sh with: # Load default module 'user' module load user The first time this runs, PATH, the rest of the module environment and the default module are set/loaded normally, including LOADEDMODULES (which keeps track of what modules are loaded). PATH is then overridden by the x2goclient. The second time this runs, modules.sh runs normally, but the module load command in zz_modules.sh doesn't do anything as LOADEDMODULES tells it that it has already loaded 'user'. PATH remains incorrect, although other environment variables (LD_LIBRARY_PATH, etc.) are correct. To be honest, I don't understand the logic of the bug that originally prompted the change, #336. If an attacker has access to the user's account on the remote system, there are endless possibilities for them to infiltrate the x2go client with arbitrary data. Additionally, the fix for #336 unexpectedly limits the number of places a system administrator is permitted to install x2go. Can someone help, please? Getting rid of overriding the server-side PATH in the client, or other solution, would allow us to offer x2go to our users, which would be really cool. Thanks, Mark

1 0

Bug#1072: X2Go Client: top 24 pixels in fullscreen session do not respond to mouse clicks
by Jason Heeris 11 Oct '16

11 Oct '16

I use Gnome 3 on my client, and run XFCE on the server. I have the same problem: even when run fullscreen (launched fullscreen), an area at the top of the screen corresponding to the *client's* Gnome 3 bar does not respond to clicks. I have my server's XFCE menu on the left, so this means window decorations and title bars, as well as a bit of the top of the menu, are unresponsive. Toggling full screen with ctrl-alt-f (off and on again) doesn't help. I also see the black/white cursor problem described. Client: Ubuntu 16.04.1 LTS, x2goclient 4.0.5.2-0~1205~ubuntu16.04.1 (from PPA), Gnome 3.18 Server: Ubuntu 14.04.5 LTS, x2goserver 4.0.1.19-0~1064~ubuntu14.04.1 (from PPA), XFCE 4.10.1-3ubuntu5 - Jason

1 0

Bug#1099: baikal test
by jkirsz 10 Oct '16

10 Oct '16

I just tried x2goserver from baikal ppa, same problem.

1 0

Bug#1099: Cannot open default display error with x2goclient
by jkirsz 10 Oct '16

10 Oct '16

Package: x2goclient Version: 4.0.5.2 With osx, windows and linux x2goclients, i cant connect to my x2goserver. Server version : 4.0.1.19-0~1064~ubuntu16.04.1 It prints me : Cannot open display "Default Display". X11Fowarding is enable in sshd, and pyhoca-gui works well. # x2goclient --debug [...] x2go-DEBUG-../src/sshmasterconnection.cpp:663> User authentication OK. x2go-DEBUG-../src/onmainwindow.cpp:2884> SSH connection established. x2go-DEBUG-../src/onmainwindow.cpp:3193> Continue normal X2Go session x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 0: "export HOSTNAME && x2golistsessions" x2go-DEBUG-../src/sshprocess.cpp:204> this=SshProcess(0x172ffb0) Running masterCon->addChannelConnection(this, ' "53babb0b-3b22-4ee6-a356-463aab557b3a" ', ' "bash -l -c 'echo "X2GODATABEGIN:53babb0b-3b22-4ee6-a356-463aab557b3a"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:53babb0b-3" '); x2go-DEBUG-../src/sshmasterconnection.cpp:1324> Locking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1326> Passing new channel conenction object to channelConnections. x2go-DEBUG-../src/sshmasterconnection.cpp:1328> Unlocking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1516> Creating new channel. x2go-DEBUG-../src/sshmasterconnection.cpp:1520> New channel:0x7fd4a0012c90 x2go-DEBUG-../src/sshmasterconnection.cpp:1551> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:53babb0b-3b22-4ee6-a356-463aab557b3a"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:53babb0b-3b22-4ee6-a356-463aab557b3a";'" x2go-DEBUG-../src/sshmasterconnection.cpp:1574> New exec channel created. x2go-DEBUG-../src/sshmasterconnection.cpp:1623> EOF on channel 0x7fd4a0012c90; SshProcess object: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:1746> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:1750> Channel closed. x2go-DEBUG-../src/sshprocess.cpp:517> SSH finished: raw output (stdout): "X2GODATABEGIN:53babb0b-3b22-4ee6-a356-463aab557b3a X2GODATAEND:53babb0b-3b22-4ee6-a356-463aab557b3a " x2go-DEBUG-../src/sshprocess.cpp:523> Have stderr only, something must be wrong. x2go-DEBUG-../src/sshprocess.cpp:528> SSH finished: false - "Cannot open display "default display" " (0). x2go-DEBUG-../src/onmainwindow.cpp:3582> "Cannot open display "default display" "

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev October 2016