I have ~/.pulse-cookie, and I don't have ~/.config/pulse/cookie. The daemon should use ~/.pulse-cookie without complaints, but it prints warnings about failing to load ~/.config/pulse/cookie. The daemon does fall back to ~/.pulse-cookie and uses it successfully, so the warnings don't indicate any real problem. The unnecessary warnings in the log are confusing to users.
Also, if no cookie exists at all when starting pulseaudio, there are even more warnings: W: [pulseaudio] authkey.c: Failed to open cookie file '/home/tanu/.config/pulse/cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to load authentication key '/home/tanu/.config/pulse/cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to open cookie file '/home/tanu/.pulse-cookie': No such file or directory W: [pulseaudio] authkey.c: Failed to load authentication key '/home/tanu/.pulse-cookie': No such file or directory None of the warnings are useful.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/497.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.