So I'm currently running PipeWire with pipewire-alsa, pipewire-pulse and Wireplumber, and for whatever reason something (supposedly not PipeWire (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3113)) keeps re-making a ~/.pulse-cookie file on my end as opposed to using the allegedly standard $XDG_CONFIG_HOME/pulse/cookie. I've been told it might be an out-of-date version of libpulse, but I have no idea how that might be since I have the latest build of its respective package.
What exactly could be remaking this file and ignoring the new path?
Bump?
Do you use by any chance Steam or some containerized or proprietary program? Cause i had that file pop up once too.
Oh, it actually is Steam that creates it each time. What the fuck.
E: Also found out immediately after that there is still a config file in /etc/pulse/client.conf and Steam seems to at least honour it. Guess that solves it.