x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Bug#1162: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mihai Moldovan 14 Sep '17

14 Sep '17

tag #1162 pending fixed #1162 4.1.0.1 thanks Hello, X2Go issue #1162 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=0445179 The issue will most likely be fixed in src:x2goclient (4.1.0.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 0445179feb2dffddb80a38b19b085fdfb9b950ac Author: Seth Galitzer <sgsax(a)ksu.edu> Date: Wed Mar 22 03:00:39 2017 +0100 {src/{help.cpp,onmainwindow.{cpp,h}},man/man1/x2goclient.1}: add new --branding option that replaces the seal logo. Fixes: #1162. diff --git a/debian/changelog b/debian/changelog index edb2a45..71b5d28 100644 --- a/debian/changelog +++ b/debian/changelog @@ -16,6 +16,8 @@ x2goclient (4.1.0.1-0x2go1) UNRELEASED; urgency=medium * New upstream version (4.1.0.1): - src/help.cpp: add documentation for the --background option. Part of #1162. + - {src/{help.cpp,onmainwindow.{cpp,h}},man/man1/x2goclient.1}: add new + --branding option that replaces the seal logo. Fixes: #1162. -- X2Go Release Manager <git-admin(a)x2go.org> Wed, 22 Feb 2017 07:13:10 +0100

2 1

Qt 4 to Qt 5
by rgregory 12 Sep '17

12 Sep '17

Hi All: Stefan asked if I would be willing to help porting some Qt4 projects (x2gclient and X2GoDesktopSharing) to Qt5. He gave me links to the git repositories for these two projects which I have downloaded and have build under Qt 5.9.1. There were only minimal changes to the DesktopSharing program and virtually no changes to the client system at all. So any way I've got a clean build of both. I have no idea of your testing regimes or code submission guidelines, so I'd appreciate someone letting me know what's next. Any ways, I'm glad to help. -rick -- Rick Gregory rgregory(a)gbgsoft.com www.gbgsoft.com 647-483-3488 800-413-3691

3 5

Bug#1204: User can login but cannot open any Folder/File
by Gutierrez, Carlos (NKI) 11 Sep '17

11 Sep '17

Package: x2goserver Version: 4.0.5.0 Hello, We have an ubuntu 16.04 server with x2go server installed. It works well on ALL of the users except one. She can login, but all her folder and files are NON responsive, you click to open them and nothing happens. Screen is Not Frozen either, you can move through the interface, just nothing opens. Any help will be greatly appreciated. Thank you. Carlos

1 0

Bug#1203: unknown dialog type make x2goclient crash
by Ulrich Sibiller 09 Sep '17

09 Sep '17

Package: x2goclient Version: 4.1.0.1-0~1586~ubuntu14.04.1 $ x2goclient --dialog something x2go-INFO-4> "Translator: :/i18n/x2goclient_de_de found." x2go-INFO-4> "Übersetzung: :/i18n/qt_de_de gefunden." Speicherzugriffsfehler (Speicherabzug geschrieben)

1 0

Bug#1200: Environment variables not set
by Bruno CAPELETO 05 Sep '17

05 Sep '17

Package: <x2goserver> Version: <4.0.1.20-0x2go1+git20170412.1125+9.main.1> # uname -a Linux mtcie1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u1 (2017-06-18) x86_64 GNU/Linux The below bugs are most probably related to each other, that's why I open one case for all of them. The issues are the following : I want to use the French software Laurux, which is based on Gambas interpreter, via a x2go session running on a Debian 9 server running LXDE (same issues seen on an Ubuntu server, x2goserver version = 4.0.1.20-0~1125~ubuntu14.04.1).. As a prerequisite, the software is installed on the server and runs well on a local session. 1. Whatever the client (Windows or Linux 4.0.3.1-4), the local environment variables are not set properly and the software - which needs French localization - crashes. That could be "solved" the following way : /etc/x2go/Xsession : ... LANG=fr LC_ALL=fr_FR.UTF-8 export LANG export LC_ALL ... That seems to be a revival of older bugs, but it is definitely still here. 2. At the start of a new session, one gets a windows with an error message "No session for pid ..." ; that bug has already been reported several times in x2go bug tracking and marked as solved. Actually it is not on my brand new system. 3. The single application mode does not work with some of the applications, including that Laurux / Gambas. For example it works with /usr/bin/leafpad, but /usr/bin/libreoffice makes the x2go session crash. 4. The mouse double clic does not work in a x2go session, but only - within the Gambas software (works well for example when launching an application) and only - when the x2go client is running in a Windows environment (no problem when client in a Linux environment) Many thanks in advance for any support, Bruno

5 21

Bug#1201: Info received (Bug#1201: Acknowledgement (Black window with KDE5 plasma))
by Klaus Fuerstberger 03 Sep '17

03 Sep '17

I tested an KDE Neon LTS 5.8 (based on Ubuntu xenial) and KDE Neon 5.9 (based on Ubuntu zesty) on my system. With both distributions, nouveau and mesa glx is running fine. Also connecting with x2go to an x2goserver installed is no problem. After compiling and installing the mentioned latest NVIDIA driver, x2go fails again to launch KDE plasma. Klaus

2 3

Bug#1202: kex error : no match for method mac algo client->server: server [hmac-sha2-256, hmac-sha2-512], client [hmac-sha1]
by Mihai Moldovan 01 Sep '17

01 Sep '17

Adding back the X2Go bugtracker, since this is valuable information for anyone that might hit this issue. On 09/01/2017 08:15 AM, J. M. van Bilsen wrote: > that would be sufficient to tackle the problem. You are right I have to > check if the package came from the mint or youre dist. Don worry I will > be testing both but not this week. > > The reason I am looking for x2go is that we do not want to use other > methods of remote connect. I'm happy to hear this. :) I still don't feel good just closing bug reports without any work carried out. More information: Linux Mint 18.1 seems to be based upon Ubuntu 16.04, and this edition has x2goclient 4.0.5.1-1 available (exactly), so this seems to be a hit. You're using very likely this version. So, now that we have this, I'm pretty sure you're also on libssh 0.6.3-4.3, which is naturally based upon libssh 0.6.3. The corresponding commit that introduced the SHA2-based MAC algorithms was 262c82ac0661bb0be46477006ed366e401c1620f (in libssh's source code repository.) This commit first made it into libssh 0.7.0. Older libssh versions do not include it and thus do not support SHA2-based MAC algorithms. Given that Ubuntu 16.04 only ships libssh 0.6.3, that explains your trouble. You basically have two options: either report this to Linux Mint and hope they will update the update the libssh package for you and rebuild every package that depends on it (including x2goclient), or build your own versions. The first one is not likely to be successful, though I do not know Mint's update philosophy. Debian and Ubuntu typically don't do such huge upgrades within a released version line. If necessary, changes are backported to the older version - but for libssh that might turn out to be quite complicated and not worth the effort. Mint might be different, so it might be worth a shot to try. The second one requires quite a lot of effort on your side, including staying up to date and deploying self-modified packages. Mihai

1 0

Bug#966: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mihai Moldovan 01 Sep '17

01 Sep '17

tag #966 pending fixed #966 4.1.0.1 thanks Hello, X2Go issue #966 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ad62687 The issue will most likely be fixed in src:x2goclient (4.1.0.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit ad6268711062cbabbe0ec67d67d1f0df38b43217 Author: Mihai Moldovan <ionic(a)ionic.de> Date: Fri Sep 1 08:32:14 2017 +0200 src/sshmasterconnection: ignore "garbage", but require at least one line to start with a known challenge auth prompt. Fixes: #966. diff --git a/debian/changelog b/debian/changelog index 0b11622..9ed36f0 100644 --- a/debian/changelog +++ b/debian/changelog @@ -182,6 +182,8 @@ x2goclient (4.1.0.1-0x2go1) UNRELEASED; urgency=medium effect on this behavior, so removing it again. - Makefile: add comment explaining why we need to do this in the first place and why it's so complicated. + - src/sshmasterconnection: ignore "garbage", but require at least one line + to start with a known challenge auth prompt. Fixes: #966. * x2goclient.spec: - Respect %{optflags} and pass QMAKE_STRIP=: to fix missing debug info issues.

2 1

Bug#966: Banner issue update
by Cherry, Andrew J. 01 Sep '17

01 Sep '17

I've done some additional testing, prompted by your mention of the banner being configured using the Banner option in sshd_config. It turns out we are *not* using the sshd config option -- instead, we are displaying the banner using the pam_echo module, configured with the following line in /etc/pam.d/sshd: auth optional pam_echo.so file=/etc/issue.net What I've found so far is that the same /etc/issue.net plays nice with x2go when configured via the Banner option, but causes an auth failure when configured using pam_echo.so. I'm going to do some more digging to see if I can figure out what the difference is. Oddly, if I cut/paste the output from the OpenSSH client (on Linux) up to and including the Password: prompt, and do a diff between the two, they are byte-for-byte identical. By the way, the reason we use pam_echo.so instead of the Banner option is because we actually have two banners -- /etc/issue/net for the standard security boilerplate which is always displayed, and /etc/issue.alcf which is normally empty but is populated with information during our scheduled maintenance windows when logins are disabled. However, I've confirmed that the problem still occurs even if I configure pam_echo.so to only display /etc/issue.net -Andrew

2 3

Bug#1202: kex error : no match for method mac algo client->server: server [hmac-sha2-256, hmac-sha2-512], client [hmac-sha1]
by J. M. van Bilsen 01 Sep '17

01 Sep '17

Package: x2goclient Version: 4.0.5.1-1 Complete system info : $ which x2goclient /usr/bin/x2goclient $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=18.1 DISTRIB_CODENAME=serena DISTRIB_DESCRIPTION="Linux Mint 18.1 Serena" $ dpkg --list | grep x2goclient ii x2goclient 4.0.5.1 -1 amd64 X2Go Client application (Qt4) WARNING my assumption is this problem will be on all x2goclient programs. After change of the security settings on sshd we cannot connect using x2go. Using portforwarding ssh -L 9999:localhost:22 someremotehost then letting x2goclient connect to localhost port 9999 works. Settings in sshd_config MACs hmac-sha2-256,hmac-sha2-512 When connecting we get error message : kex error : no match for method mac algo client->server: server [hmac- sha2-256,hmac-sha2-512], client [hmac-sha1] My assumption is client is configured using hmac-sha1 as default Problem does not surface using ssh or ssh port forwarding. Problem can be easy reproduced using raspberry with mathe and MACs hmac-sha2-256,hmac-sha2-512 in sshd_config Problem surface also with different ssh proxy servers having the MACs setting. As stated before normal connection on ssh or using port forwarding no problem.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev