Unfortunately, I don't have suggestions to offer on this specific
issue. However, given that virtualization seems to be an important
causal factor in both this problem and in your Speakup problems, at
some point the question is whether you can reasonably reorganize your
computing environment so that you aren't running Linux on a virtual
machine. At least, to the extent that you really have to virtualize
it, can you access it via ssh from the host operating system, and
ensure that the host gives you the accessibility you need for the ssh
session?
I have two machines here running different operating systems, neither
with virtual machines installed. I could, of course, take that path,
but I've so far resisted on the basis that the virtualization
introduces additional sources of unreliability that I don't need in
addition to everything else that can and does go wrong.
In your case, would it be more feasible to solve your
virtualization-related problems, or would it be better to make larger
changes so that you don't need to run screen readers on virtualized
guests?
On 4/5/23 09:28, Frank Carmickle wrote:
Greetings Debian accessibility folk,
I'm finding that on power on the sound card is muted. It appears that
alsactl restore is being run, and even if I run it by hand it doesn't
unmute the card. It appears that the card is in a muted state even
though alsa thinks that it is not. Toggling the mute state on and off
causes the audio to work. If I reboot the machine the sound comes up
working. It's particularly an issue with the power on state. I'm
running qemu 7.2 arm64.
Has anyone sorted this trouble out for themselves?
Thanks much.
--FC