<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - neither XDG_CONFIG_HOME or PULSE_COOKIE is respected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75006#c18">Comment # 18</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED --- - neither XDG_CONFIG_HOME or PULSE_COOKIE is respected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=75006">bug 75006</a>
from <span class="vcard"><a class="email" href="mailto:mikedep333@gmail.com" title="Michael DePaulo <mikedep333@gmail.com>"> <span class="fn">Michael DePaulo</span></a>
</span></b>
<pre>@Tanu, please hold off on committing the 9 patches for now.
Currently we (x2goclient master branch) are telling pulseaudio win32 to load a
config.pa script with the following lines (the only thing that ever varies is
the port):
load-module module-native-protocol-tcp port=4713 auth-cookie=\.pulse-cookie
load-module module-esound-protocol-tcp port=4714
load-module module-waveout
And we have %USERPROFILE% set to a value such as:
C:\Users\MIKE~1.DEP\X2GO~1\pulse
We have neither XDG_CONFIG_HOME or PULSE_COOKIE set.
With 5.0-121-g38c5d without the 9 patches applied, the following intended
cookie is used, and X2Go Client works with PulseAudio:
C:\Users\mike.DEPAULO\.x2go\pulse\.pulse-cookie
debug log: <a href="http://pastebin.com/ptFAwJQ6">http://pastebin.com/ptFAwJQ6</a>
When I apply all 9 patches (5.0-121-g38c5d-dirty), that cookie is not used.
Instead, the following cookie is created (and presumably used):
C:\Users\mike.DEPAULO\.x2go\pulse\.config\pulse
debug log: <a href="http://pastebin.com/Y2Ke2rk7">http://pastebin.com/Y2Ke2rk7</a>
Since we copy the other cookie to the X2Go Server, audio does not work.
I will try to fix this compatibility issue by defining %PULSE_COOKIE% and/or
%XDG_CONFIG_HOME% in the x2goclient master branch code that launches (and sets
the environment for) pulseaudio.exe. I'll let you know how it goes.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>