Hi, I have gotten a bit further, but any time I try to configure Orca, it locks up. It will start with sudo orca or just orca. I made a script that retakes ownership of everything in /home/user and that helped a bit, and got me to this point. I changed the hotkey so it is not windows alt S, it is just like Narrator, control windows enter. I put a custom user-settings.conf in ~/.local/share/orca but the settings stay as the default. Thanks.
----- Original Message ----- From: "Chevelle" <[email protected]> To: <[email protected]> Sent: Monday, August 18, 2025 1:32 PM Subject: Re: spd-say and orca are silent Well, I assume you restarted ORCA with alt-super-s. If that doesn't work, you could try looking at the Speech Dispatcher logs in /run/user/1000/speech-dispatcher/log. On 8/18/25 11:00 AM, K0LNY ?? wrote: > Well I did a purge as suggested and reinstalled orca, I had also purge > removed speech-dispatcher and python3-speechd. > After reinstalling orca, it seems that orca installed speech-dispatcher > and > python3-speechd. > I had a bit of hope when I rebooted into the Mate desktop, I heard orca > say > screenreader on. > But then it went silent again. > Almost as if there is some process in the Mate desktop blocking orca. > I still have audio, in an edit window, or terminal, I get the drip sound > when I can no longer backspace. > Again, thanks for any suggestions. > Glenn > ----- Original Message ----- > From: "john doe" <[email protected]> > To: <[email protected]> > Sent: Monday, August 18, 2025 2:11 AM > Subject: Re: spd-say and orca are silent > > > On 8/18/25 09:00, K0LNY ?? wrote: >> Hello folks, >> So I have Debian Bookworm and Orca is silent. >> If I do >> spd-say test >> I hear nothing. >> But if I do >> sudo spd-say test >> I hear espeak-ng speak. >> I may have made the mistake of running spd-conf with sudo and selecting >> system after I had trouble with no sudo and user configuration. >> Does anyone have any ideas? >> I did an apt reinstall of speech-dispatcher and a reinstall of orca, but >> that did not fix the problem. > try to "purge" and re"install" `apt-get --autoremove purge <PKG>` and > see if it helps. >
