Should I file this as a bug report? Also, I just retested this with PulseAudio 4.99.3 on the same windows 7 system. The issue was still present, but there was 1 difference: if I set the environment variable: XDG_RUNTIME_DIR=C:\Users\mike\ Then this cookie is created along with its parent dirs: C:\Users\mike\.config\pulse\cookie And this empty directory is created: C:\Users\mike\pulse -Mike On Wed, Jan 29, 2014 at 10:35 PM, Michael DePaulo <mikedep333 at gmail.com> wrote: > I think I've discovered a bug in the way the cookies are created since > 3.0 changed the default location of the cookies in order to adhere to > the XDG Base Directory Specification > > Or maybe I am just calling/using PulseAudio incorrectly.. > > If I run: > C:\Program Files\x2goclient\pulseaudio-3.0-win32>pulseaudio.exe -F > c:\Users\mike\x2go-temp\config.pa > > where config.pa contains the lines: > load-module module-native-protocol-tcp port=4713 > load-module module-esound-protocol-tcp port=4714 > load-module module-waveout > > Then a cookie is created at along with its parent dirs: > C:\Users\mike\.config\pulse\cookie > > If I override the environment variable USERPROFILE from > "C:\Users\mike\" to any other value, then the cookie is still created > relative to that variable. > > However, if I set the environment variable: > XDG_RUNTIME_DIR=C:\Users\mike\ > Then this directory is created along with its parent dirs, but the > cookie is not: > C:\Users\mike\.config\pulse\ > > If I set this environment variable instead: > XDG_CONFIG_HOME=C:\Users\mike\ > Then this directory is created along with its parent dirs, but the > cookie is not: > C:\Users\mike\pulse\mothership-7-32-runtime\ > (mothership-7-32 is this VM's hostname) > > Finally, if I set both aforementioned XDG environment variables, > Then this directory is created, and the cookie is not: > C:\Users\mike\pulse\ > > -Mike DePaulo > win32 Package Maintainer for the X2Go Project
