<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c23">Comment # 23</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 <a class="email" href="mailto:mikedep333@gmail.com" title="Michael DePaulo <mikedep333@gmail.com>"> Michael DePaulo</a> <pre>Hi Tanu, 1st, note that on Windows, %USERPROFILE% is the replacement for $(HOME). Submit complaints to 1 Microsoft Way... 2nd, remember that X2Go users might downgrade their PulseAudio version on Windows. We have supported PulseAudio downgrades on Windows. So both .pulse-cookie and .config/pulse/cookie might exist when PulseAudio 1.1 is installed. When we did not set auth-cookie at all, if the following conditions were met, PulseAudio failed to create the cookie and therefore failed to start: 1. PulseAudio 3.0 & later on Windows 2. PA was launched by X2Go Client, rather than from the command line. 3. Neither ".pulse-cookie", ".config/pulse/cookie" or ".config/pulse/" existed. It took me a long time to figure out that we could fix the issue by creating the empty dir ".config/pulse/". We considered just creating said empty dir, but we talked with you and decided on specifying auth-cookie instead. We only specify auth-cookie if PulseAudio 3.0 or later is installed. We check the version by running "pulseaudio.exe --version" and then reading the stdout. This is a long bug report, but I documented it here: <a href="http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=422">http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=422</a> I might have fixed said issue (condition #2) with x2goclient commit 6d3998f6: Windows: Fix compatibility with current PulseAudio master branch by replacing forward shashes with backslashes in file/folder paths. (Yes, I made a typo in the commit message.) That commit was actually necessary for the current PA master branch to work with x2goclient. The fact that we had specified %USERPROFILE% as an 8.3 filepath with forward slashes seemed like a bug in our code, so I changed it to an 8.3 filepath with backslashes. I tested the change with master, 5.0, and old versions of PulseAudio, and then committed it to our code. Anyway, I need to do some actual testing. (My weekend is coming up, so I have time available.) If said commit fixed the issue with cookie creation on versions 3.0 through 5.0, then I could update x2goclient code to upload the correct cookie depending upon which version of PulseAudio is installed. However, it seems like less work for me to just specify an absolute cookie path, or to specify %XDG_CONFIG_HOME%.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>