x2go-dev

x2go-dev@lists.x2go.org

2 participants
5403 discussions

Can I create an x2goclient branch for 4.0.2.0 with a few commits cherry-picked?
by Michael DePaulo 10 Jul '14

10 Jul '14

Hi guys, So Stefan Baur mentioned that he cannot deploy X2Go Client 4.0.2.0 for Windows to his clients right now without these 2 commits, and preferably the 3rd commit also. He has been waiting for 4.0.2.1 for this reason: http://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=b1246af262afde6a986… http://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=18f4c677a7d9057ec5f… http://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=0ebe95fc2fa15a61ccb… I mentioned that I could probably easily rebuild 4.0.2.0 for Windows with those 3 commits cherry-picked. May I create a new branch to do this work and push the branch to code.x2go.org? I will update the version string too. I will also make the builds available to everyone on code.x2go.org/releases/, probably under a separate folder. (It will not be the default Windows version.) If you'd like me to name the branch a certain way, let me know. -Mike

3 7

Note about nightly builds for x2goclient 4.0.2.1 for Windows (release/4.0.2.x branch)
by Michael DePaulo 10 Jul '14

10 Jul '14

There will be no nightly 4.0.2.1 builds for now. The nightly builds will be 4.0.3.0 instead. To avoid likely confusion, I deleted the 2014-07-09 nightly build, since 2014-07-09 was when decided to split 4.0.2.1 onto its own branch with fewer changes. Granted, the windows build scripts need some improvements. However, If I understand the build scripts correctly, improving the windows build scripts to the point that they have feature parity with the linux build scripts still would not enable us to produce 4.0.2.1 nightly builds. This is due to branch naming. Anyway, every time someone needs me to, I will produce a new 4.0.2.1 preview build at my earlier convenience. Remember, we intend to release 4.0.2.1 by the end of Friday anyway, -Mike#2

1 0

Testers Wanted: X2Go Client for Windows 4.0.2.1-pre05
by Michael DePaulo 10 Jul '14

10 Jul '14

In preparation for the upcoming release of X2Go Client 4.0.2.1 (which is now due by the end of Friday, July 11th) a new preview build (pre05) of X2Go Client for Windows is available to download under: http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.2.1/ It is based on commit 650e1ec. http://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=650e1ecf11fac09a52d… Note that 4.0.2.1-pre05 has fewer changes than 4.0.2.0 than 4.0.2.1-pre04 did for reasons explained in this email thread: http://lists.x2go.org/pipermail/x2go-dev/2014-July/007751.html Basically, the backstory and the reasoning is "Too many large and risky changes were scheduled for 4.0.2.1. Especially the fixes for #159, and its regression #525. So we are pushing those large changes to 4.0.3.0, and releasing 4.0.2.1 now with a smaller and safer set of changes." Note that the change to how the fonts are packaged has been reversed because that is a fairly large change that belongs in 4.0.3.0, not 4.0.2.x. So the "miscfonts" and "fullfonts" builds are back again. -Mike#2

1 0

Bug#528: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike DePaulo 09 Jul '14

09 Jul '14

tag #528 pending fixed #528 4.0.2.1 thanks Hello, X2Go issue #528 (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=1ad1c83 The issue will most likely be fixed in src:x2goclient (4.0.2.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 1ad1c83442106fb9fcb5a6b837e13a7a12e5d525 Author: Mike DePaulo <mikedep333(a)gmail.com> Date: Sun Jun 29 22:37:49 2014 -0400 Windows: Switch from regular NSIS 2.46 to NSIS Unicode 2.46.5 (Fixes #528) diff --git a/debian/changelog b/debian/changelog index 38c2685..ac57fbd 100644 --- a/debian/changelog +++ b/debian/changelog @@ -56,6 +56,8 @@ x2goclient (4.0.2.1-0x2go1) UNRELEASED; urgency=low - Windows: VcXsrv (XP Compatible) updated from 1.14.3.1 to 1.14.3.2. Fixes CVE-2014-0209, CVE-2014-0210, and CVE-2014-0211 (VcXsrv was also updated to 1.14.3.2 in 4.0.2.0+build2.) + - Windows: Switch from regular NSIS 2.46 to NSIS Unicode 2.46.5 + (Fixes: #528) -- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Thu, 10 Apr 2014 18:30:25 +0200

2 1

Bug#540: New wiki account for Nick Owen
by Nick Owen 09 Jul '14

09 Jul '14

Package: wiki.x2go.org Please create a wiki account for me. First name: Nick Last name: Owen Account name: nowen ᐧ

3 3

Bug#541: Patch to close Bug #525 has undesirable side effects
by Stefan Baur 08 Jul '14

08 Jul '14

Package: x2goclient Version: 4.0.2.1 Severity: grave Hi, Alex' latest patches introduce a new and more severe bug. His idea, assuming that Mike#1. Mike#2, Mihai and me understood him correctly, is, that on Windows, users shouldn't start x2goclient.exe any more, but rather the new x2gohelper.exe. ==>Alex, if we're misunderstanding what you wrote, please reply and explain your intentions. Assuming we're right, your plan breaks backward compatibility when it comes to desktop shortcuts on Windows, in two places. The smaller issue is that clicking the arrow on the session tile will create a desktop shortcut that is hardcoded to x2goclient.exe instead of x2gohelper.exe. This could be fixed with a small patch. However ... The bigger issue is that *all* existing links users may have on their desktops are broken, since they point to x2goclient.exe and can't easily be changed! I have at least one customer that makes heavy use of that feature, where it would mean manually updating over 600 desktop shortcuts. That is not going to be fun! We need to find a way to achieve what you were trying to achieve without breaking backward compatibility like that. >From what I understand so far, you're trying to build a "reaper" to clean up after a dying x2golient.exe, which may have left pulseaudio, xserver and ssh daemon running. I haven't tried to figure out what your current x2gohelper.exe is trying to do, and if you made changes to x2goclient.exe as well where functionality from x2goclient.exe is moved to x2gohelper.exe. If you moved it, rather than duplicating it, that's not going to help, because it might just as well be x2gohelper.exe that dies first and you'd again leave sshd, pulseaudio, and xserver dangling. Duplicating it might work, similar to how certain malware on Windows works (two processes checking on each other and re-spawning whichever gets killed first). So you'd have x2goclient.exe on the one hand permanently checking if x2gohelper.exe is running, respawning it when necessary, and upon shutdown, "trying" to clean up behind itself by terminating sshd, pulseaudio, xserver, and finally itself. While x2gohelper.exe would be checking if x2goclient.exe is still running - if not, it will terminate sshd, pulseaudio, xserver, (if any of them are still running) and finally itself. Before you start coding, I'd like to ask this question, though: Do we really want to have a reaper mechanism that tries to clean up after a malfunctioning x2goclient.exe, or wouldn't it be better to find out why x2goclient.exe is malfunctioning, fix these issues / catch those exceptions and deal with them appropriately (i.e. properly shutting down sshd, pulseaudio and xserver before going belly-up)? The latter would mean we need more bug reports and it requires analyzing what exactly went wrong, but it would be less disturbing to x2goclient development and roll-out. Whichever path you choose, Alex, please do keep in mind that we have a release planned in the near future and your latest commits aren't exactly helpful in getting 4.0.2.1 stabilized (and I *need* 4.0.2.1 out soon, my customers are desperately waiting for it because of the improved sound that PA5 brings). It would be really really cool if you could either do your development on a separate branch that could later become 4.0.2.2, or hold back until we have released 4.0.2.1. If you don't know how to do create your own branch for development, I'm sure there is more than just one Dev on the list that will help you. Kind Regards, Stefan

1 0

Bug#525: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike Gabriel 08 Jul '14

08 Jul '14

tag #525 pending fixed #525 4.0.2.1 thanks Hello, X2Go issue #525 (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=5bb4a33 The issue will most likely be fixed in src:x2goclient (4.0.2.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit 5bb4a331fed1f1891a9ff176ae4f0221ba4a4c6b Author: Oleksandr Shneyder <o.shneyder(a)phoca-gmbh.de> Date: Tue Jul 8 17:27:59 2014 +0200 Add x2gohelper to start X2Go Client on Windows and clean child processes if X2Go Client crashes. (Fixes: #525). diff --git a/debian/changelog b/debian/changelog index f4e8419..8551493 100644 --- a/debian/changelog +++ b/debian/changelog @@ -53,6 +53,8 @@ x2goclient (4.0.2.1-0x2go1) UNRELEASED; urgency=low - Update string "&Clipboard Mode" and translate in russian translation file. - Grammar fix in russian translation. - Fix "fullscreen" mode on Windows 7 with multiple monitors. + - Add x2gohelper to start X2Go Client on Windows and clean child processes if + X2Go Client crashes. (Fixes: #525). [ Mike DePaulo ] * New upstream release (4.0.2.1):

2 1

Testers Wanted: X2Go Client for Windows 4.0.2.1-pre04
by Michael DePaulo 08 Jul '14

08 Jul '14

In preparation for the upcoming release of X2Go Client 4.0.2.1 (which has been delayed till after August 2nd,) a new preview build (pre04) of X2Go Client for Windows is available to download under: http://code.x2go.org/releases/binary-win32/x2goclient/previews/4.0.2.1/ It is based on commit 3d76d00. http://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=3d76d001c18fef4f88c… In particular, there are 2 things we would like people to test: 1. That bug #525 is fixed.: x2goclient.exe shows "arrow and hourglass" cursor for 5 seconds during startup http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=525 2. Testing the installer in general, particularly for regressions in internationalization. Major improvements have been made to the installer in order to provide a proper fix for bug #108. There are no longer separate fonts builds, they are included in the regular build. (There is still a debug build though.) The inclusion of the fonts makes the regular build and the debug build about 50MB instead of about 20MB. -Mike#2

1 2

Bug#108: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike DePaulo 08 Jul '14

08 Jul '14

tag #108 pending fixed #108 4.0.2.1 thanks Hello, X2Go issue #108 (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=c0bc05f The issue will most likely be fixed in src:x2goclient (4.0.2.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit c0bc05f8e607afaa3aeb49af62eaf5d21e572519 Author: Mike DePaulo <mikedep333(a)gmail.com> Date: Mon Jul 7 23:06:07 2014 -0400 Windows: Include all fonts in NSIS installer, make them optional, and install only "misc" by default. (Fixes: #108) Also make desktop shortcut optional. diff --git a/debian/changelog b/debian/changelog index 3148ef4..f4e8419 100644 --- a/debian/changelog +++ b/debian/changelog @@ -56,12 +56,19 @@ x2goclient (4.0.2.1-0x2go1) UNRELEASED; urgency=low [ Mike DePaulo ] * New upstream release (4.0.2.1): + - Windows: Install VcXsrv "misc" fonts by default, and make all 4 font + groups optional: misc, 75dpi, 100dpi and others (Fixes: #108) + Note: The fact that all the fonts are included makes the installer about + 30MB larger. (See next comment, it would be even larger.) + - Windows: Reduce the new size of NSIS installer by several MB + by switching to lzma solid compression + - Windows: Make the desktop shortcut optional during install, + but still the default. - Windows: Prevent high PulseAudio CPU usage on Windows XP by lowering PulseAudio's CPU priority from "high" to "normal" on XP specifically. Also do so on Windows Server 2003 (R2) (Fixes #526) - Windows: Enable PulseAudio log when --debug is passed. - Windows: Fix compatibility with current PulseAudio master branch - - Windows: Reduce size of NSIS installer by switching to lzma solid compression - Windows: cygwin packages (inluding patched OpenSSH 6.6.1p1-3) updated from latest versions as of 2014-04-08 to latest versions as of 2014-06-09. This includes openssl 1.0.1h-1, which fixes the 6 CVEs announced on 2014-06-05.

2 1

Processed: clone 108 for pyhoca-gui
by owner＠bugs.x2go.org 08 Jul '14

08 Jul '14

Processing commands for control(a)bugs.x2go.org: > clone #108 -1 Bug #108 [x2goclient] Missing fonts in X application Bug 108 cloned as bug 538 > reassign -1 pyhoca-contrib Bug #538 [x2goclient] Missing fonts in X application Bug reassigned from package 'x2goclient' to 'pyhoca-contrib'. Warning: Unknown package 'pyhoca-contrib' Warning: Unknown package 'pyhoca-contrib' Ignoring request to alter found versions of bug #538 to the same values previously set Warning: Unknown package 'pyhoca-contrib' Warning: Unknown package 'pyhoca-contrib' Ignoring request to alter fixed versions of bug #538 to the same values previously set Warning: Unknown package 'pyhoca-contrib' > clone #108 -2 Bug #108 [x2goclient] Missing fonts in X application Bug 108 cloned as bug 539 > reassign -2 pyhoca-gui Bug #539 [x2goclient] Missing fonts in X application Bug reassigned from package 'x2goclient' to 'pyhoca-gui'. Ignoring request to alter found versions of bug #539 to the same values previously set Ignoring request to alter fixed versions of bug #539 to the same values previously set > found -2 0.4.0.8 Bug #539 [pyhoca-gui] Missing fonts in X application There is no source info for the package 'pyhoca-gui' at version '0.4.0.8' with architecture '' Unable to make a source version for version '0.4.0.8' Marked as found in versions 0.4.0.8. > found -2 0.5.0.0-pre02 Bug #539 [pyhoca-gui] Missing fonts in X application There is no source info for the package 'pyhoca-gui' at version '0.5.0.0-pre02' with architecture '' Unable to make a source version for version '0.5.0.0-pre02' Marked as found in versions 0.5.0.0-pre02. > End of message, stopping processing here. Please contact me if you need assistance. -- 108: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=108 538: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=538 539: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=539 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

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