[X2Go-Dev] X2Go Client Windows binary 4.0.1.2pre02

[Michael DePaulo]

Stefan,

I posted this workaround reply to the bug tracker, but it does not
seem to be showing up. So here is the exact text I posted:
------------------

Please test and follow this workaround with x2goclient-4.0.1.2pre02
(for windows) until a 4.0.1.2pre02 package with the old pulseaudio is
made (most likely in several hours):

1. Install x2goclient 4.0.1.2pre02 if you haven't already. It will by
default be installed to "C:\Program Files\x2goclient\" on 32-bit, and
"C:\Program Files (x86)\x2goclient\" on 64-bit.
2. Rename the installation location's "pulse" subfolder to "pulse-1.1"
3. Download http://code.x2go.org/releases/binary-win32/x2goclient/with-old-pulseaudio-0.9.6/releases/4.0.0.3/x2goclient-4.0.0.3.interims-setup.exe
but do not install it.
4. Open that .exe file in 7-zip or peazip as an archive and extract
the $_OUTDIR\pulse\ folder from it. Do not extract it directly to the
installation location's folder. Instead, extract it to someplace where
you have write permissions, such as your "My Documents" so that
windows UAC file virtualization does not interfere.
(There's other ways to get this "pulse" folder too. E.g, installing it
on a spare machine and copying the folder. Temporarily uninstalling
x2goclient 4.0.1.2pre02 and installing 4.0.0.3.interims, etc.)
5. Copy the "pulse" folder to the x2go installation folder.

I quickly tested this workaround on an x2goserver VM running ubuntu
12.04.x 32-bit (with the latest updates and the quantal HWE) and it
did fix this bug for me. (This bug was present when I did not perform
the workaround.) My client system is windows 8.1 64-bit.

On Wed, Dec 11, 2013 at 11:51 AM, Stefan Baur
<newsgroups.mail2 at stefanbaur.de> wrote:
> Am 11.12.2013 17:47, schrieb Michael DePaulo:
>
>> I will look into providing a build of x2goclient 4.0.1.2pre02 with the
>> old pulseaudio. I am hoping it will not require any changes to the
>> source code for x2goclient. Note that providing such a build was not
>> listed in these instructions I followed:
>>
>> http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
>
>
> That's probably because the documentation was either written before the
> "fork/workaround" was developed, or because whoever wrote the instructions
> didn't expect the problem to last. ;-)
>
> -Stefan