[pulseaudio-tickets] [Bug 75006] neither XDG_CONFIG_HOME or PULSE_COOKIE is respected

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jun 13 06:58:18 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=75006

--- Comment #24 from Tanu Kaskinen <tanuk at iki.fi> ---
(In reply to comment #23)
> Hi Tanu,
> 
> 1st, note that on Windows, %USERPROFILE% is the replacement for $(HOME).
> Submit complaints to 1 Microsoft Way...

Sure, I use $(HOME) just as a shorthand. %USERPROFILE% is handled fine.

> 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.

This should be no problem, if after the downgrade both the server and the
clients are using the same version of libpulse. As long as the server and the
clients use the same logic for finding the cookie, things should work.

> 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:
> http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=422
> 
> 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.

PulseAudio should create the necessary directories if they don't exist. The
slash issue indeed sounds like a probable cause for the directory creation
failure.

> 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%.

Setting XDG_CONFIG_HOME is probably not a good idea. If I understood correctly,
you'd set USERPROFILE to "C:\Users\mike.DEPAULO\.x2go\pulse" and
XDG_CONFIG_HOME to "C:\Users\mike.DEPAULO\.x2go". That probably works, but
doesn't make sense conceptually. It would be similar to setting XDG_CONFIG_HOME
on Linux to /home, and assuming that the user name is "pulse".

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/pulseaudio-bugs/attachments/20140613/8d4f6d30/attachment-0001.html>


More information about the pulseaudio-bugs mailing list