Re: Sound / voice issues
john doe <[email protected]> Sat, 20 Sep 2025 12:56:44 +0200
| Newsgroups | gmane.linux.debian.devel.accessibility |
|---|---|
| Message-ID | <[email protected]> |
On 9/20/25 11:12 AM, Sébastien Hinderer wrote: > 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. > > This worked all fine before the update > What update? > , namely both Orca and the two > instances of brltty (one to follow the virtual consoles and one to > follow graphical terminals) were all connecting to the speech-dispatcher > server. > > I am now encountering two issues that I believe are independent. I am > happy to report bug if/where appropriate but would like to ask for help > in diagnosing and solving the problem before doing so. > > 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 > > users become able to play sound again, but this has of course to be > repeated after each boot. > You could use rc.local for not having to do this at boot manually! Maybe the debian-user list might help as well! -- John Doe