x2go-user

x2go-user@lists.x2go.org

3 participants
2322 discussions

Important information: Wrong version of X2Go Server in Baikal LTS Debian archive
by Mike Gabriel 19 Jun '14

19 Jun '14

Dear all, == Summary == we got informed by John McMonagle [1] about wrong package versions in the Debian archive of X2Go. Unfortunately, I only grasped the severity of that bug report a couple of days back. In February 2014, a development snapshot of x2goserver* packages found their way into the Debian-based package archive of X2Go Baikal LTS [2]. This is of course a severe issue and after cross-checking last Monday, I reverted those uploads and provided the correct package versions (X2Go Server 4.0.0.11). No other area of the package archive was affected, only the Baikal LTS packages of X2Go Server for Debian. == How to downgrade == Follow these steps for downgrading the development snapshot (4.1.0.0-preview) to the current Baikal LTS release of X2Go Server (4.0.0.11). Open a terminal and run these commands... $ apt-get update $ apt-cache show x2goserver ### you should see two version of package x2goserver ### x2goserver 4.1.0.0-0x2go1~<something> (which is the currently installed version) ### and ### x2goserver 4.0.0.11-0x2go1+git20140615.736+<debversion>.baikal.1 $ cp /etc/x2go/x2goserver.conf /etc/x2go/x2goserver.conf.bak $ apt-get remove --purge x2goserver-common libx2go-server-perl libx2go-log-perl $ apt-get install x2goserver x2goserver-xsession x2goserver-printing x2goserver-fmbindings $ cp /etc/x2go/x2goserver.conf.bak /etc/x2go/x2goserver.conf ### You may want to view changes between the two config files... $ diff -ur /etc/x2go/x2goserver.conf.bak /etc/x2go/x2goserver.conf # and manually edit the one now installed as x2goserver.conf I am very sorry that this happened, it should not have!!! If you need further help, please contact either me or any other of the devs via our mailing list x2go-user [3] or via IRC [4]. light+love, Mike Gabriel [1] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=429 [2] deb http://packages.x2go.org/debian {squeeze,wheezy,jessie,sid} baikal [3] http://lists.x2go.org/listinfo/x2go-user [4] #x2go at irc.freenode.net (my nick there is "sunweaver") -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Maintenance shutdown of {bugs, code, packages, lists}.x2go.org yesterday (2014-06-18)
by Mike Gabriel 19 Jun '14

19 Jun '14

Hi all, unfortunately, our second server machine required some emergency maintenance yesterday, so that we had to take several services offline yesterday: o package archive o mailing lists o Git repository o bug tracker The system went online yesterday around 15.00 UTC after being down for about 4-5hrs. We apologize for the inconvenience, Mike Gabriel (on behalf of the X2Go team) -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Regarding ssh-agent process being left over
by paim pozhil 17 Jun '14

17 Jun '14

Hi All Is this a known bug on the x2go where after every session logout there is a zoombie process left. ? more information is here https://github.com/paimpozhil/DockerX2go/issues/3 -- Paim Pozhil

1 0

Connection time out, possibly because of ssh tunnel creation failure
by Jakub Urban 16 Jun '14

16 Jun '14

Hello, I cannot connect any more to an x2go server which used to work before. The only thing I can think of that's chaned is the kernel version. The server is a Scientific Linux 6.5 with kernel 3.10.36-1.el6.elrepo.x86_64. x2go is installed from EPEL (x2goserver-4.0.1.13-4.el6.x86_64). Below are logs from the server and pyhoca-gui (although the connection does not work from x2go clients on Windows/Linux either). Anybody has any idea why this does not work? There is no firewall in between the machines. Thanks, Jakub pyhoca-gui log: pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for proxy to come up: 0.4s x 1 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: X2Go control session parameters for profile myserver: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: username: myusername pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: key_filename: dsa2013_private_openssh_nk pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: unique_hostkey_aliases: False pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: look_for_keys: False pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: X2Go terminal session parameters for profile myserver: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: client_encoding: UTF-8 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: set_session_title: False pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: snd_system: none pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: session_type: desktop pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: server_encoding: UTF-8 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: snd_port: 4713 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: rdp_server: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: kbtype: auto pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: applications: ['TERMINAL', 'WWWBROWSER', 'MAILCLIENT', 'OFFICE'] pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: published_applications: False pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: link: adsl pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: xdmcp_server: localhost pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: kbvariant: null pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: geometry: 1700x1000 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: rdp_options: -u X2GO_USER -p X2GO_PASSWORD pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: cmd: GNOME pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: convert_encoding: False pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: kblayout: null pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: session_title: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: dpi: 110 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: pack: 16m-jpeg-9 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: X2Go sshproxy parameters for profile myserver: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_host: proxyhost.mydomain pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_port: 22 pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_look_for_keys: True pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_allow_agent: True pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_key_filename: pyhoca-gui.exe[2868] (x2gosession-pylib) DEBUG: sshproxy_user: pyhoca-gui.exe[2868] (x2gosessregistry-pylib) NOTICE: registering X2Go session myserver... pyhoca-gui.exe[2868] (x2gosessregistry-pylib) DEBUG: registering X2Go session with UUID 3fb8c8de-f2f9-11e3-8dae-eff4f402a373 pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) INFO: executing command on X2Go server ,,myserver'': sh -c "export HOSTNAME && x2golistsessions" pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 1 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 1 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 2 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 2 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 3 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 3 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 4 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 4 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 5 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 6 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 5 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 7 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 6 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 8 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 7 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 9 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 8 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 10 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 9 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 11 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 12 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 10 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 13 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goguardian-pylib) DEBUG: Entering X2Go Guardian client management loop... pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) INFO: executing command on X2Go server ,,myserver'': sh -c "export HOSTNAME && x2golistsessions" pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 11 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 14 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) INFO: executing command on X2Go server ,,myserver'': sh -c "export HOSTNAME && x2golistmounts myusername-50-1402663801_stDGNOME_dp17" pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 12 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 15 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 13 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 16 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 17 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 14 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 18 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 15 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 19 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 16 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) WARN: incoming request to 127.0.0.1:30003 failed on attempt 20 of 20: ChannelException('Connect failed',) pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 17 pyhoca-gui.exe[2868] (x2gofwtunnel-pylib) ERROR: incoming request to 127.0.0.1:30003 failed after 20 attempts pyhoca-gui.exe[2868] (PyHoca-GUI) NOTICE: [myserver - session failure] Forwarding tunnel request to [127.0.0.1]:30003 for session myusername-50-1402663801_stDGNOME_dp17 was denied by remote X2Go/SSH server. Session startup failed. pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) DEBUG: executing command on X2Go server ,,myserver'': sh -c "echo" pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) DEBUG: terminating non-associated session: myusername-50-1402663801_stDGNOME_dp17 pyhoca-gui.exe[2868] (x2gocontrolsession-pylib) DEBUG: executing command on X2Go server ,,myserver'': sh -c "x2goterminate-session myusername-50-1402663801_stDGNOME_dp17" pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 18 pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 19 pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: waiting for port fw tunnel to come up: 0.5s x 20 pyhoca-gui.exe[2868] (x2goproxy-pylib) ERROR: Bringing up NX3 proxy failed. pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: terminating proxy: <Popen at 0x5366630 pid=3664 returncode=None> pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: Shutting down X2Go proxy subprocess pyhoca-gui.exe[2868] (x2goproxy-pylib) WARN: X2Go proxy shutdown gave a message that we may ignore: [Error 5] Access is denied pyhoca-gui.exe[2868] (x2goproxy-pylib) DEBUG: Shutting down Paramiko/SSH forwarding tunnel pyhoca-gui.exe[2868] (x2goguardian-pylib) DEBUG: Entering X2Go Guardian client management loop... /var/log/messages Jun 13 14:30:18 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jun 13 14:30:18 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jun 13 14:30:19 myserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myusername-50-1402662605_stDGNOME_dp17 fail-terminate Jun 13 14:30:21 myserver /usr/bin/x2goumount-session[21341]: x2goumount-session has been called with options: myusername-50-1402662605_stDGNOME_dp17 Jun 13 14:49:59 myserver /usr/bin/x2gofeaturelist: x2gofeaturelist called with options: Jun 13 14:50:00 myserver /usr/bin/x2gostartagent: x2gostartagent called with options: 1700x1000 adsl 16m-jpeg-9 unix-kde-depth_17 null auto 1 D GNOME Jun 13 14:50:00 myserver /usr/bin/x2gosessionlimit[29965]: x2gosessionlimit has been called Jun 13 14:50:01 myserver /usr/bin/x2golistsessions[29968]: x2golistsessions has been called with options: --all-servers Jun 13 14:50:03 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:03 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:03 myserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myusername-50-1402663801_stDGNOME_dp17 pre-start Jun 13 14:50:03 myserver /usr/bin/x2gostartagent: successfully started X2Go agent session with ID myusername-50-1402663801_stDGNOME_dp17 Jun 13 14:50:03 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:04 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:04 myserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myusername-50-1402663801_stDGNOME_dp17 post-start Jun 13 14:50:13 myserver /usr/bin/x2goterminate-session: x2goterminate-session called with options: myusername-50-1402663801_stDGNOME_dp17 Jun 13 14:50:13 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Jun 13 14:50:13 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Jun 13 14:50:13 myserver /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Jun 13 14:50:13 myserver /usr/share/x2go/x2gofeature.d/x2goserver-fmbindings.features: x2goserver-fmbindings.features called with options: X2GO_DESKTOPSHARING Jun 13 14:50:13 myserver /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Jun 13 14:50:13 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:13 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:13 myserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myusername-50-1402663801_stDGNOME_dp17 pre-terminate Jun 13 14:50:13 myserver /usr/bin/x2goterminate-session: ERROR: failed to terminate session with ID myusername-50-1402663801_stDGNOME_dp17 Jun 13 14:50:13 myserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:14 myserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jun 13 14:50:14 myserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: myusername-50-1402663801_stDGNOME_dp17 fail-terminate Jun 13 14:50:15 myserver /usr/bin/x2goumount-session[30612]: x2goumount-session has been called with options: myusername-50-1402663801_stDGNOME_dp17

2 3

Dev packages for X2Go Server "sneaked" themselves into the Baikal LTS package archive
by Mike Gabriel 15 Jun '14

15 Jun '14

Control: close -1 Hi all, I have just stumbled over a very severe flaw in our X2Go package archive for Debian [1]. A development snapshot of X2Go Server (4.1.0.0-preview) got uploaded to the Baikal LTS area. That is a very very severe problem to people who run the long-term supported version of X2Go Server. I have just kicked of a rebuild of all X2Go Server packages of that archive and will provide an announcement and a troubleshooting / downgrading recipe tomorrow. I deeply apologize for this very severe flaw and big thanks to John McMonagle for unravelling this. Unfortunately, his message got ignored till now... Regards, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Occassionally very slow display update
by Milan Knížek 12 Jun '14

12 Jun '14

Hello, I run x2go server 4.0.1.15 on Arch Linux x86_64 xorg-server 1.15.1 x2go-agent 3.5.0.24-1 nxagent 3.5.0.24-1 and x2goclient V.4.0.2.0 (Qt - 4.8.5) on Windows 7 with internal X server. (Installed without admin privileges and running in portable mode.) Anyway, the issue described below happens for many months now, thus it is not related to those particular versions. After connection to the server, the desktop session (KDE) works just fine. However, once I start using apps (usually Firefox, Evolution, Smartgit, digiKam, Dolphin, etc.), the screen behaves like there are timeouts or short drops in connection. The screen may freeze for several seconds completely, it does not react on clicks, keyboard typing, though it still remembers the actions and "replays" them once the desktop resurrects: e.g. the clock widget on task bar quikly displays the seconds timer changes, like in an accelerated movie, then it freezes again. Other times, it just becomes horribly slow - slowly redrawing. A temporary solution is to close the app window and start it again. It usually helps better to disconnect (logout) and connect again. Suspending and resuming the session from the client does not help at all. Note that these issues are not caused by a bad connection per se: I can open another SSH connection from cygqin and transfer big files back and forth w/o problems at full speed (cca 2 Mbps up/down). SSH typing response is also quick, hence latency should not be an issue either. Logs on the server (syslog, x2go log level debug, CLI output of the applications) do not show anything interesting at all. I assume it may be due to the often discussed issues with applications being compiled against up-to-date X libs, while nxagent still uses the old X server. I have tried to use x2goclient on Ubuntu 12.04 (armhf) for some time and it seems it runs stable, w/o the issues. Is there anything I can do at all to improve the user experience? Or at least to debug the issues? regards, Milan -- http://milan-knizek.net/ About linux and photography (Czech only) O linuxu a fotografování

2 2

Solution X2GO Session Broker and X2Go Server over Docker.io
by Felix Hosner 12 Jun '14

12 Jun '14

Hi All In my lab, I would like to build a solution with X2Go Session Broker and X2Go Server with Docker. In the documentation of Session Broker is described as the X2Go server must be entered in the "session profile configuration". host=s-1.pool-e.local (10.0.2.11),s-2.pool-e.local (10.0.2.12),s-3.pool-e.local (10.0.2.13),s-4.pool-e.local (10.0.2.14),s-5.pool-e.local (10.0.2.15) But Docker works over a port mapping. An entry would therefore have to look like this: host=server1.local:xxx1 (10.0.2.11:xxx1),server1.local:xxx2 (10.0.2.11:xxx2),server1.local:xxx3 (10.0.2.11:xxx3),server1.local:xxx4 (10.0.2.11:xxx4) Is that a problem? (Yes / No) If Yes, how can the Probelme be solved and how the solution could look like? Thank you for your feedback Felix PS: Docker - http://www.docker.com/ -- *Notabene: * Die Zukunft soll man nicht voraussehen wollen, sondern möglich machen. Antoine de Saint Exupéry (1900-44), frz. Flieger u. Schriftsteller *Computer Coach GmbH * 3116 Kirchdorf, Thalgutstrasse 10 Tel. 031 782 12 00 Fax 031 782 12 02 fhosner(a)computer-coach.ch www.computer-coach.ch

1 0

Re: [X2Go-User] Pb with x2go agent on ppc64 system
by brian mullan 11 Jun '14

11 Jun '14

Your ifconfig -a picture shows your eth0 interface with a 10.x.x.x address. As 10.x.x.x is non-routeable you must be running in a Virtual Machine environment like virtualbox or kvm or vmware? What is the IP address of the HOST machine that that VM is running in?

2 2

Pb with x2go agent on ppc64 system
by sebastien chabrolles 11 Jun '14

11 Jun '14

I'm working for IBM, one of our partner would like to use build an "applicance" on one of our Power8 system. They would like to give access to their application through "X2go". The operating system used is a Fedora 20 ppc64. In oder to install x2goserver, we have add the Fedora Rawhide repo (x2goagent is not available in the fc20 repo). Intallation process is fine, without any error. But it is impossible to connect to the server from a x2go client. The connection is closed with the following error: running as X2Go Agent NXAGENT - Version 3.5.0 Copyright (C) 2001, 2011 NoMachine. See http://www.nomachine.com/ for more information. Info: Agent running with pid '24808'. Session: Starting session at 'Sat Jun 7 15:37:37 2014'. Info: Proxy running in server mode with pid '24808'. Info: Waiting for connection from 'localhost' on port '30003'. Warning: Refusing connection from '225.3.10.80'. .80' on port '30003'. I don't know what is this IP address !!!!! I tested the same installation on x86 system (FC20 + rawhide repo for x2goserver). Everything works out of the box. Is anybody can help me to solve this issue on ppc64 ? Cordialement / Best Regards Sébastien Chabrolles Power Systems Benchmark Specialist IBM Client Center, Montpellier 1 rue vieille poste 34000 Montpellier FRANCE Tel +33 4 67 34 40 95 Email : s.chabrolles(a)fr.ibm.com Sauf indication contraire ci-dessus:/ Unless stated otherwise above: Compagnie IBM France Siège Social : 17 avenue de l'Europe, 92275 Bois-Colombes Cedex RCS Nanterre 552 118 465 Forme Sociale : S.A.S. Capital Social : 655.732.332,20 ? SIREN/SIRET : 552 118 465 03644 - Code NAF 6202A

3 8

X2Go Windows Client on Windows 8
by James M. Pulver 11 Jun '14

11 Jun '14

We are having great success using the X2Go Client on Windows 7. However, some outside users are running Windows 8 or Windows Vista, and no matter what we can think to do, we cannot get the X2Go Client to run. It starts, freezes for a few seconds, says "Cannot Start X Server" and then exits. Is this a known problem with those OSs? Is there some configuration to make it work? Any ideas? -- James Pulver CLASSE Computer Group Cornell University

2 6

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user