x2go-user

x2go-user@lists.x2go.org

2 participants
2322 discussions

Trouble terminating a kde session
by Joao Roscoe 17 May '18

17 May '18

I Have a fresh, up-to-date install of debian 9 x86-64, including x2go from the repos (the package version is 4.1.0.0-0x2go1). So far kde5 is working pretty well. Sure, not as fast as XFCE, but quite usable. With kde5, however, I'm running into an issue at logout: right after clicking the logout button, the display into the session window goes black, and a few seconds later, it shows a dialog stating that ksmserver segfaulted. Clicking "Close" results a briefly displayed second, similar dialog stating the same about drkonqi, and then, after closing that, yes, the session terminates. Using the "Shutdown" button results in exactly the same behaviour. The client is running on up-to-date debian 8 x86 (32 bits). The client package version is 4.0.3.1-4. Has anyone noticed this issue before? Any hints? Best regards, Joao

4 5

Problems with java GUI application
by Kevin Kremer 17 May '18

17 May '18

Hi all, I set up an X2Go server to connect to a remote machine and most applications run very well. Unfortunately I rely on one java application where some of its GUI components suffers huge latencies. Here, actions like a click on a button take up to 10 seconds to perform while there is no delay when running the application without X2Go. The latencies can be reduced to 4 seconds by reducing the connection speed to "MODEM" and the image quality to 0. However, the latency is still huge compared to running the application locally. Furthermore, the java application does not re-print its window and it stays blank when minimizing the X2Go window. My setup: I use Xfce as a desktop, the connection speed is set to "MODEM", the compression algorithm is set to 16m-jpeg, the image quality is set to 0 and I use Oracle's JRE 1.8.0_152. The problems also occur when I connect to the host within the same LAN. Maybe someone has encountered similar problem and can give me a few hints for solving them. Best regards, Kevin

5 10

Load Balancers
by Roger Robinson 11 May '18

11 May '18

Hi, I almost have an x2go session broker set up but I cant get the load balancer to work. I have set Default-agent-query-mode=SSH In x2gobroker.conf I have followed the keygen commands here -> https://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:loadbalancing And have some keys in /var/lib/x2gobroker/.ssh/ root@ukvmlx-ldap-01 ~]# x2gobroker-loadchecker /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.117: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.116: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.115: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) 2018-05-08 14:39:39,200 - loadchecker - INFO - X2Go Session Broker (0.0.3.4), written by Mike Gabriel (X2Go Project) <mike.gabriel(a)das-netzwerkteam.de> 2018-05-08 14:39:39,200 - loadchecker - INFO - Setting up the Load Checker service's environment... 2018-05-08 14:39:39,200 - loadchecker - INFO - X2GOBROKER_DEBUG: True 2018-05-08 14:39:39,200 - loadchecker - INFO - X2GOBROKER_LOADCHECKER_SOCKET: /run/x2gobroker/x2gobroker-loadchecker.socket 2018-05-08 14:39:39,202 - loadchecker - DEBUG - LoadChecker.loadchecker(): load checker thread waking up... 2018-05-08 14:39:39,294 - loadchecker - DEBUG - LoadChecker.loadchecker(): backend=inifile -> processing profiles: [u'pool-KDE-RMS', u'pool-GNOME-RMS'] 2018-05-08 14:39:39,298 - loadchecker - DEBUG - LoadChecker.loadchecker(): querying remote agents for backend=inifile, profile_id=pool-KDE-RMS: [{u'hostaddr': '10.5.17.117', u'hostname': 'ukvmlx-head-03', u'port': 22}, {u'hostaddr': '10.5.17.116', u'hostname': 'ukvmlx-head-02', u'port': 22}, {u'hostaddr': '10.5.17.115', u'hostname': 'ukvmlx-head-01', u'port': 22}] /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.117: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) 2018-05-08 14:39:39,532 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-03 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.117, host address: 10.5.17.117, port: 22) failed 2018-05-08 14:39:39,647 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-KDE-RMS, hostname=ukvmlx-head-03, new load factor is: HOST-UNREACHABLE /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.116: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) 2018-05-08 14:39:39,869 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-02 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.116, host address: 10.5.17.116, port: 22) failed 2018-05-08 14:39:39,984 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-KDE-RMS, hostname=ukvmlx-head-02, new load factor is: HOST-UNREACHABLE /usr/lib/python2.7/site-packages/paramiko/client.py:682: UserWarning: Unknown ssh-rsa host key for 10.5.17.115: 48dc26733e7c1d6f7d1cdb391ce47ccd (key.get_name(), hostname, hexlify(key.get_fingerprint()))) 2018-05-08 14:39:40,209 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-01 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.115, host address: 10.5.17.115, port: 22) failed 2018-05-08 14:39:40,324 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-KDE-RMS, hostname=ukvmlx-head-01, new load factor is: HOST-UNREACHABLE 2018-05-08 14:39:40,328 - loadchecker - DEBUG - LoadChecker.loadchecker(): querying remote agents for backend=inifile, profile_id=pool-GNOME-RMS: [{u'hostaddr': '10.5.17.117', u'hostname': 'ukvmlx-head-03', u'port': 22}, {u'hostaddr': '10.5.17.116', u'hostname': 'ukvmlx-head-02', u'port': 22}, {u'hostaddr': '10.5.17.115', u'hostname': 'ukvmlx-head-01', u'port': 22}] 2018-05-08 14:39:40,527 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-03 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.117, host address: 10.5.17.117, port: 22) failed 2018-05-08 14:39:40,642 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-GNOME-RMS, hostname=ukvmlx-head-03, new load factor is: HOST-UNREACHABLE 2018-05-08 14:39:40,813 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-02 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.116, host address: 10.5.17.116, port: 22) failed 2018-05-08 14:39:40,928 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-GNOME-RMS, hostname=ukvmlx-head-02, new load factor is: HOST-UNREACHABLE 2018-05-08 14:39:41,108 - loadchecker - ERROR - querying remote agent on host ukvmlx-head-01 failed: Authentication to remote X2Go Broker Agent Host failed (user: x2gobroker, hostname: 10.5.17.115, host address: 10.5.17.115, port: 22) failed 2018-05-08 14:39:41,223 - loadchecker - INFO - LoadChecker.loadchecker(): contacted remote broker agent for backend=inifile, profile_id=pool-GNOME-RMS, hostname=ukvmlx-head-01, new load factor is: HOST-UNREACHABLE 2018-05-08 14:39:41,223 - loadchecker - DEBUG - LoadChecker.loadchecker(): sleeping for 300secs before starting next query cycle Thanks for any help, Roger [image002] Roger Robinson HPC Information Systems Engineer Peninsular House, 30 Monument Street London EC3R 8NB, United Kingdom Mobile: +44 7831 853671 Skype: +44 (0) 3934 4318 Zoom: 510-457-3840 - https://rms.zoom.us/j/5104573840

3 2

X2GO cli
by Zelda L 09 May '18

09 May '18

Hello everyone, I have installed x2go server. Is there any way to connect from cli without creating a session with gui from windows client? Thanks for great project, Zelda

5 8

installing x2go server on a mostly headless RHEL 7, solving black screen on Windows client
by Heinz Wrobel 08 May '18

08 May '18

Hi, I found a few interesting things when trying to install the x2go server on a somewhat customized and mostly headless RHEL 7 VM in the cloud, specifically in this case on a RHEL 7.2. These findings might help others, so I thought I'd post the details with some side notes. Following the instructions on https://wiki.x2go.org/doku.php/doc:installation:x2goserver for RHEL 7 was not quite enough to install a working server on this specific RHEL 7 VM. Due to the various documented issues with Gnome 3, I had switched the VM to "Server with GUI" with Xfce, but it still didn't help. On installing Xfce I even had to skip a broken dependency regarding sound support to make it install, but that is a side note only in case you also see something like that. I don't care about sound, so that single thing was easy to ignore for me. In any case, when trying to connect with a Windows x2go client, not even the X desktop window on the client showed up initially. Some investigation and log searching revealed that /usr/bin/x2goruncommand relies on dbus-run-session. This RHEL 7 machine only had dbus-launch because its dbus libs are older, and therefore it completely failed to even invoke the Xsession properly. So I hacked x2goruncommand to do the following fallback: ---- typeset dbus_wrapper="$(type -P "dbus-run-session")" typeset dbus_wrapper_args="" if [ -z "${dbus_wrapper}" ]; then typeset dbus_wrapper="$(type -P "dbus-launch")" typeset dbus_wrapper_args="--exit-with-session" fi [...] XSESSION_EXEC="$cmd" STARTUP="/usr/bin/env LD_LIBRARY_PATH=${LD_LIBRARY_PATH} ${STARTUP}" ${dbus_wrapper} ${dbus_wrapper_args} /etc/x2go/Xsession >> "$MESSAGE_FILE" 2>&1 ---- This little hack was good enough to make the client show the server window, but I got a black window only. No remote desktop in sight still. Using htop on the server, I saw that while the x2goagent was running, there was no xfce4 session of any kind or anything else that looked like a process related to any desktop session. After a long set of weird and clueless debug steps I found a problem because I manually invoked "dbus-launch --exit-with-session /etc/x2go/Xsession". It complained about elements in bash-completion.d not being valid identifiers, starting with "_itweb-settings()". Anything bad that can be fixed should be fixed while debugging along, so I started fixing those to see what might happen next. Iteratively I went through the following files in /etc/bash_completion.d to remove the "-" from the function name identifiers only(!) that it was complaining about: - rhn-migrate-classic-to-rhsm - rhsm-debug - rhsm-icon After the manual invocation of the Xsession no longer complained about bash-completion, I tried the client and ... Ta Da! ... the session came up and seems to work well now. I am sure there are other things that may need fixing and your mileage may vary, but all that is for another day. The moral of the story: It's not always just older dbus libs or similar things. Even seemingly unrelated bash completion quirks can make the x2go Xsession script fail to start up ... and not show anything in any obvious log file. BR, Heinz

2 1

Desktop sharing: "No shared desktop found"
by Jens Bürger 05 May '18

05 May '18

Dear all, I tried to set up desktop sharing as described here: https://wiki.x2go.org/doku.php/doc:usage:desktop-sharing all locally in the same LAN segment, so forwarding of port 22 shouldn’t be an issue. On a session, I start x2godesktopsharing and active sharing of the session. On another client I try to connect to the server as described but I only get a message „No shared desktop found“. What should I check? Kind regards, Jens

1 0

X2go session won't connect
by Paul Borowicz 03 May '18

03 May '18

I've been wrestling with a strange error that only seemed to be affecting my Linux laptop (OpenSUSE Tumbleweed), connecting to my Linux server (OpenSUSE LEAP). Sessions seemed to start, but wouldn't connect. If I tried to connect a 2nd time, it appeared to offer me an existing session, but would not connect. The client scrolled errors related to "unknown remote host 'localhost', and "unable to resolve remote host 'localhost'. Turned out I had removed the localhost entry from my /etc/hosts file. ------------ /etc/hosts 127.0.0.1 localhost --------- Adding this back, fixed this problem. I'm sending this email in case it is helpful to others. I couldn't seem to find any documentation mentioning localhost. Paul Borowicz

4 3

X2Go TCE classic fails / use TCE-Live instead?
by Jens Bürger 02 May '18

02 May '18

Dear people of X2Go, I did a fresh install of Debian 9 in a VM. I installed X2Go as stated here: https://wiki.x2go.org/doku.php/doc:installation:x2goserver Then I tried to install the thin client environment as explained here: https://wiki.x2go.org/doku.php/wiki:advanced:tce:install I did not manage to get it running. First, I tried x2gothinclient_create with mainly the default options. The process aborted, in between 404s came up because the x2go-repos apparently don’t have wheezy support anymore. Then I switched to stretch and tried again. This seemed to work out, but the following links in /srv/tftp are broken (i.e. the files are missing) pxelinux.0 -> /usr/lib/syslinux/pxelinux.0 vesamenu.c32 -> /usr/lib/syslinux/vesamenu.c32 memtest86+.bin -> /opt/x2gothinclient/chroot/boot/memtest86+.bin In a third try, I changed the release to jessie and started x2gothinclient_create over. The process then aborts with unmet dependencies of x2goclient-chroot… I meanwhile noticed the existence of TCE Live, but stating "This page is very much Work in Progess. Please leave a note on x2go-user(a)lists.x2go.org if you're interested in trying this out, so we can guide you along if something goes wrong.“ So, here I am :) My first question is: what is the recommended method for thin client environment? What do I need to consider if I want to use the Live method? Kind regards, Jens

2 5

X2Go gathering 2018
by Christoph 26 Apr '18

26 Apr '18

Hi there, On a recent Linux podcast (TuxRadio) I heard that the project is looking for org support for the upcoming 2018 gathering. Who's the point of contact for this from the project? Please reply directly to this email address so we can have a chat of how I could be of help. Thanks, Chris -- This email account is monitored seven days a week.

2 1

Re: [X2Go-User] Unable to start firefox docker inside x2go
by Bas van den Heuvel 16 Apr '18

16 Apr '18

No it only works on the console (through spice/vnc in this case, but display is :0 ) and I need to do a 'xhost +' first (not needed on my laptop strangely) With the x2go remote display it simply don't work (not via unix socket, or tcp or hard coded $DISPLAY with the IP of the docker host) On 16-04-18 16:05, Ulrich Sibiller wrote: > Hmm, if it works with xhost+ this looks like a cookie issue. Do you > have the matching cookie in your docker session (xauth list)? > > Uli > > On Mon, Apr 16, 2018 at 3:28 PM, Bas van den Heuvel > <bas(a)better-it-solutions.nl> wrote: >> I've tried all variations of $DISPLAY. >> >> Also tried to use xhost+ etc. etc. >> >> and my firefox docker contains the X unix socket. >> >> It works on my laptop without additional work (same docker version) >> >> It works on the x2go machine (connected through VNC/Spice) when I issue >> xhost + first >> >> It simply doesn't work when I use the x2go display >> >> Any ideas ? >> >> It worked before, just don't know what did change >> >> >> >> On 14-04-18 01:43, Mihai Moldovan wrote: >>> * On 04/13/2018 01:54 PM, Bas van den Heuvel wrote: >>>> In the past, I edited /usr/bin/x2gostartagent and removed the "-nolisten >>>> tcp" part, and edited /etc/x2go/x2goagent.options to remove "-nolisten >>>> tcp" >>>> >>>> It's not working, even a simple xeyes docker fails to open display: >>>> >>>> vdheuvel@arthur:/data/home/vdheuvel$ docker run --rm -it >>>> --net=host -e DISPLAY -v $HOME/.Xauthority:/root/.Xauthority >>>> fr3nd/xeyes >>>> No protocol specified >>>> Error: Can't open display: :50.0 >>> Makes sense, since it sounds like the UNIX socket is not passed through to >>> the >>> container. >>> >>> I'm not sure why your TCP workaround worked in the past, though. The >>> DISPLAY >>> syntax should be local-socket-specific (either UNIX socket or abstract >>> UNIX >>> socket), without a fallback to TCP. >>> >>> To use TCP connections, you'd have to specify DISPLAY=localhost:50. >>> >>> >>> The more curious thing here is that normally Xlib tries to connect via an >>> abstract UNIX socket, which theoretically should be also available in a >>> container - unless docker prohibits that, which would be plausible for >>> security >>> reasons. >>> >>> >>> >>> Mihai >>> >> _______________________________________________ >> x2go-user mailing list >> x2go-user(a)lists.x2go.org >> https://lists.x2go.org/listinfo/x2go-user

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user