[X2Go-Dev] Processed: X2Go issue (in src:x2goclient) has been marked as pending for release

2014-03-16 Thread X2Go Bug Tracking System
Processing commands for cont...@bugs.x2go.org: tag #422 pending Bug #422 [x2goclient] Windows PulseAudio 3.0 and later fail to start due to missing cookie Added tag(s) pending. fixed #422 4.0.2.0 Bug #422 [x2goclient] Windows PulseAudio 3.0 and later fail to start due to missing cookie There

[X2Go-Dev] Bug#422: X2Go issue (in src:x2goclient) has been marked as pending for release

2014-03-16 Thread Mike DePaulo
tag #422 pending fixed #422 4.0.2.0 thanks Hello, X2Go issue #422 (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=acbc897 The issue will most

Re: [X2Go-Dev] schedule release of X2Go Client 4.0.2.0

2014-03-16 Thread Michael DePaulo
Mike, As I mentioned on IRC, I accidentally applied the commit to the master branch. Let me know how you want me to proceed. Also, since it is a regression, I would like to spend until the end of Monday (tomorrow) night looking into bug 448 and hopefully fixing it by then. On Fri, Mar 14, 2014

Re: [X2Go-Dev] schedule release of X2Go Client 4.0.2.0

2014-03-16 Thread Mike Gabriel
Hi Michael, On So 16 Mär 2014 17:16:35 CET, Michael DePaulo wrote: As I mentioned on IRC, I accidentally applied the commit to the master branch. Let me know how you want me to proceed. The way to do such a dual branch commit properly is this: o Checkout the release/4.0.1.x branch o

Re: [X2Go-Dev] schedule release of X2Go Client 4.0.2.0

2014-03-16 Thread Michael DePaulo
On Sun, Mar 16, 2014 at 1:24 PM, Mike Gabriel mike.gabr...@das-netzwerkteam.de wrote: Hi Michael, a follow-up thought... We should not provide 4.0.1.4 for Windows. Only 4.0.2.0. The reason for the dual upcoming release is that distros that have an old libssh have the choice to use a legacy

[X2Go-Dev] Bug#448: Linux not affected

2014-03-16 Thread Michael DePaulo
This bug was not present on the following client setup: Fedora 20 64-bit GNOME keyring 3.10.1 (1.fc20) libssh 0.6.3 (1.fc20) x2goclient 4.0.1.3 (4.fc20) Specifically, 1. if I had not entered my passphrase for my private key into GNOME kerying yet, then upon initiating the connection GNOME

[X2Go-Dev] Bug#448: KDE's libssh was patched for Pageant support

2014-03-16 Thread Michael DePaulo
If you compare KDE's libssh 0.5.3 src/agent.c ftp://winkde.org/kde/ports/win32/releases/stable/latest/libssh-x86-mingw4-0.5.3-src.tar.bz2 To the vanilla libssh 0.5.3 src/agent.c http://git.libssh.org/projects/libssh.git/tree/src/agent.c?id=libssh-0.5.3 You'll see that KDE patched it to add