x2go-dev

x2go-dev@lists.x2go.org

5400 discussions

Bug#1061: failure to complete connection when profile files on server contain bashisms
by lucisandor＠gmail.com 23 Jul '16

23 Jul '16

Package: x2goserver Version: 4.0.1.19 failure to complete connection when profile files on server contain bashisms On a group of servers using Debian Stretch, X2Go server (version 4.0.1.19-0x2go2+git20160621.1064+stretch.main.1) was not accepting incoming connections. Namely, SSH logging in succeeded, X2go client would open a black window, but the window would close by itself in 1-2 seconds. I found that, during the login process, the server was sourcing Bash profile files assuming they were POSIX-compliant. At the first encounter of a bashism, such as an array, the script would crash, and the whole session would be killed. I tracked the issue down by inserting in /etc/x2go/Xsession (a /bin/sh file) a logging line: # Load profile for file in "/etc/profile" "$HOME/.profile" "/etc/xprofile" "$HOME/.xprofile"; do echo "$file" | /usr/bin/logger -t x2goloading ..blabla.. done In the log I found: Jul 22 21:32:43 mycomputer /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="xfce4-session" Jul 22 21:32:43 mycomputer x2goloading: /etc/profile Jul 22 21:32:43 mycomputer x2goloading: /home/user/.profile Jul 22 21:32:43 mycomputer /usr/bin/x2goruncommand: command /usr/bin/xfce4-session has finished What happened was that I had my /home/user/.profile source another script that I wrote $ tail /home/user/.profile ...blabla... # set PATH so it includes user's private bin if it exists if [ -d "$HOME/bin" ] ; then PATH="$HOME/bin:$PATH" fi . /etc/mybashsettings.sh $ cat /etc/mybashsettings.sh #!/bin/bash somefunc() { local INPUTLINES INPUTLINES=() } return 0 $ . /etc/mybashsettings.sh $ sh /etc/mybashsettings.sh /etc/mybashsettings.sh: 5: /etc/mybashsettings.sh: Syntax error: "(" unexpected (expecting "}") This is a minimally crashing example. Now, I believe that having bash scripts in one's profile should not be unexpected. In fact, on the aforementioned distro, it seems it is part of bash. I ave: $ head /home/user/.profile # ~/.profile: executed by the command interpreter for login shells. # This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login # exists. # see /usr/share/doc/bash/examples/startup-files for examples. # the files are located in the bash-doc package.

1 0

Bug#1059: pyhoca-gui can't be installed on OpenSUSE from project repository, OBS repository version throws errors
by Albrecht Kolthoff 21 Jul '16

21 Jul '16

Package: pyhoca-gui Version: 0.5.0.6-0.0 While the x2goserver and x2goclient packages are running fine on my machines (server: OpenSUSE Leap 42.1, client: OpenSUSE 13.2), the pyhoca-gui package can't be installed from the x2go repository: http://packages.x2go.org/opensuse/13.2/main/x86_64/ The same applies to the version in the heuler repository which contains nightly builds, as far as I understand. In both cases the package carries a dependency on python-wxWidgets-2_9 which can't be fulfilled by the OpenSUSE repositories; these offer only the 3_0 and alternatively the 2_8 packages. The OpenSUSE Build service version (which is some minor versions behind the current ones on the x2go project server) actually has a 3_0 dependency (instead of 2_9) and can be installed: http://download.opensuse.org/repositories/X11:/RemoteDesktop:/x2go/openSUSE… But: this version refuses to run. When started from a terminal command line, it throws these errors: ak@tantalus:~> pyhoca-gui Traceback (most recent call last): File "/usr/bin/pyhoca-gui", line 35, in <module> from pyhoca.wxgui.launcher import PyHocaGUI_Launcher File "/usr/lib/python2.7/site-packages/pyhoca/wxgui/launcher.py", line 38, in <module> from x2go import X2GOCLIENT_OS File "/usr/lib/python2.7/site-packages/x2go/__init__.py", line 189, in <module> from defaults import X2GOCLIENT_OS File "/usr/lib/python2.7/site-packages/x2go/defaults.py", line 388, in <module> RSAHostKey = paramiko.RSAKey.generate(RSAKEY_STRENGTH) File "/usr/lib/python2.7/site-packages/paramiko/rsakey.py", line 156, in generate public_exponent=65537, key_size=bits, backend=default_backend() File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/backends/__init__.py", line 35, in default_backend _default_backend = MultiBackend(_available_backends()) File "/usr/lib64/python2.7/site-packages/cryptography/hazmat/backends/__init__.py", line 22, in _available_backends "cryptography.backends" AttributeError: 'EntryPoint' object has no attribute 'resolve' Which leads to the situation, that pyhoca-gui can't be run on OpenSUSE at the moment. Which I regret. Best regards Albrecht Kolthoff --

3 5

x2go-client dual-monitors
by Lena Herrmann 19 Jul '16

19 Jul '16

Hello, since a couple of weeks I'm trying to get x2go running properly. The client is a windows machine and on the server runs a linux-debian jessie. My local-mashine as two monitors, which a want to forward to the linux-server. But only one is working. I can widen the window of the x2goclient over the whole screen, the resolution of the linux-server is adjusted, but it interprets all as one screen and not as two. Do you have any solutions how to setup such a system properly? I was trying to find a solution online, but without any luck so far. Thanks for any help Cheers, Lena

1 0

x2go connection timeout
by eastasia 19 Jul '16

19 Jul '16

hi, dear devs, x2go server is installed in gentoo, without firewalls (iptables), it works well. if i brought iptables up with some rules, the client can not connect to the server, connection time out. so the question is which port or port range should i open to make it work? i searched on the web, no proper references. here is my rules, please help me out. thanks. "rules.sh" #!/bin/bash # vars IPT=/sbin/iptables # Flush old rules, old custom tables echo " * flushing old rules" $IPT --flush $IPT --delete-chain # Set default policies for all three default chains echo " * setting default policies" $IPT -P INPUT DROP $IPT -P FORWARD DROP $IPT -P OUTPUT ACCEPT # Allow established and related packets $IPT -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # Open the following ports echo " * allowing ssh on port 22" iptables -A INPUT -p tcp --dport 22 -j ACCEPT iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT # for x2go client connecting to x2go server iptables -A INPUT -p tcp --dport 49 -j ACCEPT iptables -A OUTPUT -p tcp --sport 49 -j ACCEPT iptables -A INPUT -p tcp --dport 50 -j ACCEPT iptables -A OUTPUT -p tcp --dport 50 -j ACCEPT iptables -A INPUT -p tcp --sport 30000 -j ACCEPT iptables -A OUTPUT -p tcp --sport 30000 -j ACCEPT iptables -A INPUT -p tcp --sport 30001 -j ACCEPT iptables -A OUTPUT -p tcp --sport 30001 -j ACCEPT iptables -A INPUT -p tcp --sport 6050 -j ACCEPT iptables -A OUTPUT -p tcp --sport 6050 -j ACCEPT iptables -A INPUT -p tcp --dport 31000:31010 -j ACCEPT iptables -A OUTPUT -p tcp --sport 31000:31010 -j ACCEPT iptables -A INPUT -p tcp --dport 57400:57600 -j ACCEPT iptables -A OUTPUT -p tcp --sport 57400:57600 -j ACCEPT echo " * allowing ftp on port 21" iptables -A INPUT -p tcp --dport 21 -j ACCEPT iptables -A INPUT -p tcp --dport 20 -j ACCEPT echo " * allowing http on port 80" $IPT -A INPUT -p tcp --dport 80 -m state --state NEW -j ACCEPT echo " * allowing https on port 443" $IPT -A INPUT -p tcp --dport 443 -m state --state NEW -j ACCEPT echo " * allowing ping responses" $IPT -A INPUT -p ICMP --icmp-type 8 -j ACCEPT # DROP everything else and Log it $IPT -A INPUT -j LOG $IPT -A INPUT -j DROP # # Save settings # echo " * saving settings" /etc/init.d/iptables save yadong

1 0

Bug#1060: x2goagent exhaust all Sysv5 shared memory segments when running Java GUI app
by Grigory Shamov 18 Jul '16

18 Jul '16

Package: x2goagent Version: 3.5.0.32 We have encountered a strange problem: x2goagent on the server would eat up all the System5 shared memory segments when running a particular Java GUI application. After that any other processes doing shared memory would naturally fail. When the user connects, everything is as usual; then when Java program is opened and starts working (dataset is loaded, some graphics based on it displayed, several threads started to process the data) it quickly uses over 4K of the shared memory segments. In the output 'lsof -u user' there is about 4K lines of the sort: x2goagent 29374 auser DEL REG 0,4 402984941 /SYSV00000000 x2goagent 29374 auser DEL REG 0,4 403017710 /SYSV00000000 x2goagent 29374 auser DEL REG 0,4 403050479 /SYSV00000000 In Œipcs¹ output there is about 4K lines of this sort: ------ Shared Memory Segments -------- key shmid owner perms bytes nattch status 0x00000000 339708005 auser 600 4331520 1 dest 0x00000000 339740774 auser 600 4331520 1 dest 0x00000000 339773543 auser 600 4331520 1 dest The Java application is IGV: https://www.broadinstitute.org/igv/ Could you please advise, what causes this behaviour and what to do? The server¹s OS is CentOS 6.6, I am using X2go packages rebuilt from from EPEL sources. The desktop environment is GNOME. Thank you very much in advance! -- Grigory Shamov Westgrid/ComputeCanada Site Lead University of Manitoba E2-588 EITC Building, (204) 474-9625

1 0

Bug#1030: Repository signing uses weak digest algorithm (SHA1)
by Christian Kreidl 18 Jul '16

18 Jul '16

Package: packages.x2go.org Hi! Repository signing with SHA1 is deprecated in testing: http://packages.x2go.org/debian/dists/stretch/InRelease: Signature by key 972FD88FA0BAFB578D0476DFE1F958385BFE2B6E uses weak digest algorithm (SHA1) Please update your configuration to use SHA256: https://wiki.debian.org/SettingUpSignedAptRepositoryWithReprepro#Generating… Thanks!

3 3

Question about x2goclient xinerama
by Ulrich Sibiller 14 Jul '16

14 Jul '16

Hello, while testing my xinerama re-implementation I noticed that x2goclient reports a wrong width sometimes when simply moving the window without changing the size. The reported size differs by one pixel (too much or too little). When running x2goclient --debug you can see this: x2go-DEBUG-../src/onmainwindow.cpp:10160> "New proxy geometry: (x: 329, y: 214, w: 1440, h: 900" x2go-DEBUG-../src/onmainwindow.cpp:10160> "New proxy geometry: (x: 365, y: 213, w: 1440, h: 900" x2go-DEBUG-../src/onmainwindow.cpp:10160> "New proxy geometry: (x: 825, y: 190, w: 1440, h: 900" x2go-DEBUG-../src/sshprocess.cpp:189> executing remote command via SshProcess object (24): "export DISPLAY=:50;printf '\''1095 0 345 900\n0 0 1095 900'\'' > $HOME/.x2go/C-uli-50-1431636769_stDKDE_dp24/xinerama.conf" -> here the 345 should have been a 344. Interestingly my patched x2goagent (that completely ignores xinerama.conf) sees that value. So I conclude that x2goclient is manipulating the nxproxy window size by one pixel itself. Disabling xinerama in the session's configuration fixes the problem. That off-by-one behaviour is caused by this code in onmainwindow.cpp: void ONMainWindow::slotXineramaConfigured() { if (resumingSession.fullscreen) return; if (xinSizeInc == -1) xinSizeInc=1; else xinSizeInc=-1; #ifdef Q_OS_LINUX lastDisplayGeometry.setWidth(lastDisplayGeometry.width()+xinSizeInc); XSync(QX11Info::display(),false); XResizeWindow(QX11Info::display(), proxyWinId, lastDisplayGeometry.width(),lastDisplayGeometry.height()); XSync(QX11Info::display(),false); #endif #ifdef Q_OS_WIN QRect geom; wapiWindowRect ( (HWND) proxyWinId, geom ); wapiMoveWindow( (HWND) proxyWinId, geom.x(), geom.y(), geom.width()+xinSizeInc, geom.height(),true); lastDisplayGeometry=proxyWinGeometry(); #endif xineramaTimer->start(500); } If I set xinSizeInc to zero in all cases the off-by-one behaviour is completely gone. Why does xinSizeInc exist at all? Uli

5 14

Bug#402: Numlock issues
by jordi＠amospalla.es 12 Jul '16

12 Jul '16

Package: x2goserver Version: 4.0.1.12-0x2go2+git20140108.809+wheezy.main.1 Hello, numlock does not behave correctly. It behaves like if it was randomly and continuously toggling it state. Happens when numlock key is pressed, and after some time, it seems to stabilize in some state (on or off), but it can take some time. Happens on Mate 1.6 desktop environment over Debian 6. No problem on same host with a KDE session. If numlock state is modified with numlockx binary, it works as expected, only the key triggers this. user@host:~$ while numlockx status; do sleep 0.1; done Numlock is off Numlock is off Numlock is on Numlock is on Numlock is off Numlock is on Numlock is off Numlock is on Numlock is off Numlock is on Numlock is off Numlock is off Numlock is on Numlock is on Numlock is off Numlock is on Numlock is on ... Standard output of xev, after typing on it "test" and numlock key: http://paste.debian.net/76762/

3 7

Bug#402: Bug#402: Related issue in Ubuntu MATE...
by Mike Gabriel 12 Jul '16

12 Jul '16

Control: close -1 On Sun Jul 10 08:26:37 2016 GMT+0200, Christopher Chavez wrote: > I was one of the reporters of the numlock issue in > mate-settings-daemon; I agree that the symptoms describe here are due > to that issue. In Debian it has been resolved since > mate-settings-daemon 1.8.2-3 (released Mar 2015). > > Christopher Chavez > Ok, closing this bug then. Greets, Mike > On Tue, Nov 11, 2014 at 5:54 AM, Mike Gabriel > <mike.gabriel(a)das-netzwerkteam.de> wrote: > > This issue (#402) is probably more a MATE upstream problem then an X2Go > > issue itself... > > > > > > Ubuntu MATE: > > https://bugs.launchpad.net/ubuntu-mate/+bug/1364111 > > > > MATE Upstream: > > https://github.com/mate-desktop/mate-settings-daemon/issues/57 > > > _______________________________________________ > x2go-dev mailing list > x2go-dev(a)lists.x2go.org > http://lists.x2go.org/listinfo/x2go-dev > -- Sent from my Jolla

1 0

Bug#694: Another workaround
by Chris 10 Jul '16

10 Jul '16

After years this important issue is still there... On debian jessie one can do: Change /etc/systemd/system/printer.target.wants/cups.service from PrivateTmp=true to PrivateTmp=false I don't really see a necessity for a private tmp anyway ... **** Apart from the workaround, I would say: why use /tmp for the spool area mount points on the server side in the first place? The directories are being owned by the respective user anyway. Why not use the user's home directory under ~/.x2go? Then this problem would be solved without touching x2goserver-printing nor cups-x2go nor the operating system (see the workaround). Chris P.S.: My lack of knowledge: why has the printing be divided in cups-x2go and x2goserver-printing? Why not one package?

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev