x2go-user

x2go-user@lists.x2go.org

3 participants
2322 discussions

Re: [X2Go-User] SessionBroker
by Mike Gabriel 03 Jul '14

03 Jul '14

Hi Felix, On Do 03 Jul 2014 11:09:34 CEST, Felix Hosner wrote: > Super - Thanks > > invoke-rc.d x2gobroker-daemon stop > > [....] Stopping X2Go Session Broker standalone daemon: > x2gobroker-daemonstart-stop-daemon: warning: failed to kill 2160: No such > process > > failed! > > - Next step > > x2gobroker-daemon-debug > > Traceback (most recent call last): > > File "/usr/bin/x2gobroker", line 90, in <module> > > import x2gobroker.defaults > > File "/usr/lib/python2.7/dist-packages/x2gobroker/defaults.py", line 178, > in <module> > > X2GOBROKER_HOSTNAME = socket.gethostbyaddr(socket.gethostname())[0] > > socket.gaierror: [Errno -2] Name or service not known Make sure that your hostname resolves to a valid IP(v4 or v6) address. Use /etc/hostname if you don't have a proper DNS setup in your lab. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

SessionBroker
by Felix Hosner 03 Jul '14

03 Jul '14

Hi there Questions about the Session Broker: Background: simple Session Broker Daemon x2go Server Ubuntu 14:04 - can be called directly from the client (Terminal works) 1st Question x2gobroker-sessionprofiles.conf if I editable this file, I need to restart a service? 2st Question x2goclient - broker-url = http://10.255.120.23:8080/plain/inifile/ / etc/x2go/x2gobroker.conf as standard out of the box SessionBroker Config: [pool-A server-A] user = visor host = 10.255.120.23:2222 name = GNOME - pool-A (srv-A) command = GNOME rootless = false acl-groups-allow = gnome-users, admins acl-groups-deny = ALL acl-clients deny = ALL acl-clients allow = ALL acl-any-order = deny-allow broker-session-autologin = true What is still missing the SessionBorker flies Thank you for your feedback Felix -- *Notabene: * Die Zukunft soll man nicht voraussehen wollen, sondern möglich machen. Antoine de Saint Exupéry (1900-44), frz. Flieger u. Schriftsteller *Computer Coach GmbH * 3116 Kirchdorf, Thalgutstrasse 10 Tel. 031 782 12 00 Fax 031 782 12 02 fhosner(a)computer-coach.ch www.computer-coach.ch

2 1

screenshots while suspended?
by Matt Cowan 02 Jul '14

02 Jul '14

I'm trying to create a local service which captures status screenshots of a set of monitoring system windows about once a minute. x2go seemed like it was working great to decouple the service from a physical desktop, until I suspended the connection, at which point the screenshots get wonky (mostly just grey with a little strip of actual window contents along one border, or just all grey, or ...). It works fine when x2go is iconified, just not when it's disconnected. Is this a known problem/feature? I imagined Xclients wouldn't be impacted by a session being suspended or connected? thanks. -matt

1 1

Not Working with changes in PAM
by segurah h 02 Jul '14

02 Jul '14

Hi : I was using x2go server and it worked fine until I follow this guide in order to add my linux box (the x2go server) to a Microsoft Active Directory ( https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto ) , now I can't initiate a session from x2goclient to this box but can do perfectly ssh sessions with Unix local users also mircrosoft domains users, export X display works fine. Putting x2go server in debug mode shows : Jul 1 22:04:47 x2goserver /usr/bin/x2golistsessions[17955]: x2golistsessions has been called with no option Jul 1 22:04:48 x2goserver /usr/bin/x2gostartagent: x2gostartagent called with options: 1360x740 lan 16m-jpeg-9 unix-kde-depth_24 es auto 1 D GNOME Jul 1 22:04:48 x2goserver /usr/bin/x2gostartagent: client announced itself as ,,167.134.171.87'' Jul 1 22:04:48 x2goserver /usr/bin/x2gosessionlimit[17977]: x2gosessionlimit has been called Jul 1 22:04:48 x2goserver /usr/bin/x2golistsessions[17980]: x2golistsessions has been called with options: --all-servers Jul 1 22:04:49 x2goserver /usr/lib/x2go/x2gogetdisplays[17994]: db_getdisplays called, server: x2goserver; return value: |55| |56| |57| |58| |59| |60| |61| |62| Jul 1 22:04:49 x2goserver /usr/lib/x2go/x2gogetports[18004]: db_getports called, server: x2goserver; return value: |30001| |30002| |30003| |30004| |30005| |30006| |30007| |30008| |30009| |30010| |30011| |30012| |30013| |30014| |30015| |30016| |30017| |30018| |30019| |30020| |30021| |30022| |30023| |30024| |30025| Jul 1 22:04:49 x2goserver /usr/lib/x2go/x2goinsertsession[18025]: db_insertsession called, session ID: segurah-50-1404268489_stDGNOME_dp24, server: x2goserver, session ID: segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:04:50 x2goserver /usr/lib/x2go/x2goinsertport[18037]: db_insertport called, session ID: segurah-50-1404268489_stDGNOME_dp24, server: x2goserver, SSH port: 30026 Jul 1 22:04:50 x2goserver /usr/lib/x2go/x2goinsertport[18049]: db_insertport called, session ID: segurah-50-1404268489_stDGNOME_dp24, server: x2goserver, SSH port: 30027 Jul 1 22:04:50 x2goserver /usr/lib/x2go/x2goinsertport[18061]: db_insertport called, session ID: segurah-50-1404268489_stDGNOME_dp24, server: x2goserver, SSH port: 30028 Jul 1 22:04:51 x2goserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jul 1 22:04:51 x2goserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jul 1 22:04:51 x2goserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: segurah-50-1404268489_stDGNOME_dp24 pre-start Jul 1 22:04:51 x2goserver /usr/bin/x2gostartagent: successfully started X2Go agent session with ID segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:04:51 x2goserver /usr/bin/x2gofeature: x2gofeature called with options: X2GO_RUN_EXTENSIONS Jul 1 22:04:51 x2goserver /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features: x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS Jul 1 22:04:51 x2goserver /usr/bin/x2goserver-run-extensions: x2goserver-run-extensions called with options: segurah-50-1404268489_stDGNOME_dp24 post-start Jul 1 22:04:51 x2goserver /usr/lib/x2go/x2gocreatesession[18148]: db_createsession called, session ID: segurah-50-1404268489_stDGNOME_dp24, cookie: 6206c4ecb0328f02b7672471414a213c, client: 167.134.171.87, pid: 18115, graphics port: 30026, sound port: 30027, file sharing port: 30028 Jul 1 22:05:53 x2goserver /usr/lib/x2go/x2gochangestatus[18274]: db_changestatus called, session ID: segurah-50-1404268489_stDGNOME_dp24, new status: F Jul 1 22:05:53 x2goserver /usr/sbin/x2gocleansessions[26978]: segurah-50-1404268489_stDGNOME_dp24, pid 18115 does not exist, changing status from R to F Jul 1 22:05:53 x2goserver /usr/sbin/x2gocleansessions[26978]: segurah-50-1404268489_stDGNOME_dp24: unmounting all shares Jul 1 22:05:53 x2goserver /usr/bin/x2goumount-session[18284]: x2goumount-session has been called with options: segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:05:53 x2goserver /usr/bin/x2goumount-session[18284]: db_getdisplay called, session ID: segurah-50-1404268489_stDGNOME_dp24; return value: 50 Jul 1 22:05:53 x2goserver /usr/bin/x2goumount-session[18284]: db_getmounts called, session ID: segurah-50-1404268489_stDGNOME_dp24; return value: Jul 1 22:05:59 x2goserver /usr/lib/x2go/x2golistsessions_sql[18294]: dbsys_deletemounts called, session ID: segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:05:59 x2goserver /usr/lib/x2go/x2golistsessions_sql[18294]: Purging finished session from X2Go db, session ID: segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:05:59 x2goserver /usr/sbin/x2gocleansessions[26978]: segurah-50-1404268489_stDGNOME_dp24 is blocked Jul 1 22:05:59 x2goserver /usr/sbin/x2gocleansessions[26978]: segurah-50-1404268489_stDGNOME_dp24: unmounting all shares Jul 1 22:05:59 x2goserver /usr/bin/x2goumount-session[18306]: x2goumount-session has been called with options: segurah-50-1404268489_stDGNOME_dp24 Jul 1 22:05:59 x2goserver /usr/bin/x2goumount-session[18306]: db_getdisplay called, session ID: segurah-50-1404268489_stDGNOME_dp24; return value: Jul 1 22:05:59 x2goserver /usr/bin/x2goumount-session[18306]: db_getmounts called, session ID: segurah-50-1404268489_stDGNOME_dp24; return value: Also, at the client side (x2goclient), the error is : Error: The remote NX proxy closed the connection Error: Failure negotiating the session in stage '7 Error: Wrong version or invalid session authentication cookie Session: Terminating session at ..... A popup message says : x2go -51 The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server. What do you think that can be happening? I can't understand. Any help? Best regards, Hugo

1 0

Problems staying connected
by Jon Gilbert 02 Jul '14

02 Jul '14

Every time I login it works great for a few seconds, then it just freezes up. I checked the .xsession-x2go-errors and this is what I see: ........................................................................ localuser:bitnami being added to access control list (xfwm4:25785): xfwm4-WARNING **: The display does not support the XComposite extension. (xfwm4:25785): xfwm4-WARNING **: The display does not support the XFixes extension. (xfwm4:25785): xfwm4-WARNING **: Compositing manager disabled. xfdesktop[25791]: starting up (xfce4-settings-helper:25807): xfce4-settings-helper-CRITICAL **: Your XI is too old (1.3) version 1.4 is required. (polkit-gnome-authentication-agent-1:25798): GLib-CRITICAL **: g_variant_new_string: assertion `string != NULL' failed (polkit-gnome-authentication-agent-1:25798): polkit-gnome-1-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files (xfce4-settings-helper:25807): xfce4-settings-helper-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property. ........................................................................ If anyone can help that would be great. After three solid days of trying to make x2go actually work, it still doesn't. I'm on a fresh Ubuntu 12.04.4 LTS (GNU/Linux 3.2.0-61-virtual x86_64). Starting from there I did: sudo add-apt-repository ppa:x2go/stable && sudo apt-get update then sudo apt-get install xfce4 xfce4-goodies xfce4-artwork xubuntu-icon-theme firefox x2goserver x2goserver-xsession And that's where I'm at. If there is anything else I should do to make this work that would be great to know. It usually crashes when I try to open up a folder or drag a window around. Sometimes I can't even get that far. Any help is most appreciated... thanks... Jon

1 0

problem getting x2go to work.
by Jon Gilbert 01 Jul '14

01 Jul '14

I have a server set up which is Ubuntu 12.04.4 LTS (GNU/Linux 3.2.0-64-virtual x86_64). I installed ubuntu-desktop as instructed by the x2go wiki. I also did these steps: sudo apt-get install x2goserver sudo apt-get install x2goserver-xsession sudo apt-get install sqlite3 sudo x2godbadmin --createdb I try to connect from the Mac client (tried all the versions) and it always fails. It just hangs at the screen where it's trying to connect. I set the server log level to debug and it just says: Jun 24 00:52:50 <my_ip> /usr/bin/x2golistsessions[32234]: x2golistsessions has been called with no option Jun 24 00:52:50 <my_ip> /usr/bin/x2gostartagent: x2gostartagent called with options: 800x600 isdn 256k-jpeg unix-kde-depth_32 us query 0 D gnome-flashback.sh Jun 24 00:52:50 <my_ip> /usr/bin/x2gostartagent: client announced itself as ,,173.12.186.158'' Jun 24 00:52:50 <my_ip> /usr/bin/x2gosessionlimit[32271]: x2gosessionlimit has been called Jun 24 00:52:50 <my_ip> /usr/bin/x2golistsessions[32274]: x2golistsessions has been called with options: --all-servers Jun 24 00:52:51 <my_ip> /usr/lib/x2go/x2gogetdisplays[32289]: db_getdisplays called, server: <my_ip>; return value: Jun 24 00:52:51 <my_ip> /usr/lib/x2go/x2gogetports[32298]: db_getports called, server: <my_ip>; return value: Jun 24 00:52:52 <my_ip> /usr/lib/x2go/x2gogetdisplays[32342]: db_getdisplays called, server: <my_ip>; return value: Jun 24 00:52:52 <my_ip> /usr/lib/x2go/x2gogetports[32351]: db_getports called, server: <my_ip>; return value: It repeats this over and over as the processor runs at 100% on the server, being hosed by the several x2go processes that seem to be stuck in an infinite loop. You'll notice that it runs gnome-flashback.sh in my command, that's because it doesn't work to connect the normal way either, so I tried the steps outlined in this e-mail from this list: http://lists.x2go.org/pipermail/x2go-user/2014-May/002260.html (I find it annoying that it doesn't work with Gnome 3 according to that e-mail, yet it doesn't mention this incompatibility in a conspicuous way anywhere on the x2go site.) Anyway I followed all the steps 1. through 6. in the above-linked e-mail, to no avail, because it did nothing at all towards making this work. BTW my server is on EC2. Don't know if that matters. And yes, I have Please let me know what is going wrong here and what I can do to fix this. Thanks. BTW I do have the latest version of XQuartz installed as my client, and I did set it up to accept remote connections and all that. The connection gets made no problem; the problem definitely seems to be on the server. Jon

4 14

X2Go crashes X
by James M. Pulver 30 Jun '14

30 Jun '14

When accessing a remote server from the Linux client, we are seeing for one user X errors - X2go doesn't crash...: The issue is that, after xterm window is launched, any attempt to use the keyboard in that xterm causes the xserver to die and the x2go session to terminate. This happens with emacs as well. Both tested while using the icewm-session desktop. The x2go program doesn't crash. The errors in .xsession-errors file are: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7800011 specified for 0x780000f (X2Go - 61). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7800011 specified for 0x780000f (X2Go - 71). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x740001f specified for 0x7400626 (Error). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7800011 specified for 0x780000f (X2Go - 76). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x7800011 specified for 0x780000f (X2Go - 79). And there are core files being generated... if they would help I could post this? Any ideas? -- James Pulver CLASSE Computer Group Cornell University

2 1

x2go client side printing
by Steve Bergman 29 Jun '14

29 Jun '14

Hi, I'm running the latest x2go server on Debian 7 Wheezy. I've got the x2go-printing package installed, as well as the cups-x2go package. Browsing is enabled in cupsd.conf. 'Client side printing support' is enabled in the client. And I've restarted the cups server, and logged out and back in after installing the print packages. But my printer is not appearing in MATE's list of printers. Is there something more I need to do? This is operating over a vpn, so there is no firewall involved. And sound works fine. Thanks for any assistance. Steve Bergman Oklahoma City, OK. USA

4 6

pulseaudio
by Frédéric Henry-Couannier 29 Jun '14

29 Jun '14

Dear I'm trying for the first time x2go between an RPI (thinclient) and a Mageia PC (server) and for the time being i get a horrible sound (almost impossible to understand a speach) when i read a youtube video. I have KDE on my Mageia PC and i'v readen in various web pages that there is a problem running pulseaudio on KDE, however i see many packages available for pulseaudio, many of them already installed so may be KDE-pulseaudio compatibility is an old problem which is now solved (?) So i have no idea eventually what config should i use (pulseaudio?, arts?, eds?) and what packages should be installed on the source and sink sides (pulseaudio is there and all right on both sides as far as i could check) I also guess that a firewall configuration is needed not to block the pulseaudio default port...(?) Thank you in advance for any helpful suggestion or reference to read. regards, Fred

1 0

Re: [X2Go-User] [SOLVED] Starting a session
by Klaus Jantzen 25 Jun '14

25 Jun '14

On 06/05/2014 04:56 PM, Short, Kermit wrote: > Most likely this is due to the SSH server trying to utilize a HostKey > encryption method that is not supported by X2Go. I'd recommend > commenting out any sort of ECDSA or other elliptical curve based > algorithm(/etc/ssh/sshd_config), restarting the SSH daemon, removing the > host key entry from your client's ~/.ssh/known_hosts file, and trying > again. > The main reason for my problem was that I did not generate the SSH keys consistently. The information on the X2Go web site and in the flyer I got at the CLT 2014 (which actually motivated me to try x2go) is in respect to the generation of the keys (at least for me as a first time user of x2go) not sufficient. To solve the problem I threw out all generated keys (user on server, user on remote client) and followed the description in Michael W. Lucas: SSH Mistery (ISBN 9781470069711) Now I have the various types of keys on both machines. And with the correct settings in the session profile everything works, even automatically. Thanks for your hints. KDJ.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user