> 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. Problem solved. It was something similar, I put default server into the system wide /etc/pulse/client.conf instead of /home/secondaryuser/.config/pulse/client.conf btw, does using unix sockets safe some system overhead compared to tcp connections? Thanks > On Thu, Feb 13, 2020 at 12:33 PM mailinglisten@xxxxxxxxx > <mailto:mailinglisten@xxxxxxxxx> <mailinglisten@xxxxxxxxx > <mailto:mailinglisten@xxxxxxxxx>> 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. > (...) _______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
