- x2go-user - X2Go ListServ

X2Go: The Gathering 2017 will be taking place in TREUCHTLINGEN, 2017-09-22 to 2017-09-24
by Stefan Baur 03 Jul '17

03 Jul '17

+++ Attention +++ Attention +++ Attention +++ Attention +++ X2Go: The Gathering 2017 will be taking place in TREUCHTLINGEN, Germany, the "birthplace" of X2Go, from 2017-09-22 to 2017-09-24! Registration is now open for: - daytime-only visitors (we need you to register with us, even if you don't intend to stay over night, so the hotel knows how many people attend the conference) - accommodation - talk/workshop proposals For those of you signing up for accommodation, the following rules are part of the deal: 1) If you become sick, then please stay at home. Let us know ASAP so we can cancel your reservation/reassign your room. 2) If you've had recent contact with someone that has some contagious disease, and you are not 100% sure that you're immune - please, stay at home as well, and let us know ASAP so we can cancel your reservation/reassign your room. 3) If you know that someone has a contagious disease, and you've signed up for our event, please do not seek physical contact with that person before the event. If you have anything that needs to be discussed because you need it for the event, use e-mail, phone calls, whatever, but don't visit each other, the reason being rule #2. 4) Reservations cancelled less than 10 days before the event may mean we still have to charge you, if we cannot fill your spot with someone else. Of course, we will do our best to avoid this. Sign-Up Deadline: 2017-09-08 Cost-Free Cancellation Deadline: 2017-09-12 Please sign up ASAP if you intend to attend - we only have a limited amount of beds reserved in advance - first come, first serve. If we're exceeding that number, we run the risk of being unable to accommodate you. Currently available: 7 out of 10 single rooms, 1 out of 1 double room. To register, or to submit a talk/workshop proposal, simply reply to this E-Mail. There will also be a carpool to Treuchtlingen running via Karlsruhe, Stuttgart, Ulm, and possibly Augsburg, should the need arise. Please contact Mihai (ionic(a)ionic.de) if you're interested in joining the carpool as a passenger. The current planning status of this event can be found at the following wiki page: <http://wiki.x2go.org/doku.php/events:x2go-gathering-2017> Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 0

Workaround for X2go's unclickable regions under Gnome 3
by Jason Heeris 25 Jun '17

25 Jun '17

I'm running X2go 4.1.0.0-0~1536~ubuntu17.04.1 under Ubuntu 17.04, using Gnome 3.24 as my desktop environment on the client. Unfortunately this means I keep running into bug #1072/#982, where the top of X2go's session screen is unclickable. Thus I can't close windows, open some menus, etc. See: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=982 https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1072 I'm looking for a way to work around this without completely throwing out my workflow in general. Because my laptop screen is small, running anything less than full screen makes things fiddly and hard to do (plus mostly what I want to do involves graphics). I don't really want to close everything else I'm working on and log in again to XFCE to do something on the server. Is there a way to tweak X2go config or Gnome 3 to avoid this, or an extension somewhere that mitigates it? Even something I could run or change just before launching X2go that I could revert afterwards? Any suggestions would be appreciated. Cheers, Jason

2 5

Logging into x2go session on server
by Ali Morshedi 20 Jun '17

20 Jun '17

Dear all, I use x2go to connect to my office computer (ubuntu 16.04 using XFCE desktop environment). Let's say I'm logged into the server with x2go. Now if I go to my server computer and log in, it logs into a new and different desktop. My question is: is there a way to log into the same desktop that x2go is using when I go back to the office (on my server computer)? Note: I tries using "Connect to local desktop". It does what I want but the image quality is significantly reduced and things become slow and laggy. Thank you in advance, Ali ᐧ

2 1

X2Go: The Gathering 2017 Location - Voting period has been extended!
by Stefan Baur 20 Jun '17

20 Jun '17

+++ Attention +++ Attention +++ Attention +++ Attention +++ X2Go: The Gathering 2017 will be taking place 2017-09-22 to 2017-09-24 *Voting deadline has been extended! Vote for your favorite location!* Folks, we need your votes! Even if there's only a remote chance that you could attend our event at one or more of the listed locations, please, please, please cast your vote! We currently have *the same amount of votes* for *all locations*, which obviously isn't helpful for decision-making. Who's allowed to vote: Everyone that has read the Wiki page or that has received this voting notification via one of the X2Go Mailing Lists, *and hasn't cast their vote yet.* If *you haven't voted yet*, but would like to take part in the voting process, please list the locations you would like to vote for in an E-Mail to: gathering-2017-vote(a)baur-itcs.de Valid options are: - Essen - Stuttgart - Treuchtlingen Please list the locations in the order of your preference: - First entry gets 3 points - Second entry gets 2 points - Third entry gets 1 point If you are unwilling to attend at a particular location, then do not list it at all. *Deadline: We need your vote by Thursday, 2017-06-25, 23:59:59 CEST.* Please note that we will try to respect the outcome of the vote as good as possible, but we reserve the right to pick a different location than the one that gets the most votes in case we detect voting fraud or in case some unforeseen circumstances (like a hotel suddenly becoming unavailable) require us to relocate. To see a detailed description of all locations, as well as their pros and cons, and entertainment options, please visit: <https://wiki.x2go.org/doku.php/events:x2go-gathering-2017> Kind Regards, Stefan Baur (with my X2Go event planner hat on) -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 0

Re: [X2Go-User] Worse image quality after upgrading Firefox to 52 ESR
by Stefan Seidel 15 Jun '17

15 Jun '17

Hi, Firefox 47 disabled XRender by default. It means that remote protocols will see the whole Firefox content as image and deal with it accordingly. For now you can set xrender to true (in about:config search for xrender). It will probably stop working at some point. Stefan

2 1

Worse image quality after upgrading Firefox to 52 ESR
by south0＠tuta.io 15 Jun '17

15 Jun '17

Hi, after upgrading Firefox form v45 ESR to v52 ESR, the image quality in the X2Go client dropped considerably. Using the same setup in both cases, I now see "blocks" of JPEG artifacts scattered around the window. My setup: - Ubuntu 16.04 LTS i686 - X2Go server from stable PPA - X2Go Qt client in Windows (tested in 7 and 10) - nx set to link=lan, pack=adaptive-9, the rest as default - Firefox from Mozilla's builds (https://ftp.mozilla.org/pub/firefox/releases) I'm untaring Firefox to a dedicated dir and pointing X2Go to execute it. The tests were made with fresh Firefox profiles in both cases, with HW acceleration disabled and rendering by cairo. A major difference is that Firefox 45 uses GTK2 while Firefox 52 uses GTK3. The areas with artifacts seem to be placed randomly. Icons next to each other in the chrome may or may not be affected. Multiline paragraphs are sometimes divided across the upper/lower middle of the characters. If I highlight text around quickly, or zoom in/out, I can make the artifact blocks "jump" to other areas in the viewport. After tweaking the font configs, I managed to get rid of the artifacts consistently in text-only documents by using an aliased font against a solid background. Artifacts in the chrome remain nevertheless. If I set the nx pack to rle for instance, the artifacts disappear. I'd still like to know if - this is a bug or expected behaviour - I can still use adaptive-9 while getting a constant/reproducible image quality Let me know if you need more info or sceenshots. Thanks in advance.

3 3

X2Go vs. XRDP
by Stefan Seidel 13 Jun '17

13 Jun '17

Hi, I have been trying to get X2Go to a usable state for a long time. Some may remember that I posted about slow performance even with Gigabit networking, mostly web browser usage was problematic. After having spent very much time trying to optimise X2Go to make it perform acceptably, I gave up. I then found and tried XRDP, and all my problems are solved. Although XRDP (with xorgxrdp drivers) uses more bandwith than X2Go, it is much more usable in almost all situations. Even ADSL links work ok, but with Gigabit connectivity it really flies (including video). I don't like to advertise for other "products", but this has made such a difference that I could not withhold this information from those who are not satisfied with X2Go. Maybe as a means of making X2Go better, I would encourage X2Go developers to install XRDP on a test server and test and compare its performance to X2Go. I would be surprised if X2Go would perform better - in fact I was surprised how much better XRDP was. Maybe there are things that can be done in X2Go to make it better by looking at how XRDP does things. I really wanted X2Go to work, but somehow it didn't work for me. I wish you all the best for improving the project in the future! Stefan

8 13

Heads-Up: X2Go: The Gathering 2017 will be taking place 2017-09-22 to 2017-09-24
by Stefan Baur 29 May '17

29 May '17

+++ Attention +++ Attention +++ Attention +++ Attention +++ X2Go: The Gathering 2017 will be taking place 2017-09-22 to 2017-09-24 We currently have two possible locations (Linuxhotel, and a hacker space in the southwest of Germany) that already confirmed they can host our event in the given timeframe, and are currently evaluating a third (in the city where X2Go was created, Treuchtlingen, Germany). A Wiki page with all available options will get linked and mentioned on the X2Go-Project Mailing List shortly after 2017-05-15 (our Decision Day for the Treuchtlingen location), along with a list of Pros and Cons for each location. We intend to have a public vote amongst all potential participants regarding the location from when said wiki page goes live until 2017-06-15. Note that we reserve the right to deviate from the poll result if it turns out that it would mean an undue hardship for one or more of the core X2Go team members or our sponsors, or if something happens after the end of the polling timeframe that requires us to reconsider, like, a location suddenly increasing prices, strikes, natural disasters, etc. Please mark the date in your calendars already, as while we haven't decided on the location yet, *the date is fixed* - as it is the only weekend where we have enough "critical mass" regarding the core X2Go team members. Kind Regards, Stefan Baur -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

1 1

Fwd: pyhoca-cli printing issue
by Krasikov Oleg Igorevich 25 May '17

25 May '17

Hi, I want to replace old NX server with X2GO. At this moment i have just one issue with printing, and it does not allow to deploy X2GO. x2goclient does not have any issues with printing, but we need to use pyhoca-cli for saving passwords in the startup script. So, when I start pyhoca-cli *krasikov@krasikov-suse:~> pyhoca-cli --session-profile wmove --password 11122233* *pyhoca-cli[29471] NOTICE: preparing requested X2Go session pyhoca-cli[29471] (PyHocaCLI) NOTICE: preparing requested X2Go session pyhoca-cli[29471] (x2gosessregistry-pylib) NOTICE: registering X2Go session wmove... pyhoca-cli[29471] (x2goclient-pylib) NOTICE: initializing X2Go session... pyhoca-cli[29471] (x2gocontrolsession-pylib) NOTICE: connecting to [10.101.2.178]:22 pyhoca-cli[29471] (x2goterminalsession-pylib) NOTICE: x2gomountdirs stdout is: ['dirs:/home/krasikov/.x2go/S-krasikov-53-1493977424_stRkwrite_dp24/spool__PRINT_SPOOL___REVERSESSH_PORT__30014', 'ssh port:30014', 'Host:127.0.0.1', 'User:krasikov', 'inserted, timeout 30 sshfs -o idmap=user,uid=`id -u`,gid=`id -g`,default_permissions,ServerAliveInterval=300,Cipher=blowfish,IdentityFile=/home/krasikov/.x2go/ssh/key.z14529,UserKnownHostsFile=/home/krasikov/.x2go/ssh/key.z14529.ident "krasikov"@127.0.0.1:"/home/krasikov/.x2go/S-krasikov-53-1493977424_stRkwrite_dp24/spool" "/tmp/.x2go-krasikov/spool/C-krasikov-53-1493977424_stRkwrite_dp24" -p 30014', 'mount /home/krasikov/.x2go/S-krasikov-53-1493977424_stRkwrite_dp24/spool ok', ''] pyhoca-cli[29471] (PyHocaCLI) NOTICE: give the X2Go session some time to come up... pyhoca-cli[29471] (PyHocaCLI) NOTICE: Press CTRL+C to suspend the running session... * session started normally and after, print job give me an errror: *pyhoca-cli[29471] (x2goprintqueue-pylib) NOTICE: processing incoming X2Go print job: krasikov-53-1493977424_stRkwrite_dp24_345-krasikov-cupsjob14977X5bFtNsL8GYLdpAo.pdf Exception in thread Thread-12: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/threading.py", line 763, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/site-packages/x2go/printqueue.py", line 258, in x2go_printjob_handler spool_dir=parent_thread.spool_dir, File "/usr/lib/python2.7/site-packages/x2go/printactions.py", line 135, in do_print self._do_print(pdf_file, job_title, spool_dir) File "/usr/lib/python2.7/site-packages/x2go/printactions.py", line 336, in _do_print _hr_filename = self._humanreadable_filename(pdf_file, job_title, spool_dir) File "/usr/lib/python2.7/site-packages/x2go/printactions.py", line 151, in _humanreadable_filename _hr_path = os.path.normpath(os.path.expanduser(os.path.join(os.path.normpath(target_path), '%s.pdf' % utils.slugify(job_title)))) File "/usr/lib/python2.7/site-packages/x2go/utils.py", line 107, in slugify value = unicodedata.normalize('NFKD', unicode(value)).encode('ascii', 'ignore') UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 0: ordinal not in range(128)* * * I think its a bug with codepages on client side. here is my configs: *krasikov@krasikov-suse:~> cat /home/krasikov/.x2goclient/sessions** **[20170427121255689]** **speed=2** **pack=16m-jpeg** **quality=9** **fstunnel=true** **export=** **iconvto=KOI8R** **iconvfrom=UTF-8** **useiconv=false** **fullscreen=false** **multidisp=false** **display=1** **maxdim=false** **rdpclient=rdesktop** **directrdpsettings=** **width=800** **height=600** **dpi=97** **setdpi=true** **xinerama=false** **clipboard=both** **usekbd=true** **type=auto** **sound=false** **soundsystem=pulse** **startsoundsystem=true** **soundtunnel=true** **defsndport=true** **sndport=4713** **print=true** **name=wmove** **icon=:/img/icons/128x128/x2gosession.png** **host=10.101.2.178** **user=krasikov** **key=** **rdpport=3389** **sshport=22** **autologin=false** **krblogin=false** **krbdelegation=false** **directrdp=false** **rootless=true** **published=false** **applications=kwrite, WWWBROWSER, MAILCLIENT, OFFICE, TERMINAL, leafpad, /home/wmove** **command=kwrite** **rdpoptions=** **rdpserver=** **xdmcpserver=localhost** **usesshproxy=false** **sshproxytype=SSH** **sshproxyuser=** **sshproxykeyfile=** **sshproxyhost=** **sshproxyport=22** **sshproxysamepass=false** **sshproxysameuser=false** **sshproxyautologin=false** **sshproxykrblogin=false* *krasikov@krasikov-suse:~> cat /home/krasikov/.x2goclient/printing** **[General]** **showdialog=false** **pdfview=false** **[CUPS]** **defaultprinter=2-HP_M602_pict_hpcups** **[print]** **startcmd=false** **command=lpr** **stdin=false** **ps=false** **[view]** **open=true** **command=xpdf** * *krasikov@krasikov-suse:~> cat /etc/SuSE-release** **openSUSE 13.1 (i586)** **VERSION = 13.1** **CODENAME = Bottle** * *krasikov@krasikov-suse:~> locale** **LANG=ru_RU.UTF-8** **LC_CTYPE="ru_RU.UTF-8"** **LC_NUMERIC="ru_RU.UTF-8"** **LC_TIME="ru_RU.UTF-8"** **LC_COLLATE="ru_RU.UTF-8"** **LC_MONETARY="ru_RU.UTF-8"** **LC_MESSAGES="ru_RU.UTF-8"** **LC_PAPER="ru_RU.UTF-8"** **LC_NAME="ru_RU.UTF-8"** **LC_ADDRESS="ru_RU.UTF-8"** **LC_TELEPHONE="ru_RU.UTF-8"** **LC_MEASUREMENT="ru_RU.UTF-8"** **LC_IDENTIFICATION="ru_RU.UTF-8"** **LC_ALL=* Thank you for any advice -- С уважением, Красиков Олег Игоревич, e-mail:krasikov@finvest.biz e-mail:kr@rp.ru тлф: +7(499)4900547 Best regards, Krasikov Oleg Igorevich e-mail:krasikov@finvest.biz e-mail:kr@rp.ru tel: +7(499)4900547

2 2

Standard client won't connect, pyhoca is fine (addendum)
by Mike Morris 23 May '17

23 May '17

Hummmm; it appears that x2goclient sessions are still not being purged successfully. The first two lines below are a connection attempt while loglevel is "notice"; changing loglevel to "info" immediately began producing info including repeated calls to x2gosuspend-session and x2goumount for the same two sessions on displays 52 and 55... loglevel = notice: May 23 16:33:52 destiny /usr/bin/x2gostartagent: successfully started X2Go agent session with ID mikem-55-1495582428_stRPUBLISHED_dp24 May 23 16:34:45 destiny /usr/bin/*x2gosuspend-session*: session with ID mikem-55-1495582428_stRPUBLISHED_dp24 has been suspended successfully loglevel change = info May 23 16:35:05 destiny /usr/bin/*x2gosuspend-session*:*x2gosuspend-session* called with options: mikem-52-1495577325_stRPUBLISHED_dp24 May 23 16:35:06 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-55-1495582428_stRPUBLISHED_dp24 May 23 16:35:06 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 16:35:06 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 16:35:06 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 16:35:06 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 16:35:07 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 16:35:07 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 16:35:07 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495577325_stRPUBLISHED_dp24 pre-suspend May 23 16:35:08 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 16:35:08 destiny /usr/bin/x2goumount-session[20811]: x2goumount-session has been called with options: mikem-52-1495577325_stRPUBLISHED_dp24 May 23 16:35:08 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 16:35:08 destiny /usr/bin/*x2gosuspend-session*: x2gosuspend-session called with options: mikem-52-1495576959_stRPUBLISHED_dp24 May 23 16:35:08 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 16:35:08 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-55-1495582428_stRPUBLISHED_dp24 pre-suspend May 23 16:35:09 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 16:35:09 destiny /usr/bin/x2goumount-session[20897]: x2goumount-session has been called with options: mikem-55-1495582428_stRPUBLISHED_dp24 May 23 16:35:09 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 16:35:09 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 16:35:09 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 16:35:10 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 16:35:10 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 16:35:10 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 16:35:10 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495576959_stRPUBLISHED_dp24 pre-suspend May 23 16:35:11 destiny /usr/bin/x2goumount-session[21019]: x2goumount-session has been called with options: mikem-52-1495576959_stRPUBLISHED_dp24

1 0

Standard client won't connect, pyhoca is fine
by Mike Morris 23 May '17

23 May '17

I'm an ecstatic X2Go user, and been lurking on this list for a couple of years... I greatly appreciate any assistance. Know that I *have* googled the heck out of this, and read everything relevant I can find, first :-) Both Client & Server are: * Ubuntu 16.04, up to date * X2Go from launchpad ppa, up to date SYMPTOMS: * PYHoca-GUI works fine on my client (no other clients use it) * Standard X2go-client continues to work on other clients (at least, no other complaints), but on my machine: o connects... that is, ssh key negotiate succeeds, and there's a Desktop Notification of "New session started." after login o remote startup ensues, but never changes from "Connecting" to "Connected" o instead after about 20s I get a popup saying "Could not yet establish the connection to the remote proxy. Do you want to terminate the current session?" Any action (Yes, No, timeout) all result in termination. Last night a failed session stuck around forever, with server logs showing attempts to cleansession every 20 or 30 seconds, but it appears that behavior is gone (via something I did below....), though the login failure remains. I've seen threads about similar symptoms several years ago, but all were fixed. Also, none were exactly the same... see logs below. WHAT I'VE TRIED: * deleted all x2go dirs in /tmp, both client and server side * deleted my client side session files, (~/.x2go/[CSF]-<session-id>) * deleted my x2goclient configs (~/.x2goclient) and recreated profile * restarted the x2goserver service on the server - have also rebooted whole server in the "wee hours"... * deleted (backed up of course) the /var/lib/x2go/x2go_sessions sqlite database and reinitialzed it with "x2godbadmin --createdb" But none of the above changed the symptoms. Below are some logs & such... may be too much, or entirely the wrong, information, but I can definitely supply any other info required. Thanks in advance!!!! Gratefully, MikeM ====================================== Client "Show details" textbox during startup: NXPROXY - Version 3.5.0 Copyright (C) 2001, 2010 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '20532'. Session: Starting session at 'Tue May 23 15:08:48 2017'. Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0. Info: Connecting to remote host 'localhost:51909'. x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." Connection timeout, abortingInfo: Aborting the procedure due to signal '15'. Session: Session terminated at 'Tue May 23 15:09:18 2017'. This ("/abortingInfo: Aborting the procedure due to signal '15'./") is about the only real clue for me... but it doesn't say what procedure! :-( Server Logs: With /etc/x2go/x2goserver.conf's loglevel @ debug, tail -f /var/log/syslog | grep x2go: (NOTE: The "mikem" user is the only relevant one, but have not purged a few other session's details) May 23 15:08:41 destiny /usr/lib/x2go/x2gogetstatus[22485]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:41 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:08:41 destiny /usr/lib/x2go/x2gogetstatus[22495]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:41 destiny /usr/lib/x2go/x2gogetagent[22511]: db_getagent called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:08:41 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 15:08:41 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 15:08:41 destiny /usr/lib/x2go/x2gogetstatus[22525]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:41 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 15:08:41 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 15:08:41 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 15:08:41 destiny /usr/bin/x2golistsessions[22591]: x2golistsessions has been called with no option May 23 15:08:41 destiny /usr/lib/x2go/x2gogetstatus[22585]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:41 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:08:42 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:08:42 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-50-1495534287_stRPUBLISHED_dp24 pre-suspend May 23 15:08:42 destiny /usr/bin/x2goumount-session[22653]: x2goumount-session has been called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:08:42 destiny /usr/bin/x2goumount-session[22653]: db_getdisplay called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:08:42 destiny /usr/bin/x2goumount-session[22653]: db_getmounts called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:08:43 destiny /usr/bin/x2golistsessions[22676]: x2golistsessions has been called with no option May 23 15:08:43 destiny /usr/bin/x2golistmounts[22694]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:08:44 destiny /usr/bin/x2gostartagent: x2gostartagent called with options: 1024x768 wan 16m-jpeg-9 unix-kde-depth_24 us auto 1 P PUBLISHED both May 23 15:08:44 destiny /usr/bin/x2gostartagent: SSH port randomization requested. May 23 15:08:44 destiny /usr/bin/x2gostartagent: client announced itself as ,,73.241.243.127'' May 23 15:08:44 destiny /usr/bin/x2gosessionlimit[22742]: x2gosessionlimit has been called May 23 15:08:44 destiny /usr/lib/x2go/x2gogetstatus[22726]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:08:44 destiny /usr/bin/x2golistsessions[22747]: x2golistsessions has been called with options: --all-servers May 23 15:08:44 destiny /usr/lib/x2go/x2gogetstatus[22755]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:44 destiny /usr/lib/x2go/x2gogetdisplays[22783]: db_getdisplays called, server: destiny; return value: |50| |51| |53| |54| |55| May 23 15:08:44 destiny /usr/lib/x2go/x2gogetstatus[22786]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:45 destiny /usr/lib/x2go/x2gogetports[22801]: db_getports called, server: destiny; return value: |37435| |37436| |37437| |46862| |46863| |46864| |53949| |53950| |53951| |56887| |56888| |56889| |57816| |57817| |57818| May 23 15:08:45 destiny /usr/lib/x2go/x2gogetstatus[22806]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:45 destiny /usr/lib/x2go/x2gogetstatus[22835]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:45 destiny /usr/lib/x2go/x2goinsertsession[22834]: db_insertsession called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, server: destiny, session ID: mikem-52-1495577325_stRPUBLISHED_dp24 May 23 15:08:45 destiny /usr/lib/x2go/x2gogetports[22853]: db_getports called, server: destiny; return value: |37435| |37436| |37437| |46862| |46863| |46864| |53949| |53950| |53951| |56887| |56888| |56889| |57816| |57817| |57818| May 23 15:08:45 destiny /usr/lib/x2go/x2goinsertport[22869]: db_insertport called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, server: destiny, SSH port: 50909 May 23 15:08:46 destiny /usr/lib/x2go/x2gogetports[22885]: db_getports called, server: destiny; return value: |37435| |37436| |37437| |46862| |46863| |46864| |50909| |53949| |53950| |53951| |56887| |56888| |56889| |57816| |57817| |57818| May 23 15:08:46 destiny /usr/lib/x2go/x2goinsertport[22902]: db_insertport called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, server: destiny, SSH port: 50910 May 23 15:08:46 destiny /usr/lib/x2go/x2gogetports[22912]: db_getports called, server: destiny; return value: |37435| |37436| |37437| |46862| |46863| |46864| |50909| |50910| |53949| |53950| |53951| |56887| |56888| |56889| |57816| |57817| |57818| May 23 15:08:46 destiny /usr/lib/x2go/x2goinsertport[22928]: db_insertport called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, server: destiny, SSH port: 50911 May 23 15:08:47 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:08:47 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:08:47 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495577325_stRPUBLISHED_dp24 pre-start May 23 15:08:47 destiny /usr/bin/x2gostartagent: successfully started X2Go agent session with ID mikem-52-1495577325_stRPUBLISHED_dp24 May 23 15:08:47 destiny /usr/lib/x2go/x2gogetstatus[22985]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:08:47 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:08:47 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:08:47 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495577325_stRPUBLISHED_dp24 post-start May 23 15:08:48 destiny /usr/lib/x2go/x2gogetstatus[23023]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:48 destiny /usr/lib/x2go/x2gocreatesession[23048]: db_createsession called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, cookie: 8ce8cec30ab8abf7a0f461d688cedb7c, client: 73.241.243.127, pid: 22994, graphics port: 50909, sound port: 50910, file sharing port: 50911 May 23 15:08:48 destiny /usr/lib/x2go/x2gogetstatus[23056]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:48 destiny /usr/lib/x2go/x2gogetstatus[23068]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:48 destiny /usr/lib/x2go/x2gogetstatus[23077]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:48 destiny /usr/lib/x2go/x2gogetstatus[23085]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:08:48 destiny /usr/bin/x2golistsessions[23091]: x2golistsessions has been called with no option May 23 15:08:49 destiny /usr/bin/x2golistmounts[23119]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:08:51 destiny /usr/lib/x2go/x2gogetstatus[23162]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:08:51 destiny /usr/lib/x2go/x2gogetstatus[23171]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:51 destiny /usr/lib/x2go/x2gogetstatus[23180]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:52 destiny /usr/lib/x2go/x2gogetstatus[23188]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:52 destiny /usr/lib/x2go/x2gogetstatus[23201]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:52 destiny /usr/lib/x2go/x2gogetstatus[23217]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:08:54 destiny /usr/bin/x2golistsessions[23253]: x2golistsessions has been called with no option May 23 15:08:55 destiny /usr/lib/x2go/x2gogetstatus[23273]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:08:55 destiny /usr/bin/x2golistmounts[23283]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:08:55 destiny /usr/lib/x2go/x2gogetstatus[23289]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:55 destiny /usr/lib/x2go/x2gogetstatus[23302]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:55 destiny /usr/lib/x2go/x2gogetstatus[23319]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:56 destiny /usr/lib/x2go/x2gogetstatus[23328]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:56 destiny /usr/lib/x2go/x2gogetstatus[23338]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:08:58 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-52-1495576959_stRPUBLISHED_dp24 May 23 15:08:58 destiny /usr/lib/x2go/x2gogetstatus[23383]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:08:58 destiny /usr/lib/x2go/x2gogetagent[23402]: db_getagent called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:08:58 destiny /usr/lib/x2go/x2gogetstatus[23404]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:08:58 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 15:08:59 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 15:08:59 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 15:08:59 destiny /usr/lib/x2go/x2gogetstatus[23429]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:08:59 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 15:08:59 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 15:08:59 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:08:59 destiny /usr/lib/x2go/x2gogetstatus[23462]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:08:59 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:08:59 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495576959_stRPUBLISHED_dp24 pre-suspend May 23 15:08:59 destiny /usr/lib/x2go/x2gogetstatus[23494]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:08:59 destiny /usr/bin/x2goumount-session[23512]: x2goumount-session has been called with options: mikem-52-1495576959_stRPUBLISHED_dp24 May 23 15:08:59 destiny /usr/bin/x2goumount-session[23512]: db_getdisplay called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:08:59 destiny /usr/lib/x2go/x2gogetstatus[23520]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:08:59 destiny /usr/bin/x2goumount-session[23512]: db_getmounts called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:09:00 destiny /usr/bin/x2golistsessions[23546]: x2golistsessions has been called with no option May 23 15:09:00 destiny /usr/bin/x2golistmounts[23559]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:01 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:09:02 destiny /usr/lib/x2go/x2gogetagent[23591]: db_getagent called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:02 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 15:09:02 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 15:09:02 destiny /usr/lib/x2go/x2gogetstatus[23604]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:02 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 15:09:02 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 15:09:02 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 15:09:02 destiny /usr/lib/x2go/x2gogetstatus[23642]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:02 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:09:02 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:09:02 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-50-1495534287_stRPUBLISHED_dp24 pre-suspend May 23 15:09:02 destiny /usr/lib/x2go/x2gogetstatus[23673]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:02 destiny /usr/bin/x2goumount-session[23701]: x2goumount-session has been called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:09:02 destiny /usr/bin/x2goumount-session[23701]: db_getdisplay called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:02 destiny /usr/lib/x2go/x2gogetstatus[23705]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:03 destiny /usr/bin/x2goumount-session[23701]: db_getmounts called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:03 destiny /usr/lib/x2go/x2gogetstatus[23719]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:03 destiny /usr/lib/x2go/x2gogetstatus[23738]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:05 destiny /usr/lib/x2go/x2gogetstatus[23778]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:06 destiny /usr/bin/x2golistsessions[23794]: x2golistsessions has been called with no option May 23 15:09:06 destiny /usr/lib/x2go/x2gogetstatus[23787]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:06 destiny /usr/lib/x2go/x2gogetstatus[23809]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:06 destiny /usr/lib/x2go/x2gogetstatus[23827]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:06 destiny /usr/bin/x2golistmounts[23834]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:06 destiny /usr/lib/x2go/x2gogetstatus[23844]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:06 destiny /usr/lib/x2go/x2gogetstatus[23853]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:09 destiny /usr/lib/x2go/x2gogetstatus[23900]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:09 destiny /usr/lib/x2go/x2gogetstatus[23916]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:09 destiny /usr/lib/x2go/x2gogetstatus[23925]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:10 destiny /usr/lib/x2go/x2gogetstatus[23934]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:10 destiny /usr/lib/x2go/x2gogetstatus[23945]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:10 destiny /usr/lib/x2go/x2gogetstatus[23955]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:11 destiny /usr/bin/x2golistsessions[23985]: x2golistsessions has been called with no option May 23 15:09:12 destiny /usr/bin/x2golistmounts[23998]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:13 destiny /usr/lib/x2go/x2gogetstatus[24028]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:13 destiny /usr/lib/x2go/x2gogetstatus[24039]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:13 destiny /usr/lib/x2go/x2gogetstatus[24049]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:13 destiny /usr/lib/x2go/x2gogetstatus[24057]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:14 destiny /usr/lib/x2go/x2gogetstatus[24074]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:14 destiny /usr/lib/x2go/x2gogetstatus[24082]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:16 destiny /usr/lib/x2go/x2gogetstatus[24129]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:17 destiny /usr/lib/x2go/x2gogetstatus[24139]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:17 destiny /usr/lib/x2go/x2gogetstatus[24157]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:17 destiny /usr/bin/x2golistsessions[24165]: x2golistsessions has been called with no option May 23 15:09:17 destiny /usr/lib/x2go/x2gogetstatus[24175]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:18 destiny /usr/lib/x2go/x2gogetstatus[24190]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:18 destiny /usr/bin/x2golistmounts[24189]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:18 destiny /usr/lib/x2go/x2gogetstatus[24210]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:18 destiny /usr/bin/x2gocmdexitmessage: x2gocmdexitmessage called with options: mikem-52-1495577325_stRPUBLISHED_dp24 May 23 15:09:18 destiny /usr/lib/x2go/x2gogetagent[24237]: db_getagent called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24; return value: 22994 May 23 15:09:19 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-52-1495576959_stRPUBLISHED_dp24 May 23 15:09:19 destiny /usr/lib/x2go/x2gogetagent[24265]: db_getagent called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:09:19 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 15:09:19 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 15:09:19 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 15:09:19 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 15:09:19 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 15:09:19 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:09:20 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:09:20 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-52-1495576959_stRPUBLISHED_dp24 pre-suspend May 23 15:09:20 destiny /usr/bin/x2goumount-session[24351]: x2goumount-session has been called with options: mikem-52-1495576959_stRPUBLISHED_dp24 May 23 15:09:20 destiny /usr/bin/x2goumount-session[24351]: db_getdisplay called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:09:20 destiny /usr/bin/x2goumount-session[24351]: db_getmounts called, session ID: mikem-52-1495576959_stRPUBLISHED_dp24; return value: May 23 15:09:20 destiny /usr/lib/x2go/x2gogetstatus[24380]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:21 destiny /usr/lib/x2go/x2gogetstatus[24389]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:21 destiny /usr/lib/x2go/x2gogetstatus[24399]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:21 destiny /usr/lib/x2go/x2gogetstatus[24413]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:21 destiny /usr/lib/x2go/x2gogetstatus[24425]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:22 destiny /usr/lib/x2go/x2gogetstatus[24433]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:22 destiny /usr/bin/x2gosuspend-session: x2gosuspend-session called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:09:22 destiny /usr/lib/x2go/x2gogetagent[24457]: db_getagent called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:22 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING May 23 15:09:22 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING May 23 15:09:22 destiny /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING May 23 15:09:22 destiny /usr/share/x2go/x2gofeature.d/x2goserver-printing.features: x2goserver-printing.features called with options: X2GO_DESKTOPSHARING May 23 15:09:22 destiny /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING May 23 15:09:23 destiny /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS May 23 15:09:23 destiny /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS May 23 15:09:23 destiny /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: mikem-50-1495534287_stRPUBLISHED_dp24 pre-suspend May 23 15:09:23 destiny /usr/bin/x2goumount-session[24541]: x2goumount-session has been called with options: mikem-50-1495534287_stRPUBLISHED_dp24 May 23 15:09:23 destiny /usr/bin/x2golistsessions[24543]: x2golistsessions has been called with no option May 23 15:09:23 destiny /usr/bin/x2goumount-session[24541]: db_getdisplay called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:23 destiny /usr/bin/x2goumount-session[24541]: db_getmounts called, session ID: mikem-50-1495534287_stRPUBLISHED_dp24; return value: May 23 15:09:23 destiny /usr/bin/x2golistmounts[24572]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:24 destiny /usr/lib/x2go/x2gogetstatus[24598]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:24 destiny /usr/lib/x2go/x2gogetstatus[24611]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:25 destiny /usr/lib/x2go/x2gogetstatus[24624]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:25 destiny /usr/lib/x2go/x2gogetstatus[24632]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:25 destiny /usr/lib/x2go/x2gogetstatus[24643]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:25 destiny /usr/lib/x2go/x2gogetstatus[24656]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:28 destiny /usr/lib/x2go/x2gogetstatus[24716]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:28 destiny /usr/lib/x2go/x2gogetstatus[24727]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:28 destiny /usr/lib/x2go/x2gogetstatus[24736]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R May 23 15:09:29 destiny /usr/lib/x2go/x2gogetstatus[24748]: db_getstatus called, session ID: janicem-54-1495560570_stRPUBLISHED_dp24, return value: R May 23 15:09:29 destiny /usr/bin/x2golistsessions[24763]: x2golistsessions has been called with no option May 23 15:09:29 destiny /usr/lib/x2go/x2gogetstatus[24767]: db_getstatus called, session ID: kdeary-55-1495566339_stRPUBLISHED_dp32, return value: R May 23 15:09:29 destiny /usr/lib/x2go/x2gogetstatus[24788]: db_getstatus called, session ID: mikem-52-1495577325_stRPUBLISHED_dp24, return value: R May 23 15:09:29 destiny /usr/bin/x2golistmounts[24794]: db_getmounts called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24; return value: 127.0.0.1|/tmp/.x2go-mikem/spool/C-mikem-50-1495534687_stRPUBLISHED_dp24| May 23 15:09:31 destiny /usr/lib/x2go/x2gogetstatus[24850]: db_getstatus called, session ID: pcaploe-51-1495565325_stRPUBLISHED_dp32, return value: S May 23 15:09:32 destiny /usr/lib/x2go/x2gogetstatus[24862]: db_getstatus called, session ID: mikem-50-1495534687_stRPUBLISHED_dp24, return value: R May 23 15:09:32 destiny /usr/lib/x2go/x2gogetstatus[24877]: db_getstatus called, session ID: edeamicis-53-1495547220_stRPUBLISHED_dp32, return value: R

1 0

Please help I am stuck with Socket Error: Unknown error
by Tajammul Rafique 21 May '17

21 May '17

I posted this question before but had no luck in finding a solution. Since last month my windows 10 computer with x2go client stopped working with Linux Ubuntu 14.4 x2go server. I tried uninstalling and reinstalling the client but it did not help. In the mean time my co-league's x2go client still works. I captured packets on my computer as attached, all I see is the connection was reset. Why and how to fix it I don't can someone please help? Thanks Tajammul

2 3

OpenSuse Leap 42.2
by Robert Dinse 17 May '17

17 May '17

The stable build of x2go has the xrandr version issue (it has 1.2, OpenSuse 42.2 needs at least 1.3). The nightly build requires nx-libs 3.5.99+. Arctica Project does not have a repository of built libs 3.5.99 but in theory should be possible to build from source, as I've had to do for Zesty. However, a prerequesite for OpenSuse is obs-build, but there is no obs-build packages in OpenSuse Leap 42.2's distribution. I have not been able to find a suitable package elsewhere. I've tried to download from the OpenSuse software website, but it has an error in the URL and won't download. I've tried to find on rpm.pbone.net, no luck. Any other suggestions to get this working? -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

Logging x2go connections?
by Grigory Shamov 04 May '17

04 May '17

Hi All, This perhaps is a trivial question: but is it possible to somehow log/check history of past x2go session on the server? -- Grigory Shamov Westgrid/ComputeCanada Site Lead University of Manitoba E2-588 EITC Building, (204) 474-9625

6 6

Socket error: Unknown error
by Tajammul Rafique 01 May '17

01 May '17

I am trying to connect to Ubuntu workstation remotely usingX2GO client. My co-workers can connect without any problem. But when I try, Iget an error "Socket error: Unknown error". I uninstalled andreinstalled X2GO client but nothing helped. In the past I was able to connectbut not anymore. Any advice? Thanks Tajammul

1 0

Spoke too soon
by Robert Dinse 30 Apr '17

30 Apr '17

Found one other thing that isn't working, the normal menu I get under Ubuntu Mate when I right click the mouse on the background. The menus on the top bar work but not those on the background. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 1

Zesty
by Robert Dinse 30 Apr '17

30 Apr '17

I have re-installed a fresh install of Zesty-Mate on my old Mac Pro 1,1. I had to modify the ISO to work with my odd ball 64-bit CPU but 32-bit BIOS, but other than that it is stock Zesty Mate. I then installed all the tools and dependencies to build the Arctica 3.5.99 version of nx-libs, and installed those. I thehn installed the Nightly Builds version of x2go client and server. Almost everything works, enough for the functionality I need. The only thing that does not work is the background does not get set when I login, it remains block. But I can manually set it and then it works fine. So something is still broke but I don't need a pretty background for things to be functional, so the important things are working for me now. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

Thin/Zero-client solution with desktop feel (video streaming)
by Lars Bonnesen 28 Apr '17

28 Apr '17

Having a setup where I would like to run 10-20 zero-clients (like ThinStation). Users would like to connect to a Windows desktop and stream various videos from services like youtube. I have been setting up ThinStation where a number of test PC's boots directly into FreeRDP and connects to a Windows 2016 RDS-server. It works well except for the streaming part. One single client in full screen fills up 100% of two of the Win2016 RDS 4 Xeon CPUs! I am aware of MS' RemoteFX but this requires HyperV. We are running VMware, and for this, you will have to use Horizon and PCoIP/Blast. Only... the license price for this is simply outrageous. As we would like to keep our VMware virtualization, going to MS' HyperV is something we would be very sad about just because of this. I have been working with NoMachine before, and as I remember, it worked very well with video streaming from the NX client... I was going to try this again, but reading about it, I found numerous places where people wrote "Hey!!! No, no, no... try x2go instead... this is a fork of NoMachine". Ok... this was what I did then. Installed x2go on a CentOS, downloaded the x2go client only to experience that streaming like with FreeRDP and RDS work just as bad. Apart from this, I really liked x2go, and if I am able to get a much better desktop feel with full screen streaming, I would definitely force our users to use this Open Source solution instead. Can anyone in here suggest a way to setup x2go to perform better with streaming like if we used a setup that could handle H.264? Regards, Lars.

1 0

Ubuntu-Mate 17.04 Zesty x2go server borked
by nanook＠eskimo.com 26 Apr '17

26 Apr '17

On a fresh install of Ubuntu-Mate 17.04, after doing updates but before installing any other software other than that which installs by default, I installed x2goserver, x2goserver-xsession, and x2goclient per the instructions on the x2go website. The client works fine, the server has the normal issue with modern Linux's wanting a newer version of xrandr and gives me a 800x600 window even if I specify the full display 1. I can resize the screen using xrandr -s 1920x1080 from a terminal window. I tried installing the Arctica Libs for xenial, this worked on servers which I installed as older versions of Ubuntu and upgraded online but does not work for a fresh install. Doing so results in a disconnect before the screen is drawn. At someone's suggestion here, I built nx-libs from source on Zesty and installed, still disconnects before drawing screen. It does give a small screen which then expands to the full screen size but is black save for the letters X2GO, but it disconnects before drawing the desktop. This is using Mate, the 18.01 version that ships with Zesty. I have attached to files of the output of x2goclient --debug, x2go-debug-good-server.out is what happens when I connect to an x2go server on Zesty 17.04 that has been upgraded from an earlier version and has the xenial arctica nx-libs installed and works. x2go-debug.out is when I connect to the server where I've built the Arctica nx-libs from source, they are version 3.5.99.6-0.1. Thanks for your help.

1 0

x2goserver on Ubuntu 17.04 Zesty
by Robert Dinse 25 Apr '17

25 Apr '17

I have not been successful at getting x2go to work consistently on machines I have upgraded to Ubuntu 17.04, oddly it works on some and not others. I have two machines on which it appears to work fine and two which it does not, one of those it just gives me a black screen and the other it immediately exits. On the machine that it immediately exits it prints some error messages but the client exits too fast to read them. I can't figure out if and where x2go logs erros. I do see some things in the syslog but indicates it is starting the session successfully when obviously it is not. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

3 4

Ubuntu 17.04
by Robert Dinse 25 Apr '17

25 Apr '17

On a machine that x2go was not working, I did a fresh install of Ubuntu Mate 17.04 then only did upgrades. Then I installed x2goserver, x2goserver-xsession, and x2goclient. It worked except that it gave me an 800x600 screen unless I manually reset it using xrandr -s 1680x1050 from the command line. I then installed arctica project Sunweaver's Net nx-libraries, and now it exploded when it tried to connect. I backed out those libs and it worked again. So something has changeed, yet, on two other machines I have arctica project's libs installed and all is well. The only difference is that those machines started out life as 14.04 and were upgraded in place to 17.04, as opposed to being fresh installs. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

1 0

x2go display not opening on windows 10
by Gladia Hotan 24 Apr '17

24 Apr '17

Hi, After a recent windows 10 update, my x2go window no longer opens. The taskbar icon appears and the program is shown as 'running' in task manager, but there is no display window. Any ideas how to fix this? Thanks and best regards, Gladia

1 0

usb fingerprint
by Olaf St. 24 Apr '17

24 Apr '17

Hi! Is there any solution to use usb fingerprint sensor to log-in/load sessions with x2go tce? ⁣Bye, Olaf Gesendet mit TypeApp

1 0

x2goserver can support mutliple clients?
by Randell Palmer 19 Apr '17

19 Apr '17

I have setup a x2goserver and 2 x2goclients : client1 & client 2 Either of the clients will work when it is the only client receiving service from the x2goserver. I can connect one of the x2goclients, client1, to the x2goserver and it will bring up xfce4 as requested and can play music etc. However when I try to start client2 I get the menu which has 3 options. Suspend Terminate New If I select New then the X2GO screen briefly appears and then it returns to the menu. If I select terminate, it kills the session on client1 and then I can select New and client2 will display XFCE4. Is this expected behavior? All 3 are running freshly installed Arch linux. Thank you

4 7

Windows x2go client displays at incorrect resolution
by Davis, Jean-Paul 18 Apr '17

18 Apr '17

I'm hoping that someone out there with more experience will be able to solve this problem! Server = RHEL 7, running local GNOME-3 session at native 3840x2160 (dpi 149) of attached 4K display Installed Packages: x2goagent.x86_64 3.5.0.32-3.el7 @epel x2goclient.x86_64 4.1.0.0-1.el7 @epel-rhel-x86_64-workstation-7 x2goserver.x86_64 4.0.1.20-1.el7 @epel x2goserver-xsession.x86_64 4.0.1.20-1.el7 @epel Settings: /etc/x2go/x2go-agent.options - commented out X2GO_NXAGENT_DEFAULT_OPTIONS+=" -extension XFIXES" /etc/x2go/Xresources - set Xft.dpi: 192 Everything else left at defaults Client = Windows 10, x2go client v4.1.0.0, local native display 2560x1440 (dpi 192) Settings: Session Type = MATE (automatically changes to "Custom desktop" with command "MATE") Display = Fullscreen Set display DPI = 192 The session starts just fine, filling the screen with the MATE desktop, except that the display resolution is incorrect... with following information obtained inside a MATE terminal: jpdavis: xdpyinfo | grep dots resolution: 192x193 dots per inch jpdavis: ps -waux | grep $DISPLAY | grep x2goagent jpdavis 28204 0.2 0.3 217268 57696 ? S 10:05 0:08 /usr/lib64/nx/../x2go/bin/x2goagent -nolisten tcp -nolisten tcp -dpi 192 -D -auth /home/jpdavis/.Xauthority -name X2GO-jpdavis-50-1491062721_stDMATE_dp32 :50 jpdavis: xrandr --prop xrandr: Failed to get size of gamma for output default Screen 0: minimum 320 x 240, current 1280 x 720, maximum 1920 x 1200 default connected 1280x720+0+0 0mm x 0mm Thus the actual dpi being used by the display is 192*1280/2560 = 96, not the 192 sent to x2goagent and reported by xdpyinfo. attempting to change the resolution from inside the session... xrandr --size 1920x1200 works but keeps same actual dpi of 96 (so desktop is larger than my screen) MATE Settings->Hardware->Displays returns error "RANDR extension is too old (must be at least 1.3)" xrandr --version returns xrandr program version 1.4.3 Server reports RandR version 1.2 I get the same behavior if I try sessions with KDE or XFCE instead of MATE. Since the maximum resolution reported by xrandr corresponds to dpi of 192*1920/2560=144 x 192*1200/1440=160, I wondered if it had something to do with the local X session on the server which is at 149 dpi; closing that session, however, makes no difference. Could it be something about the X server that is running on the x2go server? (It is running but with no sessions, just the login greeter). The Windows client generates the following in the file .x2go\<session>\sessions: Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Auth: WARNING! Failed to read data from the X auth command. Auth: WARNING! Generating a fake cookie for X authentication. Loop: WARNING! Could not retrieve the X server authentication cookie. Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... Fork: WARNING! Function fork failed. Error is 11 'Resource temporarily unavailable'. Retrying... ... and the following in the file .x2go\<session>\options: nx/nx,root=/cygdrive/C/Users/jpdavis/X2GO~1,connect=localhost,cookie=6f9207806bc4e3206aa5df26759c77bc,port=60732,errors=/cygdrive/C/Users/jpdavis/X2GO~1/S-JPDA~1/sessions:50 Where could it be getting a session type of 'unix-kde-depth_32' when I've set it to use a MATE session? And where exactly do I find the /cygdrive/C/Users/jpdavis/X2GO~1 directory on my Windows machine? I can't find any files where x2go client saves program preferences or session preferences. Under the client settings, I changed to "use custom X server", pointed to the VcXsrv.exe file that comes with x2go, added "-dpi 192" to the command-line options for all cases, and restarted x2go. This had no effect. I also tried using the XMing X server with the same options, this also had no effect. More interesting information... If I simply Putty ssh to the server and run xrandr I get "Can't open display." If I enable X11 forwarding in Putty but don't start a local X server on the Windows machine, then xrandr returns slightly more information: "Can't open display 134.253.62.153:10.0." If I do this again but first start VcXsrv with the same command-line options as I've set in x2go ("C:\Program Files (x86)\x2goclient\VcXsrv\vcxsrv.exe" -fullscreen -notrayicon -clipboard -dpi 192) then xrandr returns "Screen 0: minimum 0 x 0, current 1280 x 720, maximum 4096 x 4096" (and xdpyinfo still says "192x193 dots per inch"). If I also add the command-line options "-screen 0 2056x1440", I get that resolution but much larger than my real display, and text is even larger. Finally, I tried using Putty X11 forwarding with XMing, with XMing options set via it's XLaunch executable. With XMing set to fullscreen and no additional options passed, xdpyinfo says "75x75 dots per inch" and xrandr returns "Screen 0: minimum 1280 x 720, current 1280 x 720, maximum 1280 x 72." Same result with XMing set to multiple windows. In this mode, graphical applications started from inside Putty actually don't look bad (normal text size). Adding command line option "-dpi 192" to XMing makes xdpyinfo return "192x193 dots per inch" but xrandr output remains the same, and the resulting graphical application text is way too large. Using XMing with Putty and X11 forwarding to start mate-session has the same issue, so I guess this is not actually an x2go problem. I'm still posting here in case someone can help, maybe I'll also look for user mail lists relevant to X in general, or VcXsrv/XMing. So what am I missing? Where is it getting the dpi=96 that the display is actually using? The 96 value makes the session fairly useless, as all display elements are huge compared to the screen. I had this working not that long ago, but I wouldn't be able to confirm exactly what changes have been made in the interim because I don't recall exactly _when_ it was working. Jean-Paul Davis

2 3

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user