After I read some of these messages again, I realized that my system was
upgraded from Bookworm and not installed fresh. This is why my audio
works for speakup and Nick's doesn't. I installed a Trixie system in a
Virtual machine from.
debian-13.1.0-amd64-netinst.iso. It has the problem where speakup can't
speak. When I compare the systems I notice that files are missing in:
/etc/alsa/conf.d
My upgraded bookworm system has
10-rate-lav.conf
10-samplerate.conf
10-speexrate.conf
50-arcam-av-ctl.conf
50-jack.conf
50-oss.conf
50-pulseaudio.conf
60-a52-encoder.conf
60-speex.conf
60-upmix.conf
60-vdownmix.conf
98-usb-stream.conf
99-pulseaudio-default.conf.example
99-pulse.conf
I was able to fix the virtual machine system by doing
sudo apt install pulseaudio
Now if you type 'amixer' it will work.
sudo apt purge pulseaudio
Now 'amixer' and speakup still worked.
I'm not saying this is the correct solution, but it might be a work-around.
If you read this message from the Debian forum he is asking about
essentially the same problem, but nobody gave him an answer.
https://forums.debian.net/viewtopic.php?t=156266
On 9/21/25 3:26 PM, Nick Gawronski wrote:
Hope this helps.
Hi, I just did the installation with the latest network image written
to the USB stick and the same issue happened. I get speech with orca
and the mate desktop but no espeakup console speech and before I go
installing other voices I like to make sure the default setup works.
I filed an installation-report bug number
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115864 if you want
to take a look at it. Nick Gawronski
On 9/21/2025 11:19 AM, john doe wrote:
On 9/21/25 5:14 PM, Geoff Shang wrote:
On Sat, 20 Sep 2025, 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.
Apologies if I'm missing something, but Trixie was released 6 weeks
ago. In fact, 13.1 is already out.
Is there any reason why you aren't using the release version?
The OP has opened a bug, where the same advice ([1]) was suggested!
To the OP, please link your threads in your bug report.
If you want help, the more context we have the better.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115864
