Hi Martin: I am quite dense, so maybe you already stated the issue and I just missed it. What is the exact issue? Speakup doesn't start on boot? Speakup doesn't run at all? Speakup won't run while gnome and orca are running? If it is the boot issue, zookia posted a link on the speakup list about getting that working. If it's they don't play nice together, you'll need to provide more info because they work just fine together here. But, having said that I don't use gnome, I use i3 and storms i38 scripts and startx. I'd appreciate it if you could clarify the issue please. Kirk On Mon, 2 Sep 2024, Martin McCormick wrote:
It looks like speech-dispatcher is running and was started on boot and is serving all the gnome terminals that is, the first two consoles. They both talk but behave identically as gnome consoles. The remaining 3 consoles are not GUI so are mute right now except for the beep which comes from the sounder on the main board but sound does result if I play noise, tones or anything else through sox so, if speakup was in the output path, it should speak. As I said, I don't want to mess up orca speech since it works fine, just switch inputs to speakup from gnome while I am using the text consoles and then go back to gnome when needed. This installation started as a debian install a couple of years ago in which I got speech going by typing the s character to get a talking installer and then went from there after installing the gnome desktop. I didn't even know that pulseaudio is not the sound system of choice but pipewire is so I'm getting smarter by the minute. I'm still not sure what I am learning, but so far, so good. Martin
