[pulseaudio-discuss] multiuser access using sockets not working

Russell Treleaven rtreleaven at bunnykick.ca
Thu Feb 13 18:56:14 UTC 2020

Maybe the main user doesn't know the path to the socket.
As the main user try `pactl --server=/tmp/pulse-server info`
If that works it confirms my suspicion.

On Thu, Feb 13, 2020 at 12:33 PM mailinglisten at posteo.de <
mailinglisten at posteo.de> wrote:

> Dear list,
> I run a user in a desktop environment (KDE5) that starts pulseaudio.
> I´d like to grant other users on the same machine access in order to run
> audio applications from a terminal with those users. And I would like to
> achieve this using Unix sockets.
> Some web sites suggst to try this:
> client.conf=>
> default-server = unix:/tmp/pulse-server
> default.pa=>
> load-module module-native-protocol-unix auth-group=audio \
> auth-anonymous=1 socket=/tmp/pulse-server
> That doesn´t work correctly. Actually the terminal users get access to
> the main pulseaudio process, but, the main user, logged into KDE does
> not get sound, though he started the pulseaudio daemon.
> All users are in group audio. And there´s no bogus
> $HOME/.config/pulse/{client.conf,default.pa}  files either.
> I´m using pulseaudio version 11.1 with kernel 5.4.7
> Thanks for any hint!
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss


Russell Treleaven
sip:rtreleaven at sip.bunnykick.ca;transport=tcp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20200213/f21754c5/attachment.htm>

More information about the pulseaudio-discuss mailing list