x2go-user October 2017

x2go-user@lists.x2go.org

21 participants
22 discussions

error getting session bus: Failed to connect to socket Connection refused
by Robert Kudyba 18 Oct '17

18 Oct '17

I was able to get around the below errors by deleting the user’s .x2go directory. Any reason why this continues to happen? We’re using the nightly builds. Here are some logs. Fails with MATE and XFCE. rpm -q x2goserver x2goserver-4.1.0.0-0.0x2go1.0.git20171015.1421.heuler.fc26.x86_64 Unable to contact settings server Failed to connect to socket /run/user/xxxx/bus: Connection refused and the second was Unable to load a failsafesession Unsable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem): environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "etc'), or xfce4-session is installed incorrectly. more .xsession-x2go-o <http://xsession-x2go-erdos.dsm.fordham.edu/>urdomain-errors XSession-x2go: X session started for localuser at Wed Oct 18 09:45:30 EDT 2017 Failed to connect to bus: Connection refused dbus-update-activation-environment: error: unable to connect to D-Bus: Failed to connect to socket /run/user/xxxx/bus: Connection refused (imsettings-check:14190): IMSettings-WARNING **: Could not connect: Connection refused (imsettings-check:14190): GLib-GIO-CRITICAL **: g_dbus_proxy_call_sync_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed mate-session[14003]: WARNING: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=MATE environment variable: Could not connect: Connection refused mate-session[14003]: WARNING: Could not make bus activated clients aware of DISPLAY=:184 environment variable: Could not connect: Connection refused mate-session[14003]: WARNING: Could not make bus activated clients aware of MATE_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused mate-session[14003]: dconf-WARNING: failed to commit changes to dconf: Could not connect: Connection refused mate-session[14003]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/14003,unix/unix:/tmp/.ICE-unix/14003 environment variable: Could not connect: Connection refused Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. mate-session[14003]: Gtk-CRITICAL: gtk_main_quit: assertion 'main_loops != NULL' failed mate-session[14003]: CRITICAL: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. mate-session[14003]: Gtk-CRITICAL: gtk_main_quit: assertion 'main_loops != NULL' failed mate-session[14003]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed mate-session[14003]: WARNING: Could not make bus activated clients aware of GTK_OVERLAY_SCROLLING=0 environment variable: Could not connect: Connection refused mate-session[14003]: WARNING: keycode1 not existent mate-session[14003]: WARNING: keycode2 not existent mate-session[14003]: WARNING: GSIdleMonitor: IDLETIME counter not found mate-session[14003]: GLib-GObject-CRITICAL: object GSIdleMonitor 0x556fe2443c80 finalized while still in-construction mate-session[14003]: GLib-GObject-CRITICAL: Custom constructor for class GSIdleMonitor returned NULL (which is invalid). Please use GInitable instead. mate-session[14003]: CRITICAL: error getting session bus: Failed to connect to socket /run/user/xxxx/bus: Connection refused mate-session[14003]: WARNING: Unable to register presence with session bus mate-session[14003]: CRITICAL: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed mate-session[14003]: CRITICAL: error getting session bus: Failed to connect to socket /run/user/xxxx/bus: Connection refused

1 0

Using x2go on thinclient Wyse
by Bel Pou 16 Oct '17

16 Oct '17

Hello, I want to know if x2go client can be installed on Wyse ThinLinux ? Has anyone ever realized that? Thank's

4 3

Black screen of death - please help
by Brian Walsh 13 Oct '17

13 Oct '17

Hi, I've recently upgraded from redhat 7.0 to 7.3 and as such lost some of my useful tools - one of which was x2go. So I reinstalled the relevant rpms and using the same client and config I now can login but just get a blank black screen with no way to open a terminal etc. I'm using XFCE (as I had before) - tries with gnome and few other session types all with the same result. Been googling this but can't seem to get an answer - appreciate any help as my stare is now as black and blank as the screen below! Client side and server side logs are below. There seems to be a problem with the waiting for keyboard to appear in the server logs - not sure how to change this. There is plenty of disk space on server. Client output: 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 '340'. Session: Starting session at 'Thu Oct 12 18:15:05 2017'. Info: Connecting to remote host 'localhost:47525'. Info: Connection to remote proxy 'localhost:47525' established. Info: Connection with remote proxy completed. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Failed to read data from the X auth command. Warning: Generated a fake cookie for X authentication. Info: Using ADSL link parameters 512/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-7' with session 'unix-kde-depth_32'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: Using cache file '/cygdrive/C/Users/bwalsh/X2GO~1/cache-unix-kde-depth_32/S-57B9405EF162652E97E80D7B7C6EBC56'. Info: Forwarding X11 connections to display 'localhost:1'. Session: Session started at 'Thu Oct 12 18:15:06 2017'. Info: Established X server connection. Info: Using shared memory parameters 0/0K. Server side: Oct 12 18:15:01 bfs-dl360g7-26-xm1 systemd: Started Session 35 of user bwalsh. Oct 12 18:15:01 bfs-dl360g7-26-xm1 systemd-logind: New session 35 of user bwalsh. Oct 12 18:15:01 bfs-dl360g7-26-xm1 systemd: Starting Session 35 of user bwalsh. Oct 12 18:15:03 bfs-dl360g7-26-xm1 /usr/bin/x2goresume-session: x2goresume-session called with options: bwalsh-72-1507827821_stDXFCE_dp32 800x600 adsl 16m-jpeg-7 us auto 1 both Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: bwalsh-72-1507827821_stDXFCE_dp32 pre-resume Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2goresume-session: client 10.20.60.62 has successfully resumed session with ID bwalsh-72-1507827821_stDXFCE_dp32 Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2gofeature: x2gofeature called with options: X2GO_DESKTOPSHARING Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: x2gosetkeyboard called with options: bwalsh-72-1507827821_stDXFCE_dp32 Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/share/x2go/x2gofeature.d/x2goserver.features: x2goserver.features called with options: X2GO_DESKTOPSHARING Oct 12 18:15:04 bfs-dl360g7-26-xm1 /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features: x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING Oct 12 18:15:05 bfs-dl360g7-26-xm1 /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Oct 12 18:15:05 bfs-dl360g7-26-xm1 /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Oct 12 18:15:05 bfs-dl360g7-26-xm1 /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: bwalsh-72-1507827821_stDXFCE_dp32 post-resume Oct 12 18:15:05 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:06 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:07 bfs-dl360g7-26-xm1 /usr/bin/x2gomountdirs[13063]: x2gomountdirs has been called with options: dir bwalsh-72-1507827821_stDXFCE_dp32 bwalsh /users/bwalsh/.x2go/ssh/key.q14080 /cygdrive/C/Users/bwalsh/X2GO~1/S-82CD~1/spool__PRINT_SPOOL___REVERSESSH_PORT__46527 Oct 12 18:15:07 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:09 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:10 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:11 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Waiting for /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard to appear Oct 12 18:15:12 bfs-dl360g7-26-xm1 /usr/bin/x2gosetkeyboard: Setting X keyboard according to /users/bwalsh/.x2go/C-bwalsh-72-1507827821_stDXFCE_dp32/keyboard

3 2

Re: [X2Go-User] x2go fails with tcsh
by Mihai Moldovan 11 Oct '17

11 Oct '17

On 10/09/2017 12:44 PM, Frank Steiner wrote: > I was able to solve this. When I looked into the code, I saw that you > already to use "bash -c '...'" for all commands, so quoting shouldn't be > an issue. I really think it can get problematic easily, for instance with nested single quotes, that require special handling that differs from shell to shell - same thing for double quotes. Looks like you weren't hit by that issue, though. :) > But as the error message for tcsh was about > Warning: Protocol mismatch or no X authentication data. > I started looking at xauth and found an interesting difference between > bash and tcsh as login shell. > > For bash, these entries are added by x2gostartagent: > > myhost/unix:59 MIT-MAGIC-COOKIE-1 e938deb788659f0bf8c99069d199aff6 > myhost.ifi.lmu.de:59 MIT-MAGIC-COOKIE-1 e938deb788659f0bf8c99069d199aff6 > myhost.ifi.lmu.de:59 MIT-MAGIC-COOKIE-1 e938deb788659f0bf8c99069d199aff6 I knew that we're adding two entries, but it didn't come across that this might be the issue. Great debugging! Thanks. What feels odd is that there are three entries, two of which are equal. I'm not sure where the third one is coming from - in a quick test, I only see two entries on one of my sessions. Might be related to nxproxy adding another entry via xauth as well, but it still feels odd. Especially given that the two xauth calls in x2gostartagent both use ${HOSTNAME}, if ${HOSTNAME} is only "myhost", there should only be entries for myhost/unix:DISPLAY and myhost:DISPLAY. > For tcsh, I got those: > myhost.ifi.lmu.de/unix:58 MIT-MAGIC-COOKIE-1 7212fb8aa466de75ea0224a4d010f5e4 > myhost.ifi.lmu.de:58 MIT-MAGIC-COOKIE-1 7212fb8aa466de75ea0224a4d010f5e4 > myhost.ifi.lmu.de:58 MIT-MAGIC-COOKIE-1 7212fb8aa466de75ea0224a4d010f5e4 > > And that's the point! For some reason, x2go needs the cookie for > display "myhost/unix" at some point and "myhost.ifi.lmu.de/unix" > doesn't suffice. > > Indeed, when I wrote a little bash script > > #!/bin/bash > echo $HOSTNAME > > and called it with "ssh myhost bash -c './testscript'", it echoed > "myhost" with login shell bash, and "myhost.ifi.lmu.de" with > login shell tcsh. That's very interesting. bash seems to automatically populate HOSTNAME according to its man page, but the tcsh man page doesn't mention HOSTNAME at all -- only HOST, which is populated automatically by the gethostname() libc call and (on my system) returns the short hostname. I guess HOST and HOSTNAME might be the shell equivalents. It gets worse, though. I tested this on OS X, which is a BSD-like system. On this system, tcsh's HOST and bash's HOSTNAME values were the same again, BUT both included the domain name (and, incidentally, the 'hostname' program's default behavior is to print the FQDN hostname, which corresponds to the hostname returned by gethostname().) This may not sound interesting at first, because OS X is not an X2Go Server target, but according to the hostname man pages on FreeBSD, this matches this system's behavior (and it would be nice to eventually support *BSD as well at some point in time, even though that's not possible currently.) Luckily, all of them support the -s flag to hostname, so I'll just make use of it. > I'm not yet sure where this difference comes from, if it's deep inside > bash and tcsh or in some server-wide login scripts from SuSE (it > was not in the users dotfiles, we even removed them all). Whatever sets it, it's not tcsh itself. Likely some global startup script. Care to grep -R HOSTNAME /etc? The problem at hand really is that something sets and exports HOSTNAME. Since this variable is then defined in the environment, bash won't touch it. Clearly x2gostartagent uses bash (even if called from a tcsh shell) - but it inherits the exported HOSTNAME value and stuff goes boom. In my opinion, that's a bug that the distro should take care of. IMHO, the global startup scripts can set HOSTNAME, but shouldn't export this variable to the environment. > Anwyay, I added "setenv HOSTNAME `uname -n`" to my .cshrc and: > x2go works :-) Better use hostname -s. > To make that work for all our users I added > HOSTNAME=${HOSTNAME%%.*} > into x2gostartagent which doesn't harm if HOSTNAME is already > without the domain. So maybe you could add this to the next > release to help people running into the same issue. I'll fix up the server script. Mihai

2 2

x2goclient MacOS
by Robert Dinse 11 Oct '17

11 Oct '17

x2go-client versions 4.1.0.0 and 4.1.1.0 both core dump under MacOS X 10.7.5 (Lion). 4.0.0.1 does not but also will not login to a non-root account on Ubuntu server. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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.

2 2

x2go fails with tcsh
by Frank Steiner 09 Oct '17

09 Oct '17

Hi, we just tried to x2go for the first time (client 4.0.5.2 server 4.0.1 on SLED 12). It works fine for users with bash as login shell on the server side, but fails for those with tcsh. According to http://blog.x2go.org/index.php/2012/07/26/x2go-sessions-startups-for-users-… this should have been fixed a while ago, but it seems to have returned. I couldn't see any difference neither in the server log (debug level) nor in the output of "x2goclient --debug". The clients are identical until the line x2go-DEBUG-../src/onmainwindow.cpp:6014> Proxy wrote on stderr: "Session: Session started at 'Fri Oct 6 16:43:09 2017'. and then the tcsh instance exits with Warning: Protocol mismatch or no X authentication data. while the bash version continues with x2go-DEBUG-../src/onmainwindow.cpp:6014> Proxy wrote on stderr: "Info: Established X server connection. The server logs are identical until the line 2017-10-06T16:43:09.173981+02:00 knuth /usr/lib/x2go/x2gocreatesession[21667]: db_createsession called, session ID: fst-76-1507300986_stDmwm_dp24, cookie: 7b94de4d7f6bdbcda01a3dc547c42f66, client: xx:xx:xx:xx, pid: 21620, graphics port: 35760, sound port: 35761, file sharing port: 35762 and then the tcsh instance exits with 2017-10-06T16:43:15.007175+02:00 knuth sshd[21228]: pam_unix(sshd:session): session closed for user fst 2017-10-06T16:43:15.011998+02:00 knuth systemd-logind[9940]: Removed session 59. Is this problem known already? Sth. I could try to solve it? We wouldn't like to force all our users to switch away from their tcsh... cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 5

X2Go for non-bash users
by Marlin Whitaker 07 Oct '17

07 Oct '17

We have found that a user whose default shell is tcsh is affected by bash startup files when running X2Go. I assume this because x2go runs under the bash script x2goruncommand and inherits its environment. Is this correct? Is there any way around this problem? Thanks. -- Marlin

1 1

Connect Time
by Robert Dinse 06 Oct '17

06 Oct '17

Just for drill, I timed the amount of time it took to connect using my 2005 vintage Mac Pro 1,1, a whole of 5 seconds. -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- 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

ttyname failed error
by Joshua Alexander 05 Oct '17

05 Oct '17

Hello all, I'm trying to get x2go set up on CentOS 6. When I try to connect the client says "Connection failed. megs: ttyname failed. Invalid argument megs: ttyname failed: Invalid argument"... any ideas how to troubleshoot? Thanks, Josh

2 2

Re: [X2Go-User] Incomplete redrawing,of screen
by Ulrich Sibiller 04 Oct '17

04 Oct '17

What window manager are you using on the client? Uli Vom Smartphone gesendet. ----- Ursprüngliche Nachricht ----- Von: "K. Reinhold Trier" <R.Trier(a)it-jobst.de> Gesendet: ‎04.‎10.‎2017 19:03 An: "Ulrich Sibiller" <uli42(a)gmx.de> Betreff: Re: [X2Go-User] Incomplete redrawing,of screen Am 03.10.2017 um 17:37 schrieb Ulrich Sibiller: >> OK, but nevertheless I would like to know what I can do about it. For sure >> it's not a software-problem. I have an automated installation script which >> installs thick clients with the same software on different hardware. The >> installation runs fine e.g. on a virtual box on my workstation. And it runs >> also fine on a ZBOX when I use the VGA connection. Is there anybody who has >> solved the problem (maybe by changing parameters for the HDMI-Connection) or >> is the solution simply to buy more expensive hardware? > Well, some Ubuntu bug reports suggest activating "Intel tearfree mode" > for your hardware - however, I don't know what that is or if it yould > help here. Thank you, I'll try that when I find the time to do it >>> What Desktop Environment are you using? Does the problem happen with >>> other Desktop Environments, too? Does it show in singe application >>> mode? >> If you mean by single application mode that an application uses full screen: it's not shown in that case > No, I mean that you connect to the x2goserver and only run a single > application that is shown on your display just like any local software > would. You can activate that by going to the session setting in > x2goclient, first tab, last row and select "Application" instead of > "XFCE" or "KDE" or whatever. I tried it with Firefox. The error does not happen in this case - anyhow it happens only when window frames are crossing. But I had a different difficulty: the menus in the first line didn't work. When clicking on them, only a short flash appeared and disappeared. I was not able to leave the program and had to restart the box. Reinhold

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user October 2017