So as we all know We all like bluetooth. And we all need pulseaudio to run it.
If you have anything to say against please find another thread this is about making it better.
Here we go years have gone by an we all needed to delete the .config/pulse or what ever those just point pulse to /tmp/pulse-*.
so after so many years we are still unable to point to the correct socket. or delete ~/home/.config/pulse
when you do that and reboot it forces a new socket.
I am lost before I spend stupid hours looking at a simple code any help would be nice.
I am not a pulseaudio lover I can use jackd and pulse together like a team. so if you send a hate pulse in please just give a report to Jeremy for you will get a simple TSK.
Time to fix the socket how it is created and pointed to.
going to pull the latest branch.
Check back in 30 days.
FAB

I have no idea what you want help about. Other than it's something about pulseaudio sockets.

Just a shot in the dark: I have had similar issues, in cases where the socket provider writes in $XDG_RUNTIME_DIR whereas the other app looks for it in $XDG_CACHE_HOME. The solution was to use the same dir, like I do writing in ~/.profile:

Thanks for feed back seems pulseaudio does not clear the pid all the time /tmp/pulse/pid. And the one in ~/home/.config/ points to old /tmp/pulse which means DE isn't creating an updated link. It becomes stale. Mark this solved go to the github thanks.

This seems like a decent idea. I posted a proposal in the Requests for -current (14.2-->15.0) thread