x2go-dev

x2go-dev@lists.x2go.org

5403 discussions

Bug#1364: X2Go issue (in src:x2gothinclient) has been marked as pending for release
by Mike Gabriel 18 Jan '19

18 Jan '19

tag #1364 pending fixed #1364 1.5.0.1 thanks Hello, X2Go issue #1364 (src:x2gothinclient) 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=x2gothinclient.git;a=commitdiff;h=25bef95 The issue will most likely be fixed in src:x2gothinclient (1.5.0.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 25bef951bd5a3bb13c49dc45992ca594a99de656 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Fri Jan 18 13:51:39 2019 +0100 19_x2gothinclient-minidesktop.gschema.override: Explicitly use MATE-specific theming of the desktop UI. (Closes: #1364). diff --git a/debian/changelog b/debian/changelog index 1cac657..6ba6b2d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -13,6 +13,11 @@ x2gothinclient (1.5.0.1-0x2go1) UNRELEASED; urgency=medium * usbmount/x2gousbmount: - Pull (most) changes from doc:howto:tce wiki page. + [ Mike Gabriel ] + * New upstream release (1.5.0.1): + - 19_x2gothinclient-minidesktop.gschema.override: Explicitly use MATE- + specific theming of the desktop UI. (Closes: #1364). + -- X2Go Release Manager <git-admin(a)x2go.org> Sun, 02 Dec 2018 06:49:42 +0100 x2gothinclient (1.5.0.0-0x2go1) unstable; urgency=low

1 0

Bug#1349: Fwd: Bug#1349: x2goclient not connecting after upgrade
by Javier Almasoft 18 Jan '19

18 Jan '19

From: Javier Almasoft <javier.almasoft(a)gmail.com> Date: jue., 10 ene. 2019 a las 10:25 Subject: Re: [X2Go-Dev] Bug#1349: x2goclient not connecting after upgrade I did a bit of testing today, and managed to set it running. I happen to have a non-standard port declared as default for ssh connections in my .ssh/config file, in the form: Host * Port NNNNN at the end of the file, because I have the custom of setting my installed servers apart from the default 22, to minimize attacks from port scanners. And not all my remote machines are declared in the config file, so this line takes care of the forgotten ones. If I comment out that line, x2goclient works again, both connecting to the default port 22 or to a non-standard port. It didn't matter before if I was connecting to a standard setup in port 22, or a custom one. It always choked at that line. This line doesn't give problems in my ssh connections, though. Perhaps there is a problem somewhere in the parsing of the ssh config file? Where should I report that? Thanks for taking your time in answering (and motivating me in digging more on this... ;-) ). It was really a nuisance, i use x2go in a lot if machines. -- Un saludo, Javier Martínez ALMASOFT, S.L.

1 0

Bug#1360: Works for me now
by Tristan Miller 17 Jan '19

17 Jan '19

The RPM is installable for me now. Either some X2Go developer changed the Perl dependency in the X2Go packages, or openSUSE changed its Perl RPMs so that they satisfy X2Go's requirements. Either way, this bug can probably be closed.

1 0

Bug#1363: Windows 10 version 1809 breaks X2go, can't read user name with space.
by Khoa Tran 15 Jan '19

15 Jan '19

Package: X2GoClient-4.1.2.0-2018.06.22-setup.exe Version: 4.1.2.0 1-After updating from Window 10 Ver 1803 to 1809; x2go doesn't work any more. 2- It fails with the following messages: Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, abortingLoop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, aborting *Looking at the "options" files now generated under Ver 1809, they look like:* nx/nx,root=/cygdrive/C/Users/Barry Pangrle/.x2go,connect=localhost,cookie=064e8b5bdd350e061f76b243b8d5b5e5,port=35936,errors=/cygdrive/C/Users/Barry Pangrle/.x2go/S-bpangrle-51-1546910140_stDMATE_dp32/sessions:51 *An "options" file generated under Ver 1803 looks like:* nx/nx,root=/cygdrive/C/Users/BARRYP~1/X2GO~1,connect=localhost,cookie=e8a3a18f683a68163533a911fad81985,port=45490,errors=/cygdrive/C/Users/BARRYP~1/X2GO~1/S-bpangrle-51-1545005939_stDMATE_dp32/sessions:51 It looks like the old version used to use "BARRYP~1" in the path instead of "Barry Pangrle" and based on the error messages, it seems to not be able to trace through the " " in the path name. 3. Expect to read folder with space and replace with ~ instead of space. 4. X2go can't read space, can't replace with ~ and failed. Also, please list the following info: 1. The client machine's OS (e.g., “Windows 10 pro version 1809”) 2. The client machine's version of X2GoClient: 4.1.2.0 3. The server's OS: CentOS 7, worked with Windows 10 version 1803

1 0

x2go on Windows 10 - crashes on connect - problem libssh version
by Gerhard Wiesinger 15 Jan '19

15 Jan '19

Hello, The following versions crash on connect from Windows 10 to a Fedora 28 server: x2goclient-4.1.0.0-2017.03.11-setup.exe x2goclient-4.1.1.1-2018.03.01-setup.exe x2goclient-4.1.2.0-2018.06.22-setup.exe x2goclient-4.1.2.2-2018.11.30-6596556-setup.exe The last good known version is: x2goclient-4.0.5.2-2016.09.20-setup.exe UAC is disabled on this computer When I copy libssh.dll from x2goclient-4.0.5.2-2016.09.20 to the newer version, everything works well. Solution and summary: x2goclient-4.1.2.2-2018.11.30-6596556-setup.exe with libssh.dll from x2goclient-4.0.5.2-2016.09.20-setup.exe is OK!!!!!!!! OK: libssh 0.7.0 NOK: libssh 0.7.4 Can you please update libssh to https://www.libssh.org/files/0.8/libssh-0.8.6.tar.xz (and include Pageant support, fixes also some security leaks) OpenSSL upgrade to 1.1.1a would also be fine (currently 1.0.2n is installed, one year old). If I should test something let me know. Thank you. Ciao, Gerhard

1 1

Bug#1362: Upgrade to Windows 10 version 1809 break X2Go, can't read user name with space
by Khoa Tran 14 Jan '19

14 Jan '19

Package: <X2GoClient-4.1.2.0-2018.06.22-setup.exe> Version: <4.1.2.0> 1-After updating from Window 10 Ver 1803 to 1809; x2go doesn't work any more. 2- It fails with the following messages: Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Loop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, abortingLoop: PANIC! Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Error: Can't open options file '/cygdrive/C/Users/Barry'. Error is 2 'No such file or directory'. Connection timeout, aborting Looking at the "options" files now generated under Ver 1809, they look like: nx/nx,root=/cygdrive/C/Users/Barry Pangrle/.x2go,connect=localhost,cookie=064e8b5bdd350e061f76b243b8d5b5e5,port=35936,errors=/cygdrive/C/Users/Barry Pangrle/.x2go/S-bpangrle-51-1546910140_stDMATE_dp32/sessions:51 An "options" file generated under Ver 1803 looks like: nx/nx,root=/cygdrive/C/Users/BARRYP~1/X2GO~1,connect=localhost,cookie=e8a3a18f683a68163533a911fad81985,port=45490,errors=/cygdrive/C/Users/BARRYP~1/X2GO~1/S-bpangrle-51-1545005939_stDMATE_dp32/sessions:51 It looks like the old version used to use "BARRYP~1" in the path instead of "Barry Pangrle" and based on the error messages, it seems to not be able to trace through the " " in the path name. 3. Expect to read folder with space and replace with ~ instead of space. 4. X2go can't read space, can't replace with ~ and failed. Also, please list the following info: 1. The client machine's OS (e.g., “Windows 10 pro version 1809”) 2. The client machine's version of X2GoClient: 4.1.2.0 3. The server's OS: CentOS 7, worked with Windows 10 version 1803

1 0

Bug#1361: Fwd: [Bug 1665366] New: Cannot run AttributeError: module 'wx' has no attribute 'TaskBarIcon'
by Orion Poplawski 11 Jan '19

11 Jan '19

Package: pyhoca-gui -------- Forwarded Message -------- Subject: [Bug 1665366] New: Cannot run AttributeError: module 'wx' has no attribute 'TaskBarIcon' Date: Fri, 11 Jan 2019 07:15:55 +0000 From: bugzilla(a)redhat.com To: orion(a)nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1665366 Bug ID: 1665366 Summary: Cannot run AttributeError: module 'wx' has no attribute 'TaskBarIcon' Product: Fedora Version: 29 Hardware: x86_64 OS: Linux Status: NEW Component: pyhoca-gui Severity: high Assignee: orion(a)nwra.com Reporter: rastislav.janci(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)nwra.com Target Milestone: --- Classification: Fedora Description of problem: Cannot execute puhoca-gui application because of the changes in wxpython4 - wx.TaskBarIcon is moved to wx.adv.TaskBarIcon Version-Release number of selected component (if applicable): pyhoca-gui-0.5.0.7-6.fc29.noarch python3-cups-1.9.72-22.fc29.x86_64 python3-setproctitle-1.1.10-9.fc29.x86_64 python3-gobject-base-3.30.4-1.fc29.x86_64 python3-wxpython4-4.0.1-9.fc29.x86_64 python3-x2go-0.6.0.2-1.fc29.noarch How reproducible: run pyhoca-gui Steps to Reproduce: 1. Open command line 2. run pyhoca-gui Actual results: Traceback (most recent call last): File "/usr/bin/pyhoca-gui", line 35, in <module> from pyhoca.wxgui.launcher import PyHocaGUI_Launcher File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/launcher.py", line 44, in <module> from .frontend import PyHocaGUI File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/frontend.py", line 42, in <module> from . import taskbar File "/usr/lib/python3.7/site-packages/pyhoca/wxgui/taskbar.py", line 83, in <module> class PyHocaGUI_TaskBarIcon(wx.TaskBarIcon): AttributeError: module 'wx' has no attribute 'TaskBarIcon' Expected results: executed -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

Bug#1357: X2Go issue (in src:x2goserver) has been marked as pending for release
by Mike Gabriel 11 Jan '19

11 Jan '19

tag #1357 pending fixed #1357 4.1.0.4 thanks Hello, X2Go issue #1357 (src:x2goserver) 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=x2goserver.git;a=commitdiff;h=d7c4222 The issue will most likely be fixed in src:x2goserver (4.1.0.4). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit d7c42225b52d42111b1220888c024ed4efe3b061 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Fri Jan 11 12:34:39 2019 +0100 debian/changelog: add bug closure for #1357 diff --git a/debian/changelog b/debian/changelog index 0526008..2547462 100644 --- a/debian/changelog +++ b/debian/changelog @@ -5,7 +5,7 @@ x2goserver (4.1.0.4-0x2go1) UNRELEASED; urgency=medium - Fix version number in VERSION.x2goserver-desktopsharing. - x2goserver-x2goagent: Drop x2goagent.keyboard file. - x2goversion: Fix situations where ${compfile} contains a - non-absolute path (e.g. it contains '../'). + non-absolute path (e.g. it contains '../'). (Fixes: #1357). * debian/x2goserver.postinst: + Drop duplicate sourcing of debconf includes.

2 1

Processed: tags 1358 rpm-packages
by owner＠bugs.x2go.org 09 Jan '19

09 Jan '19

Processing commands for control(a)bugs.x2go.org: > tags 1358 rpm-packages Bug #1358 [x2goclient] x2goclient for openSUSE 15.0 is missing Added tag(s) rpm-packages. > End of message, stopping processing here. Please contact me if you need assistance. -- 1358: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1358 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#1360: openSUSE RPM depends on obsolete (and nowadays missing) Perl
by Tristan Miller 09 Jan '19

09 Jan '19

Package: x2goserver Version: 4.1.0.4 Tag: rpm-packages The openSUSE Tumbleweed packages for x2goserver at <https://wiki.x2go.org/doku.php/wiki:repositories:suse> are not compatible with the version of Perl currently distributed by Tumbleweed. This makes it impossible to install them on Tumbleweed; if they are already installed then it makes it impossible to update Tumbleweed without uninstalling x2goserver. For example: $ sudo zypper update perl Loading repository data... Reading installed packages... There is an update candidate for 'perl', but it is from a different vendor. Use 'zypper install perl-5.28.1-169.5.x86_64' to install this candidate. Resolving package dependencies... Problem: x2goserver-xsession-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 requires perl(:MODULE_COMPAT_5.26.2), but this requirement cannot be provided deleted providers: perl-5.26.2-1.4.x86_64 Solution 1: Following actions will be done: deinstallation of x2goserver-xsession-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of x2goserver-common-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of x2goserver-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of perl-X2Go-Server-DB-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of perl-X2Go-Server-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of perl-X2Go-Log-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 deinstallation of x2goserver-extensions-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 Solution 2: do not install perl-5.28.1-1.1.x86_64 Solution 3: break x2goserver-xsession-4.1.0.4-0.0x2go1.0.git20181213.1753.heuler.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c):

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev