x2go-user December 2013

x2go-user@lists.x2go.org

21 participants
28 discussions

Folder sharing does not work with x2goclient
by Emanuele Rocca 27 Nov '14

27 Nov '14

Hi list, While folder sharing works fine using pyhoca-cli, it does not work at all with x2goclient. This is what sshd says on the client side when trying to "share" a folder from the gui: May 8 13:55:43 uranus sshd[23908]: Connection from 127.0.0.1 port 51821 May 8 13:55:43 uranus sshd[23908]: Connection closed by 127.0.0.1 [preauth] mount's output on the server side does not show anything interesting. I am running Ubuntu precise (12.04), both on the client and the server. Do you have any hints on how to debug this further? Installed packages: ii cups-x2go 3.0.0.3-0~54~oneiric1 X2GO printer for CUPS ii python-x2go 0.1.1.9-0-0~612~oneiric1 Python module for X2go client support ii x2goagent 2:3.5.0.11-0~220~oneiric1 X2Go agent ii x2goclient 3.99.0.6-0~144~oneiric1 X2Go Client application (Qt4) ii x2gognomebindings 2.0.1.4-0~53~oneiric1 Description: x2gognomebindings (GNOME mimetypes for X2go) ii x2goserver 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts ii x2goserver-compat 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (backwards compatitbity to old client versions) ii x2goserver-extensions 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (extensions) ii x2goserver-fmbindings 3.1.0.0-0~477~oneiric1 Generic (freedesktop-based) file manager bindings for X2Go ii x2goserver-printing 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (printing) ii x2goserver-pyhoca 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (add-ons for pyhoca client) ii x2goserver-xsession 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (Xsession runner) ii pyhoca-cli 0.1.4.2-0~108~oneiric1 A command line X2go client written in Python ii pyhoca-gui 0.1.0.10-0~487~oneiric1 A graphical X2go client written in (wx)Python ii x2goserver-pyhoca 3.1.0.0-0~477~oneiric1 X2Go server daemon scripts (add-ons for pyhoca client) Conf file: [20120503160857309] speed=3 pack=16m-jpeg quality=9 fstunnel=true export="/media:1;" iconvto=UTF-8 iconvfrom=ISO8859-1 useiconv=false fullscreen=false width=1024 multidisp=false display=1 height=768 dpi=96 setdpi=false xinerama=false usekbd=true layout=us type=pc105/us sound=true soundsystem=pulse startsoundsystem=true soundtunnel=true defsndport=true sndport=4713 print=true name=xxx icon=:icons/128x128/x2gosession.png host=host.example.org user=username key= sshport=22 autologin=false krblogin=false rootless=false applications=WWWBROWSER, MAILCLIENT, OFFICE, TERMINAL, gnome-session-fallback command=gnome-session-fallback rdpoptions= rdpserver= xdmcpserver=localhost

5 11

Mac OSX and keyboard
by Paul van der Vlis 02 Sep '14

02 Sep '14

Hello, Is X2goclient working on Mac OSX? I read some messages that there are keyboard problems. Not sure they are gone. Here is such a message, with a link to another message: http://www.mail-archive.com/x2go-user@lists.berlios.de/msg00632.html When the problem is fixed, is this also the case for the Lenny version of X2go? (I have a customer with Macs who does not want to upgrade because the office will be closed in a few months.) With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl

11 20

x2go server for windows
by Dmitri Chebotarov 27 Mar '14

27 Mar '14

Hello, I¹m looking for info on x2go server for windows. Is there a package available for XP/7/8/Server? I was in a NetApp class last week. We did our labs in a VM environment and used x2go to access RedHat and Windows 2012 VM, which worked nicely. I would like to try to implement x2go in my environment. I support a Virtual Computer Lab (VCL) at GMU and x2go looks very interesting as access method. Currently we use RDP protocol to access VMs - Windows and Linux (xRDP). -- Thank you, Dmitri Chebotarov VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 | Fax: (703) 993-3404

7 8

Nightly builds for Fedora and EPEL
by Mike Gabriel 21 Feb '14

21 Feb '14

Hi all, thanks to one of our project sponsorers, IMMOBILIEN SCOUT 24, we will be able to provide nightly built RPM packages and RPM release packages directly from upstream in the (near) future. Our RPM packages currently build against various Fedora (18-21 atm) versions [1] and against EPEL (5+6) [2]. The nightly built RPMs still need some work here and there (QA work is still in process), but we are happy to share the test load. For those of you who start playing with our RPM builds: please use our X2Go bug tracking system to report RPM bugs [3]. Please tag your bug report with ''Tag: rpm-packages'', if you think the bug exists in the RPM package itself and not so much in the X2Go code. Don't report to your distro as the distro maintainers cannot help you when playing with package provided by X2Go upstream. We will do our best to support the Fedora packaging team of X2Go to merge our (as we think) improvements into the .spec (i.e. RPM packaging) files. Greets, Mike [1] http://wiki.x2go.org/doku.php/wiki:development:nightly-builds#nightly_build… [2] http://wiki.x2go.org/doku.php/wiki:development:nightly-builds#nightly_build… [3] http://wiki.x2go.org/doku.php/wiki:bugs -- 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…

2 2

Keyboard mapping issues with Windows client
by Roderick Johnstone 09 Jan '14

09 Jan '14

@Mike Gabriel I have broken this out of the thread "[X2Go-User] [newb] display size ignored". I wanted to clarify the keyboard mapping issues that I'm seeing. I need, at least, to connect to a KDE session from a Windows client with a UK keyboard and from a UK model Mac laptop correctly. When connecting a Windows KDE session I invariably get a US keyboard layout. I'm sorry this post is so long, but its all a bit complicated... My early tests were a bit confusing, I think because the system I'm connecting to has a system-wide UK keyboard setting. So, sometimes tests with xterm seem to be working when its just getting a default. In order to resolve this ambiguity, I've been testing from my Windows laptop with the keyboard set to French mapping which is not a default for the system I'm connecting to or for kde. I've been testing from Windows client 4.01.2 and server package x2goserver-4.0.1.9-2.fc20.x86_64 from the Fedora 20 repo. When I start a single application session (/usr/bin/xterm) the only setup that seems to get the correct French keyboard mappings is when I explicitly set the Keyboard layout to fr and the Keyboard model to pc105/fr. Choosing either auto for the layout or ticking the checkbox "Keep current keyboard settings" does not result in a French layout. (In both cases I get a UK keyboard layout which is the system default for the system I'm connecting to). Having established how to get the correct keyboard mapping in a plain xterm I try a kde session with the same client keyboard settings; now I get a US keyboard layout, which I suspect is a kde default. I'm doing a setxkbmap -print >& /tmp/temp.lis very early on in /usr/bin/startkde and I can see that at that point a French keyboard is set. However, by the time the KDE session is running and I can type into a konsole I have a US key layout. (Logging in to a KDE session at the console on this system gets me a UK keyboard as expected). I thought that maybe KDE is setting its own US keyboard map (or just defaulting to US) so I took some advice from the Fedora KDE list on how to stop KDE setting its own keyboard map. However, that had no effect. I still get the US keyboard map. So, I think there are at least two problems: 1) For the simple xterm session setting the layout to "auto" or checking the box "Keep current keyboard settings" is not working. 2) KDE is possibly overriding the already set keyboard map with a US layout. Is it likely that the nightly Windows client builds will address both these issues or perhaps just 1)? Can you confirm that its possible (for you) to get a KDE session with the correct keyboard mapping that is not the default? Thanks Roderick

2 2

wmctrl problems
by Jean-Francois Dagenais 07 Jan '14

07 Jan '14

Hi all, Running x2go server on ubuntu (12.04), and my terminal is a mac running XQuartz (with quartz-wm) and the Qt x2go client. I used the Published apps rootless and spawn a few windows from the server. Things run pretty smoothly and Im happy with the performance. The thing that hurts is related to window management. Heres a relevant output: $ echo $DISPLAY :50 $ wmctrl -l Cannot get client list properties. (_NET_CLIENT_LIST or _WIN_CLIENT_LIST) $ wmctrl -m Cannot get window manager info properties. (_NET_SUPPORTING_WM_CHECK or _WIN_SUPPORTING_WM_CHECK) Whereas if I run the same commands natively on the mac, XQuartz responds correctly to wmctrl. So the problem affects pretty much all tools related to window management I tried. I am no X11 expert, but I am a developer and very familiar with linux systems. Right now I just need a few pointers, any thoughts? Thanks in advance! /jfd

2 4

pxe: "Access denied: Authentication that can continue...."
by Luciano Gabriel Andino 06 Jan '14

06 Jan '14

Hi there)) I am trying to configure x2go/pxe and this is my first question. I did a clientsession in server and scp transfer to pxe server. PXE server is ready, client booted but I can't login cause this message appears (in client): "Access denied: Authentication that can continue...." while it was possible to login from a linux box. The idea is that a any user can access to his account from anyclient. how can I store this publickeys? thanks in advance, -- Saludos!! Luciano Andino GNU/Linux user #185103 Santa Fe - Argentina -----------------------------------------------

2 3

No sound in X2Go TCE (ATTN: @Mike)
by Stefan Baur 06 Jan '14

06 Jan '14

Hi list, I managed to get X2Go TCE running, by following the instructions on http://wiki.x2go.org/doku.php/wiki:advanced:tce:install Everything works fine, except for the sound. All my thin clients don't emit sound. Browsing through the list archive, I found a post from back in October where Mike said it happens due to a permission problem, and he posted two links to GIT where he had patched this (the first patch introduced a typo, which was fixed in the second patch). So I decided to give it a go and simply copy the x2gothinclient_create script from GIT over the one I already had on disk. Sadly, this just made things worse: after removing the chroot directory and rebuilding it with the new version of x2gothinclient_create, neither keyboard nor mouse work, so I can't even log in. Reverting back to the old script, rm'ing the chroot directory and running x2gothinclient_create again fixed that issue - but I still have no sound. Any hints? Which log or config file(s) should I post? -Stefan

2 3

[newb] display size ignored
by Neal Becker 29 Dec '13

29 Dec '13

Just trying x2go on fedora 20. Starting a kde session, the display size is ignored. It takes the entire display. xdpyinfo reports: screen #0: dimensions: 1920x1200 pixels (423x264 millimeters) resolution: 115x115 dots per inch The physical screen is (local X): screen #0: dimensions: 1680x1050 pixels (371x232 millimeters) resolution: 115x115 dots per inch

4 13

[newb] fedora 20 gnome won't start
by Neal Becker 28 Dec '13

28 Dec '13

kde works, but gnome (or unity) just gives me a message about 'something's wrong'

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user December 2013