Hi Sean, Thank you for the confirmation about pacmd ignoring PULSE_SERVER env var! I want to update a source's proplist and afaik pactl cannot do that. // this is what I want to do $ pacmd update-source-proplist mysource.monitor device.description=foo with PULSE_SERVER pointing to a different socket than the default one (i.e. something else than unix:/tmp/pulse-socket) Best regards, Tudor From: pulseaudio-discuss <pulseaudio-discuss-bounces@xxxxxxxxxxxxxxxxxxxxx> on behalf of Sean Greenslade <sean@xxxxxxxxxxxxxxxxxx> Sent: Wednesday, November 9, 2022 4:52 PM To: General PulseAudio Discussion <pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx> Subject: Re: pacmd ignores PULSE_SERVER env var On Sun, Nov 06, 2022 at 07:02:03PM +0000, Tudor Zaharia wrote: > Hello, > > Following this documentation page https://wiki.archlinux.org/title/PulseAudio ; > I am setting the PULSE_SERVER env var to point to a pulseaudio server that runs inside a docker container. > > Unfortunately the "pacmd" command seems to ignore this env var and query instead the local machine. Am I doing something wrong? Is this the expected behavior? > pactl command works as expected though. > > $ pacmd --ver > pacmd 13.99.1 > Compiled with libpulse 13.99.0 > Linked with libpulse 13.99.0 As a brief (but hopefully helpful) answer, I can confirm that pacmd indeed ignores PULSE_SERVER. pactl, on the other hand, respects PULSE_SEVER. Are you able to use pactl instead? --Sean
