Re: Sound / voice issues

Try one of these.
https://www.debian.org/releases/reportingbugs

On 9/20/25 3:47 PM, Nick Gawronski wrote:
> Hi, I just did the fresh installation using the RC3 image and once it 
> was completed orca works just fine but no speech what so ever in the 
> console.  Same issue that the alsa mixer is down when I run 
> alsamixer.  The reason I am writing again is to say that this issue 
> should be fixed before the release as well as allowing both orca and 
> espeakup to work side by side if this can be done as when Trixie 
> worked normally before some update I was able to use either orca in 
> mate or the espeakup console setup if at the mate login screen I 
> pressed control and alt and f1.  After I successfully login then no 
> console speech at all.  Now it is the same but no espeakup even at the 
> mate login screen if I press control and alt and f1 but orca works 
> just fine and I do have ssh access as I always install it.  What 
> should I do to get this information to the proper group who can fix 
> it?  Nick Gawronski
>
> On 9/20/2025 12:04 PM, Nick Gawronski wrote:
>> Hi, This is almost the same issue I have where I get orca working in 
>> the mate desktop after a fresh installation but no espeakup working 
>> in the console.  I installed Trixie using the latest RC3 installation 
>> image and get orca working fine once the login screen comes up and 
>> after I login to mate.  If I switch to the console with control and 
>> alt and f1 I get no speech what so ever and alsamixer as root says 
>> that the mixer device is down.  What is the best way to have this 
>> issue looked at as I am able to ssh into the system as root?  Nick 
>> Gawronski
>>
>> On 9/20/2025 6:23 AM, Sebastian Humenda wrote:
>>> 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
>>
>