x2go-dev

x2go-dev@lists.x2go.org

1 participants
5403 discussions

Processed: your mail
by owner＠bugs.x2go.org 02 Jul '15

02 Jul '15

Processing commands for control(a)bugs.x2go.org: > close 157 Bug #157 [x2goclient] x2goclient.app 4.0.0.4 crashes immediately on launch Bug #209 [x2goclient] Mac Client crashes on start Marked Bug as done Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 157: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=157 209: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=209 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#901: Patch to simplify lrelease in the x2goclient.pro
by Henning Heinold 02 Jul '15

02 Jul '15

Package: x2goclient Version: Tags: patch Hi, the attached patch makes it easier to determine the path of lrelease. With this patch it is possible to crosscompile with the mxe toolchain. Bye Henning

1 0

Cross-Compiling X2Go Client for Windows
by Michael DePaulo 02 Jul '15

02 Jul '15

Hi Heinz, At the X2Go Gathering 2015, I gave a talk on X2Go Client for Windows development: https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3… Although many components such as nxproxy have to be built with separate build systems and thus will have to be built manually, I would like there to be a more reproducible way to build X2Go Client itself (x2goclient.git -> x2goclient.exe & x2gohelper.exe). I love tools like pbuilder and mock for Linux. 2 possible solutions for this (cross-compilation environments) that look promising are: http://mxe.cc http://win-builds.org However, I think Mike#1 said that you told him there was a need to build X2Go Client for Windows via a Windows machine (the WinBuilder VM) rather than a cross-compilation environment. Can you explain the reason for that? Note that I am frequently updating this page: http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient I see 4 potential obstacles to using a cross-compilation environment: 1. We configure Qt for static builds (the Qt libraries are included withing x2goclient.exe): http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient… However, I doubt there is a need to configure Qt for static builds. If we have to distribute some Qt DLLs, so be it., Note that OpenSSL support in Qt should not be a problem; it is safe to assume that all the cross-compilation environments support that. 2. We have to use a version of libssh that is patched for Pageant support (upstream libssh wants to do redesign how they handle SSH agents before they accept the patch): http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient… 3. We would need to package libraries for the cross-compilation environments. For example, MXE lacks libssh. 4. At the end of the build, we need to combine all the 3rd party components (built with separate build systems) into the NSIS installer. This should be feasible though; MXE supports NSIS for example. -Mike#2

2 1

Bug#897: epel 5 repos have signature errors
by Christian Trenkwalder 02 Jul '15

02 Jul '15

Package: <buildscripts> Version: x2goserver.x86_64 0:4.0.1.19-0.0x2go2.1.git20150608.1064.main.el5.centos Hello, im using Red Hat Enterprise Linux Client release 5.8 (Tikanga) and get the following error for more than 1 dependency: > Header V3 RSA/SHA1 signature: BAD For the full log see the attachemend, i think this may be just like #699.

4 8

Bug#899: EPEL 6 8 Jul 2015 release has dependency error
by Harris, Peter A 01 Jul '15

01 Jul '15

Package: X2Go BTS Version: 4.0.1.19 When I try to yum install x2goserver on RHEL 6.6 from epel/6/x86_64, I get a dependency error for libXcompshad.so.3 required by nxagent. Downloading the package directly from http://packages.x2go.org/epel/6/main/x86_64/rpms/nx-libs/libXcompshad3-3.5.… and using yum to install just the one RPM returns the error "Nothing to do". I have a clean RHEL6.6 system. See attachments for: x2go.repo Output of "yum install x2goserver" Abridged yum output: [PAH-TEST-134-62-62] tmp> yum install x2goserver 2>&1 | tee /login/peteh/logs/yum_install_x2goserver.log Loaded plugins: aliases, changelog, downloadonly, kabi, presto, product-id, : refresh-packagekit, security, subscription-manager, tmprepo, : verify, versionlock Loading support for Red Hat kernel ABI Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.19-0.0x2go2.1.git20150608.1064.main.el6 will be installed ... ---> Package nxagent.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed ... --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 ... --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 --> Running transaction check ---> Package nx-libs.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed ---> Package nxagent.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 --> Finished Dependency Resolution Error: Package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 (x2go-release-epel) Requires: libXcompshad.so.3()(64bit) Direct investigation of the repo showed a non-zero length libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm, which I downloaded and tried to pre-install using yum: [PAH-TEST-134-62-62] tmp> ll libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm -rw-rw-r-- 1 root root 31940 Jun 7 19:35 libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm [PAH-TEST-134-62-62] tmp> yum install ./libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm Loaded plugins: aliases, changelog, downloadonly, kabi, presto, product-id, refresh-packagekit, security, subscription-manager, tmprepo, verify, versionlock Loading support for Red Hat kernel ABI Setting up Install Process Examining ./libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm: libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 Error: Nothing to do Regards, Pete Harris Danaher / Tektronix Danaher T&M / Global IT Infrastructure / UNIX Servers & Storage MS 50-555 / PO BOX 500 / BEAVERTON OR 97077-0500 Phone: +1.503.627.3989 Fax: +1.503.627.4005 -- Any opinions expressed are those of the author and may not be those of Danaher / Tektronix --

2 5

Processed: your mail
by owner＠bugs.x2go.org 30 Jun '15

30 Jun '15

Processing commands for control(a)bugs.x2go.org: > reassign 899 nx-libs 3.5.0.29 Bug #899 [x2go bts] EPEL 6 8 Jul 2015 release has dependency error Warning: Unknown package 'x2go' Warning: Unknown package 'bts' Bug reassigned from package 'x2go bts' to 'nx-libs'. No longer marked as found in versions 4.0.1.19. Ignoring request to alter fixed versions of bug #899 to the same values previously set Bug #899 [nx-libs] EPEL 6 8 Jul 2015 release has dependency error There is no source info for the package 'nx-libs' at version '3.5.0.29' with architecture '' Unable to make a source version for version '3.5.0.29' Marked as found in versions 3.5.0.29. > thanks Stopping processing here. Please contact me if you need assistance. -- 899: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=899 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

We should release nx-libs 3.5.0.32 soon because of the security fixes
by Michael DePaulo 30 Jun '15

30 Jun '15

Hi X2Go devs, Because the nx-libs 3.5.0.x branch contains X.org security fixes, I propose that we release 3.5.0.32 soon. More info: https://github.com/ArcticaProject/nx-libs/issues/29 -Mike#2

3 2

Re: [X2Go-Dev] Bug#883: Bug#883: Bug#883: Can be fixed by reverting winmultiwindow.patch
by Michael DePaulo 29 Jun '15

29 Jun '15

Hi Alex, I spoke with Jon Turney (jturney), the Cygwin XWin maintainer on #cygwin on Freenode. I also tested some options. It sounds like the best approach to making a "full screen" secondary monitor work is to launch VcXsrv (or Cygwin XWin) with these arguments: -nodecoration -screen 0 @2 For tertiary monitor, use @3 instead. This launches Cygwin XWin in root window mode (the default) rather than -multiwindow mode. -nodecoration hides the window decoration from the Windows OS. Can you please test this out and see if it meets your needs? If so, it should be a simple change to x2goclient to launch VcXsrv this way. Also, FYI: It is true that if you launch Cygwin XWin or VcXsrv in fullscreen mode, then it will always use the primary display, even when you tell it to use the secondary: -fullscreen -screen 0 @2 However, by telling either X server to use its older rendering engine, you can solve this problem: -fullscreen -engine 1 -screen 0 @2 I do not recommend this approach for x2goclient though because if you click out of the X server, then the X server minimizes. Note: these are the engines: -engine engine_type_id Override the server's automatically selected engine type: 1 - Shadow GDI 2 - Shadow DirectDraw - obsolete 4 - Shadow DirectDraw4 Non-Locking Engine 4 is the default. Engine 2 is not available on VcXsrv. Jon acknowledges that there is a secondary monitor limitation/bug with Engine 4. -Mike#2

1 0

My slides and related files from X2Go Gathering 2015
by Michael DePaulo 29 Jun '15

29 Jun '15

XSession, Polkit, and making apps “just work” https://docs.google.com/presentation/d/1EXx13YXzQcLQRXdQWthgo2xjqkLxbsiBDdV… Related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShM1NyQzktNHkyTmc&usp=sha… X2Go Client for Windows Development (40 minutes): https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3… Windows X server benchmarks & other related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShflN1c1BPZF9aTkh3NkF1Qkl… In the case of the latter presentation, I made some small corrections and added some info. You can view the versions from 2015-06-21 if you want to see exactly what I presented. -Mike#2

1 0

Bug#891: I have a fix for VcXsrv, but it needs discussion
by Michael DePaulo 28 Jun '15

28 Jun '15

So here is the fix for VcXsrv (which is bundled with X2Go Client) that I ported from Cygwin XWin: https://github.com/ArcticaProject/vcxsrv/commit/d45db884b19a0f081fcd259e3b3… Here is a test build of VcXsrv : https://github.com/ArcticaProject/vcxsrv/releases/tag/1.17.0.0-2-bug4test1 (I do not make a test build of X2Go Client available yet, so you'll have to test it via the "X.Org Server settings" GUI in X2Go Client.) And here is the issue against VcXsrv (X2Go/Arctica Builds): https://github.com/ArcticaProject/vcxsrv/issues/4 Read that issue for more details on why this bug happens with X2Go (and its component nx-libs.) Discussion over the details of the patch should be discussed there (or in a PR.) However, If I release X2Go Client 4.0.4.1 (or an update to 4.0.4.0) with this fix, then sessions started on X2Go Client for Windows 4.0.4.0-2015.06.24 and earlier can not be resumed on the new version. This could be very disruptive to users. Does anyone have any thoughts on this dilemma? -Mike#2

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev