x2go-dev March 2013

x2go-dev@lists.x2go.org

33 participants
117 discussions

Bug#126: Issues resolved in x2gobroker 0.0.0.6
by Mike Gabriel 06 Mar '13

06 Mar '13

close #126 close #127 close #134 thanks The reported issues have been resolved in X2Go Session Broker 0.0.0.5 and 0.0.0.6. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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…

2 1

Bug#133: X2Go Broker: hostname vs. FQDN mixup fixed in X2Go Git
by Mike Gabriel 06 Mar '13

06 Mar '13

tag #133 pending thanks Hi Anders, The hostname vs. FQDN feature has been fixed by these two commits: The main one: http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=9557b6757087589… A slight fix-up: http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=09dff9341cb3dc6… Will be in 0.0.0.7. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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…

2 1

Bug#137: crash when using the --session=<name> and --hide flag with a key that need a password to unlock
by Oleksandr Shneyder 06 Mar '13

06 Mar '13

close #137 http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=bfa63c366057f87… regards, Alex -- Oleksandr Shneyder Dipl. Informatik X2go Core Developer Team email: oleksandr.shneyder(a)obviously-nice.de web: www.obviously-nice.de --> X2go - everywhere@home

3 3

Making an OSX x2goclient customized to your site
by Anders Bruun Olsen 06 Mar '13

06 Mar '13

Hi guys, This is a short guide detailing my adventures in building x2goclient for my OSX users, so they can easily login to our upcoming load balanced x2goserver farm. Problem: In order to login to a load balanced farm you need to connect to a broker, which, at the time of writing this, requires x2goclient to be started with the --broker-url=<url> argument. This is not exactly userfriendly. Most normal desktop users aren't comfortable with the command line. On Linux and Windows you can distribute a new start shortcut with the correct --broker-url added (a .desktop file for Linux and who-knows for Windows). This isn't possible on OSX due to the way applications are packaged. You can still start apps like x2goclient from the command line with arguments and all, but it is a bit more complex and difficult on OSX than Linux. Solution: Build a custom x2goclient package containing a start-script which includes your broker-url, so users will automatically be connected to your broker when starting x2goclient by clicking the app icon. This makes your custom version unusable for power users who need to connect to different servers, but for making it easy for your ordinary users to work from home or on the road, it is great. They only need to install your customized x2goclient and know their username/password. Steps: 1. You need a bunch of prerequisites to be able to build x2goclient: 1a. Install XCode with command line utilities (guides available elsewhere online) 1b. Install MacPorts. Remember to fix your PATH. 1c. Install x2goclient from source using port, to get all dependencies: sudo port -s install x2goclient 1d. Install dylibbundler: sudo port install dylibbundler 2. Fix permissions on certain libraries, or dylibbundler will choke on them, and they won't be added to the finished .app: 2a. In /opt/local/lib: chmod ug+w libssh.4.dylib libcrypto.1.0.0.dylib libssl.1.0.0.dylib (expects that your user is in group 'adm') 2b. At the time of writing this, libtiff needs to be build with other parameters, than the binary version distributed by macports. As soon as a new revision of libtiff is released this step should be unnecessary. Until then, rebuild libtiff: sudo port -s -n upgrade --force tiff 3. Grab the newest version of x2goclient source tarball from x2goclient 4. Unpack it somewhere: tar -zxvf x2goclient-<VERSION>.tar.gz 5. Go into it and create a file called x2goclient-start-script with this content: #!/usr/bin/env bash DIR=$(cd "$(dirname "$0")"; pwd) exec $DIR/x2goclient.bin --broker-url=<YOUR_BROKER_URL> 6. Make it +x: chmod +x x2goclient-start-script 7. Modify macbuild.sh. Between the "Bundling" phase and the "Creating DMG" phase, add these lines: phase "Setting up custom run script" mv "$APPBUNDLE/Contents/MacOS/x2goclient" "$APPBUNDLE/Contents/MacOS/x2goclient.bin" cp x2goclient-start-script "$APPBUNDLE/Contents/MacOS/x2goclient" 8. run macbuild.sh to get both a x2goclient.app and x2goclient.dmg When a newer version of x2goclient is released, just repeat steps 3 through 8. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

1 0

Bug#138: Workardound in X2Go Broker
by Mike Gabriel 06 Mar '13

06 Mar '13

Hi Alex, for the issue in #138 I have added a workaround to x2gobroker.git: http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=620cf778695448f… If you want to test the problem with x2gobroker.git, please comment out the committed code under the above link. Testing: $ git clone git://code.x2go.org/x2gobroker.git $ cd x2gobroker $ git checkout tornado $ # comment out the code from the commit above $ debuild -uc -us $ cd .. $ dpkg -i *x2gobroker*.deb Then launch x2goclient $ x2goclient --broker-url=http://localhost:8080/plain/zeroconf/ If you want to test the broker API with GET method requests, then enable debugging in /etc/default/python-x2gobroker and restart x2gobroker-daemon. Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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

DMG build problem
by Anders Bruun Olsen 06 Mar '13

06 Mar '13

Hi guys, I can succesfully build the DMG on my MacBook (OSX 10.8). I have gone with MacPorts instead of Homebrew, since installing nxcomp/nxproxy with Homebrew isn't straightforward currently. The macbuild.sh script creates a nice dmg for me, and it works fine on my system. However, when I try it on a different system, which doesn't have XCode and MacPorts, it won't start at all. It gives an error report which boils down to it not being able to load the dependent libraries. Specifically it tries to load /opt/local/lib/libcrypto-1.0.0.dylib which doesn't exist on this other system. It is x2goclient.app/Contents/Frameworks/libssl-1.0.0.dylib which references it. The official dmg released by Clemens works fine, it is only my build of it, which has problems. Why does in try to load libcrypto-1.0.0.dylib from /opt instead of the on included in Contents/Frameworks? (I have checked, libcrypto-1.0.0.dylib IS in there). I am on a completely clean install of newest MacPorts and have nothing except x2goclient+deps installed there. And no, just using the official DMG isn't currently an option as we want to provide a simple way for our users to access our new x2gobroker setup. If we don't customize the startup script, they would have to start it from a cmd-line with --broker-url args. This first build however hasn't been customized at all. It is just the official 4.0.0.4 source tarball with no changes. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

3 12

Bug#139: x2goclient: No keyboard input at login in broker-mode on OSX
by Anders Bruun Olsen 06 Mar '13

06 Mar '13

Package: x2goclient Version: 4.0.0.4 Severity: grave The newly released version of x2goclient for Mac OSX is unusable when used in broker-mode. When started with --broker-url a dialog pops up handling authentication against the broker. After this is done, you choose a session. This next authentication dialog is the problem. The cursor is placed in the login-field and is blinking, but nothing appears when keys are pressed on the keyboard. The system bell (*dunk*) is chimed upon each keystroke. Clicking in the field does not change anything. You can place focus in the password field, but no input happens here either. I have also tried setting the broker in noauth mode, so auth is only needed when connecting to the actual terminal servers. The problem is also present here. No initial auth dialog is displayed (of course), but when a session is chosen, the auth dialog will not accept any input. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

1 0

Bug#138: httpbroker client in X2Go Client does not set content type "application/x-www-form-urlencoded"
by Mike Gabriel 06 Mar '13

06 Mar '13

Package: x2goclient Severity: important Version: HEAD Hi Alex, After having some troubles with the web.py framework I have switched over to the more mature (but younger) tornado WSGI framework for the public X2Go Session Broker. However, with tornado, I encouter the below issue in X2Go Client' httpbrokerclient: http://qt-project.org/faq/answer/when_qhttppost_is_called_it_doesnt_seem_to… Could you take a look at that? Otherwise, I can try to fix that, however, you would probably be much quicker. Thanks+Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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

Bug#137: crash when using the --session=<name> and --hide flag with a key that need a password to unlock
by Kjell Otto 05 Mar '13

05 Mar '13

Package: x2goclient Version: 4.0.0.4 crash of x2goclient when started with the --session=<sessionname> and --hide flags and the key used needs a password The client will ask for the password then then instantaniously close itself.

1 0

findbusyservers algorithm
by Anders Bruun Olsen 05 Mar '13

05 Mar '13

Hi Mike, I now have a somewhat working setup of load-balanced login with the broker: Broker: x2go-broker.dsl.lan Terminal servers: testterm1.dsl.lan and testterm2.dsl.lan All are virtualized Ubuntu 12.04 servers. However, everytime we login we end up on testterm1. We can login directly to both servers without any problems. We have tried setting testterm1 to calculate pi and logged a bunch of users into it, to try and add load to have the algorithm choose the other server, but it just isn't happening. Is this a bug? We have tried running /usr/lib/x2go/x2gobroker-agent abo findbusyservers and got this output: OK 16:testterm2 83:testterm1 Which tells me that it might be the x2gobroker-daemon which isn't using the information correctly. -- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)

2 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev March 2013