Hi Sébastien Sébastien Hinderer schrieb am 20.09.2025, 11:12 +0200: >Running an up-to-date Debian Unstable with the new >pipewire-system-services package installed, speech-dispatcher havinb >been adapted to this so that only one system-wide instance is running. […] >Issue 1: users can't play sound. > >My understanding of the problem: Pipewire's socket, >/run/pipewire/pipewire-0, belongs to root.nogroup and is neither >readable nor writable by others. If I run the following command: >chmod o+rw /run/pipewire/pipewire-0 I suppose this should be discussed directly with the pipewire maintainers, as their systemd unit should set the group to `audio`, IMO. Because I lacked the time to resolve this properly, I currently use pipewire as from the user session and configured speech-dispatcher to use pulse. With pipewire-pulse, I can use the network transparency (or UNIX socket) to get audio from BRLTTY to my user pipewire. But that's more a hack which was quicker in my case. If you come up with a solution, please let me know. I plan to write something on the Wiki page, if noone is faster :). Sebastian
Attachment:
signature.asc
Description: PGP signature