Well here's an update. It seems that Bullseye no longer uses /etc/rc.local, I created the file, but my command: sudo /usr/bin/speakupconf load didn't work. So I put it in crontab sudo crontab -e and I added: @reboot sudo speakupconf load
and my saved settings get loaded. But it is back to using eSpeak. spd-say test, without sudo is still silent but with sudo, I get Voxin. So, espeakup, or just speakup, whichever I'm using, is not runing as sudo, which I wonder is why it is defaulting to espeak. Any ideas on fixing this? Thanks. Glenn ----- Original Message ----- From: "K0LNY_Glenn" <glenn@ervin.email> To: "Samuel Thibault" <sthiba...@debian.org> Cc: <debian-accessibility@lists.debian.org> Sent: Wednesday, November 02, 2022 1:19 PM Subject: Re: Voxin Almost Works Where here is a bit of change that happened since my last message. I installed git, and did the gitclone for speakup. This was after I just uninstalled espeakup. So the gitclone of speakup gave me no errors, but speakup does not work. However, when I do spd-say test now, Voxin works, I just don't seem to have a screenreader. I got speakup with: git clone https://github.com/linux-speakup/speakup.git speakupdir I got it from github because my apt install could not locate the package speakup. Glenn ----- Original Message ----- From: "Samuel Thibault" <sthiba...@debian.org> To: "K0LNY_Glenn" <glenn@ervin.email> Cc: <debian-accessibility@lists.debian.org> Sent: Wednesday, November 02, 2022 1:12 PM Subject: Re: Voxin Almost Works K0LNY_Glenn, le mer. 02 nov. 2022 13:07:05 -0500, a ecrit: > I just looked, the other day you suggested I increase the log level, and > at > that time in speechd.conf I changed it to 4, it says 5 is not recommended > so > you are still getting level 4, I just checked. 4 should be enough, yes. So, are the log files really completely empty after having run spd-say? Samuel