x2go-dev August 2009

x2go-dev@lists.x2go.org

5 participants
9 discussions

error starting x2goagent
by "Oelmüller, Christoph" 23 Sep '09

23 Sep '09

Hi, we are sporadically encoutering problems starting the x2goagent: session.log says: ================================================================ NXAGENT - Version 3.3.0 Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information. Info: Agent running with pid '21323'. Session: Starting session at 'Wed Aug 19 12:09:46 2009'. Info: Proxy running in server mode with pid '21323'. Info: Waiting for connection from 'localhost' on port '1053'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'X2goagent: Unable to open display 'nx/nx,options=/home/9ffc8ff2/.recobs/options:17''. Session: Aborting session at 'Wed Aug 19 12:10:19 2009'. Session: Session aborted at 'Wed Aug 19 12:10:19 2009'. ================================================================= the options file looks like this: ================================================================= nx/nx,link=adsl,pack=16m-jpeg-8,limit=0,root=/home/9ffc8ff2/.recobs,cache=8M,images=32M,type=unix-kde-depth_32,id=Recobs-Agent,cookie=cd36e6c69a09ce555b5204a7c576045c,errors=/home/9ffc8ff2/.recobs/session.log,keyboard=de,kbtype=pc105/de,keybd=0,geometry=800x600,resize=0,fullscreen=0,accept=localhost,listen=1053:17 ================================================================= commandline starting the agent is: ================================================================= RECOBS_HOST=nx/nx,link=adsl,pack=${RECOBS_PACK},limit=0,root=${SESSION_DIR},cache=8M,images=32M,type=unix-kde-depth_32,\ id=Recobs-Agent,\ cookie=${COOKIE},errors=${SESSION_DIR}/session.log,keyboard="de",kbtype="pc105/de",\ keybd="0",\ geometry="800x600",resize=0,fullscreen=0,accept=localhost,listen=$GR_TUNNEL_PORT echo "${RECOBS_HOST}:${RECOBS_PORT}" >${SESSION_DIR}/options DISPLAY=nx/nx,options=${SESSION_DIR}/options:${RECOBS_PORT} export DISPLAY # ... LD_LIBRARY_PATH="${LD_LIBRARY_PATH}:/usr/lib/x2go" export LD_LIBRARY_PATH # add x-authorization xauth add ${HOSTNAME}/unix:${RECOBS_PORT} MIT-MAGIC-COOKIE-1 ${COOKIE} xauth add ${HOSTNAME}:${RECOBS_PORT} MIT-MAGIC-COOKIE-1 ${COOKIE} # start agent NX_AGENT=":${RECOBS_PORT}" $AGENT_BIN -R -geometry 800x600 -name "ReCoBS-Browser-Session" ${NX_AGENT} 2>${SESSION_DIR}/session.log & ================================================================= ssh-tunnel from client is estabished when starting the agent. Any hints?! Do you know a manpage/documentation/... where the mentioned signals (...due to signal '1') are described? We are just using the your/nx components x2goagent incl. libs on server side. On client side we are using your nxproxy.exe, taken from your nxclient for windows package, but that shouldn't matter at this point. Unfortunally the failure doesn't happen reproducable :-( Thanks a lot in advance Christoph Oelmüller Please help Logica to respect the environment by not printing this email / Pour contribuer comme Logica au respect de l'environnement, merci de ne pas imprimer ce mail / Bitte drucken Sie diese Nachricht nicht aus und helfen Sie so Logica dabei, die Umwelt zu schützen. / Por favor ajude a Logica a respeitar o ambiente nao imprimindo este correio electronico. This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

2 3

keyboard not working quite right in gtk client...
by Douglas M. Stanley 13 Sep '09

13 Sep '09

Hello list, I appologize ahead of time if this has already been brought up, but I couldn't find anything about this yet. I recently set up x2go in a xen guest, and when I try to connect to it with the gtk client, the keyboard isn't right. Everything seems to work, except the arrow keys. If I turn numlock on/off, then the arrows on the keypad seem to work, but not the normal arrow keys. I've tried everything I can think of to set the keyboard both on the client and on the actual host. Everything is set to 105key qwerty US, but the arrow keys still don't work. The maemo client using the directional pad seemed to work fine simulating the arrow keys, so I'm not sure if it would work with the QT client or not as I haven't tried that client yet. Anyone else run into this issue yet? It may very well be due to the machine running under xen, so I'm not sure if anyone else is doing something similar or not. Any help would be greatly appreciated. Thanks, Doug

4 6

install problems solved
by kamerun＠immerda.ch 21 Aug '09

21 Aug '09

hello, we had problems to install x2go: we made a big mistake * we comment the lo interface, it was so silly that we don't see this mistake long time: the result was that the machine work, but the next boot, it was no nfs ... now it is going well. as i told you before i think, it will be better to make a install script, because you can control if it's really work. the documentation has mistakes and for the installer they can be sure, they don't make a tipping / copy mistake. we have done such a script and we can give to the community, if desired. now we have tried to make x2go as a xen virtual machine. it is at the moment not working, we get following mistake something like: in login (without ldap): cannot connecting to host "localhost:30001" proxy with nmap 192.168.0.250 we dont have port 30001 open tcpdump on eth1 where is the dhcpserver try from the client to reach the x2go server / 13:27:03.666347 IP 192.168.0.106.3088888606 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.679034 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3088888606: reply ok 116 getattr [|nfs] 13:27:03.666594 IP 192.168.0.106.930 > x2goserver.planetexpress.de.nfs: . ack 1669475119 win 41915 <nop,nop,timestamp 274543 293666> 13:27:03.668053 IP 192.168.0.106.3105665822 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668130 IP 192.168.0.106.3122443038 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668161 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3105665822: reply ok 116 getattr [|nfs] 13:27:03.668218 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3122443038: reply ok 116 getattr [|nfs] 13:27:03.668424 IP 192.168.0.106.3139220254 > x2goserver.planetexpress.de.nfs: 116 getattr [|nfs] 13:27:03.668471 IP x2goserver.planetexpress.de.nfs > 192.168.0.106.3139220254: reply ok 116 getattr [|nfs]/ some idea, where is the mistake? michel

2 1

Bug-tracker
by Paul van der Vlis 17 Aug '09

17 Aug '09

Hello, I was looking for a bug-tracker for X2go and I found this: https://developer.berlios.de/support/index.php And I did put some bugs and a feature requests in it. But now I am not sure anymore ;-) Is this some kind of a bug-tracker, or is it something else? Is it in use? With regards, Paul van der Vlis. -- http://www.vandervlis.nl/

1 1

Fonts to big or to small
by Paul van der Vlis 17 Aug '09

17 Aug '09

Hello, I still have the problem that my fonts are sometimes to big or to small in the X2go session. Even with the newest client and server. I found this article about this problem: http://www.nomachine.com/ar/view.php?ar_id=AR04C00198 And this seems to be true. In the x2go session I see 75x75 dots per inch, and in my normal session I see 96x96 dots per inch. I used "xdpyinfo | grep resolution" to get this info. In the article they have a link to a solution, they say to use a variable: DEFAULT_X_DPI = "96", but this is for the Nomachine software, not for X2go. I had the same problem in FreeNX. There I found a solution. In the configfile I found this: -------- # Extra options sent to the different nx agents. See !M documentation # for examples of useful parameters. AGENT_EXTRA_OPTIONS_X="-nolisten tcp" -------- I've changed this to: AGENT_EXTRA_OPTIONS_X="-nolisten tcp -dpi 96" And now my DPI-porblems are gone in FreeNX. But this does not help for X2go. Is it possible to give agent-options for X2go? Or do I need to hack /usr/bin/x2gostartagent? With regards, Paul van der Vlis. -- http://www.vandervlis.nl/

2 2

x2go after restart desstroy nfs system
by kamerun＠immerda.ch 07 Aug '09

07 Aug '09

hello, we try to intall x2go and it works, but when we restart the machine, the nfs si no more working. so we test and install only x2goserver and sshfs, nothing else when we restart the nfs is no more working we just wonder what happen and we cannot belive that we are the only x2go user with this problem we have debian 5 lenny (stable) with lxde but we test with gnome and kde too and we follow the installation of the pdf document http://www.x2go.org/fileadmin/doc/de.installation.x2go.pdf who can help? michel

2 1

Password in plain text!?!?!?
by Alexander.Kuchler＠pruftechnik.com 04 Aug '09

04 Aug '09

Dear group, today I figured out you are saving the password entered during the startup of the session in plain text in C:\Documents\%User%\.x2go\ssh\. And not even delete it after closing the session.. You can not be serious!? Especially when knowing you are promoting X2Go for schools etc. where different people might access the same terminals this is not only dangerous but breakneck. Yours, Alexander

3 6

install : at least 4 mistakes in pdf de.insstallation.x2go.pdf and a install script
by kamerun＠immerda.ch 04 Aug '09

04 Aug '09

hello, at least and after many test, we are able to install x2go installation date monday 3.8.2009 installation on machine with debian 5 and lxde (ths same result with a debian 5 machine with gnome) we have done the installtion many times on different machines with the same bad result we can start client and everything is ok after the installation, when reboot, *big problem:* when booting stop in statd (NFS) and follow after ~ 1 minutes after stop y postgres : long message CEST FATAL could not create any TCP/IP sokets after more than 1 minute continue stop again by statd wait long and finish until login after login nfs does not work atftp is running dhcp is running but the file /etc/default/dhcp3-server is overwritten nfs cannot start, postgres has mistakes and it takes very long time to boot it comes to login and we can login, but no postgres and nfs is running. i try to start nfs but it fails, so logically the client cannot start and the machine by shutdown the machine don't shutdown properly we try to start nfs and posstgres manually, but it fails: no socket i wonder if somebody else has the same situation *installation: * from my humble opinion there are at least 4 mistakes in the pdf de.installation.x2go.pdf #echo "192.168.1.1 x2goserver.planetexpress.de x2goserver" >>/opt/ x2gothinclient/etc/hosts -- label linux kernel vmlinuz append root=/dev/nfs nfsroot=192.168.1.1:/opt/x2gothinclient ro initrd=initrd.img ip=dhcp -- option domain-name "planetexpress.de"; option domain-name-servers 192.168.1.1; # x2go thin client range/group subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.100 192.168.0.199; filename "/pxelinux.0"; next-server 192.168.0.250; } when i put the dhcp-server on 192.168.0..250 and change the ip 192.168.1.1 to 192.168.0.250, it works. it is for me a mistake first not to say on which ip address the dhcp server must be set, that it works the description of de.installation.x2go.pdf. anyway with the 192.168.1.1 i could not install an x2go. there is another mistake : # cd /usr/lib/X2go/scrip # ./x2gocreatebase.sh X2go directory does not exist, it exist x2go directory (i don't know, but i was thinking that before it was existing) question: when i want to close a client, it comes back to login it can just switch off, is it normal? a good news is that lxde is working well, i prefer the light lxde than kde. thanks michel

2 1

[x2goserver] After upgrade to 3.0.1-1 no connection possible
by Paul Menzel 03 Aug '09

03 Aug '09

Subject: x2goserver: After upgrade to 3.0.1-1 no connection possible Package: x2goserver Version: 3.0.1-1 Severity: normal *** Please type your report below this line *** Dear X2go hackers, I use Debian Sid/unstable and I upgraded all packages to 3.0.1-1 today and I am not able to get a connection anymore. I tried the GTK client, but hitting Ok just leaves the blue backround and nothing happens. $ x2goclient_gtk & [1] 328 (x2goclient_gtk:328): Gdk-CRITICAL **: gdk_drawable_copy_to_image: assertion `src_x >= 0' failed ssh command: export HOSTNAME && x2golistsessions x2gostartagent 1024x768 lan 16m-jpeg-9 unix-kde-depth_32 de pc105/de 0 R TERMINAL ssh command: x2gostartagent 1024x768 lan 16m-jpeg-9 unix-kde-depth_32 de pc105/de 0 R TERMINAL I tried TERMINAL, GNOME and /usr/bin/xclock to no avail. I did not find anything useful ~/.x2go either. NXPROXY seems to be working. $ nxproxy -S NXPROXY - Version 3.3.0 Copyright (C) 2001, 2007 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '29935'. Session: Starting session at 'Sat Aug 1 16:03:13 2009'. Info: Waiting for connection from any host on port '4008'. Any help is appreciated. Bests, Paul -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages x2goserver depends on: ii lsof 4.81.dfsg.1-1 List open files ii ssh 1:5.1p1-7 secure shell client and server (me ii sudo 1.7.2-2 Provide limited super user privile ii x2goagent 3.3.0-6-1 Special NX-ized client, was develo Versions of packages x2goserver recommends: pn sshfs <none> (no description available) x2goserver suggests no packages. -- no debconf information

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev August 2009