x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

pyhoca-gui systray icon no showing on Ubuntu 17.10 or 18.04 with Gnome
by brian mullan 09 Feb '18

09 Feb '18

I haven't used pyhoca-gui for a while but decided to try it again on both my Ubuntu 17.10 and Ubuntu 18.04 systems. Both of those are using Gnome. I thought I remembered under Unity that Pyhoca-GUI would put its Icon in the top systray. But in 17.10 and 18.04 Gnome I don't see it any longer. Is there a way to enable it in the systray for Gnome? Brian

2 1

Upcoming Deprecation of (Almost) EOL Distributions
by Mihai Moldovan 07 Feb '18

07 Feb '18

Hi In order to lower resource stress when building packages, I plan to deprecate support for distributions that have (almost) reached End Of Life on December 31th 2017. This includes the following distro versions: - Debian: o 7.0 "wheezy" - Fedora o 23 o 24 o 25 - OpenSuSE o 13.1 o 13.2 o 42.1 Ubuntu builds are ceased automatically after upstream deprecation. After deprecation, no new builds will be published and existing builds will be moved to the archive repositories to discourage users from installing unmaintained software. Mihai

1 1

Bug#1250: X2Go Doesn't Set Remote Environment
by Matthew Rubenstein 06 Feb '18

06 Feb '18

Package: x2goclient, x2gostartagent Version: 4.0.5.1 Severity: wishlist Hello. x2goclient and x2gostartagent (and the rest of X2Go) use libssh, but do not use either the local ssh ~/.ssh/environment or the remote sshd ~/.ssh/rc . Neither does X2Go use its own corresponding config files for the remote environment. X2Go will use the remote ~/.bashrc when X2Go starts the remote bash shell, but if that .bashrc quits upon detecting a non-interactive bash session (such as the ones X2Go creates) then those .bashrc configs aren't applied to the X2Go session. That non-interactive=quit logic is standard practice, and indeed Ubuntu's /etc/skel/.bashrc includes it (among many other distros). This lack of X2Go session configuration can cause remote client applications to fail. Especially where the X2Go 'Session type' = 'Single application', where the environment X2Go is using was set per- user at (interactive) login prior to using X2Go. The hackaround is to create a per-user wrapper that sets the environment (but can't just source ~/.bashrc for the non-interactive session). This is unmanageable especially for multiple users and multiple local/remote hosts, and makes setting the remote environment complex and time consuming (compared to the basic X2Go invocation configuration). It also requires the user have access to the remote filesystem, probably to a remote shell, and to use it to write freeform wrappers. The best support for setting the environment would use a local ~/.x2gorc that can set the remote environment with bash syntax, overridden by a GUI in x2goclient, overridden by a remote ~/.x2gorc , with perhaps system defaults local and remote in /etc/x2go/.x2gorc . The X2Go config files/GUI could include an option to use their ssh(d)equivalents, ie. [. ~/.ssh/environment].

1 0

Bug#1249: numlock not working on win7 client and ubuntu 14.04 LTS server and XFCE desktop
by n.vanvliet＠utwente.nl 05 Feb '18

05 Feb '18

Package: x2goserver Version: 4.0.1.22 Numlock key on the Windows clients is not functional. My coworkers informed me of this. I am not entirely sure it's a server problem. 1. My Window versions: Windows 7 Enterprice service pack 1. 2. My Windows x2go client version is: 4.1.0.0 3. Session is set for XFCE 4. Server OS is Ubuntu 14.04.5 LTS 5. Servers x2go packages are: x2goagent/trusty,now 2:3.5.0.33-0~710~ubuntu14.04.1 all [installed,automatic] x2goserver/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 amd64 [installed] x2goserver-extensions/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 all [installed,automatic] x2goserver-xsession/trusty,now 4.0.1.22-0~1197~ubuntu14.04.1 all [installed] 6. There are several xfce4 packages installed on the server. 7. I made no changes to the configuration on the server. Please let me know if you need further information. Regards, Nico van Vliet

1 0

Re: [X2Go-Dev] Bug#1247: Can't get full screen on Raspberry PI (Blake McBride)
by Rob Janssen 29 Jan '18

29 Jan '18

| I have a Raspberry PI running their latest OS (9.1 Stretch) | I can't seem to get full screen. Note I have the same problem with Windows. Is fullscreen still working for anyone? Rob

1 0

Search for a new date for the developer meetings
by Heinz-M. Graesing 29 Jan '18

29 Jan '18

Dear developers, Unfortunately, the current date on Thursday evening (CET) does not allow all participants to attend our meetings. We are therefore looking for a new possible appointment. It would be nice if you could indicate your preferences on the following wiki page: https://wiki.x2go.org/doku.php/wiki:development:planning:start Regards Heinz

1 1

Bug#1246: Can't start X Server, please check your installation)
by LANNES Pierre-Yves 28 Jan '18

28 Jan '18

A bit more info... First, I can now confirm that this bug occurs systematically, regardless of any connection attempt. I just had to start X2go client and wait for the error to pop up. Second, I have tried to use a recent vcxsrv.exe (installed separately), as the X2go built-in is 1.17.0.0-3". I tried with version 1.19.5.2". No change noticed. Hope that helps... --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus

1 0

Bug#1235: SSH daemon could not be started
by Feustel, Thomas 27 Jan '18

27 Jan '18

Das Problem wird auf dem Windows Client dadurch ausgelöst, das bei der Installation Host-Keys vom Typ RSA für den SSH Daemon erzeugt werden. Der Server selbst versucht beim Start einer Client Verbindung aber Host-Keys vom Typ DAS einzulesen. Diese wurden früher immer erstellt, so dass bei einem Update das Problem nicht existiert. Zwei Lösungen existieren: a) DSA Host-Keys manuell oder mit einem alten Setup erstellen b) sshd.config anpassen und auf die neuen Keys bzw. Datei verweisen (nicht geteset) Mit freundlichen Grüßen Thomas Feustel

1 0

Bug#1247: Can't get full screen on Raspberry PI
by Blake McBride 26 Jan '18

26 Jan '18

Package: x2goclient Version 4.1.1.0 I have a Raspberry PI running their latest OS (9.1 Stretch) I can't seem to get full screen. If I set x2goclient to Display Fullscreen, it starts up and works fine except that it is a window on my screen (having a headline with minimize, etc. buttons). Then when I exit, it changes the config to Custom 1920x1078. In fact, I just noticed that if I select "Fullscreen" and then click "OK", when I go back in, it's changed to Custom 1920x1078. Same thing with Display Use whole display. Nothing I do will make "Fullscreen" stick. Not having any problems on my LinuxMint box.

1 0

Support SSH_AUTH_PARTIAL
by Orion Poplawski 25 Jan '18

25 Jan '18

I'm starting to take a stab at supporting SSH_AUTH_PARTIAL in x2goclient. Here's what I have at the moment. I think there still is work to be done for userAuthKeyboardInteractive() and userChallengeAuth() and userAuthWithPass(), but they would be similar to what was done for userAuthAuto and userAuthWithKey. This also requires work in libssh - see https://bugs.libssh.org/T82 -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev