[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: no speech in the console but speech in the mate desktop under Trixie


On 9/13/25 3:47 PM, Nick Gawronski wrote:
Hi, Here is first the alsa search and then the pipewire search. Sep 11 20:07:10 dellinspironn7110 systemd-udevd[581]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 GOTO="alsa_restore_std" has no matching label, ignoring.
Sep 11 20:07:10 dellinspironn7110 systemd-udevd[581]: /usr/lib/udev/rules.d/90-alsa-restore.rules:18 The line has no effect any more, dropping.
Sep 11 20:07:10 dellinspironn7110 systemd-udevd[581]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.
Sep 11 20:07:10 dellinspironn7110 systemd-udevd[581]: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 The line has no effect any more, dropping.
Sep 11 20:07:31 dellinspironn7110 systemd[1]: alsa-state.service - Manage Sound Card State (restore and store) was skipped because of an unmet condition 
check (ConditionPathExists=/etc/alsa/state-daemon.conf).
Sep 11 20:07:31 dellinspironn7110 systemd[1]: Starting alsa-restore.service - Save/Restore Sound Card State...
Sep 11 20:07:31 dellinspironn7110 systemd[1]: Finished alsa-restore.service - Save/Restore Sound Card State.  Sep 11 20:07:34 dellinspironn7110 systemd[1162]: Listening on pipewire-pulse.socket - PipeWire PulseAudio. Sep 11 20:07:34 dellinspironn7110 systemd[1162]: Listening on pipewire.socket - PipeWire Multimedia System Sockets. Sep 11 20:07:34 dellinspironn7110 systemd[1162]: Started pipewire.service - PipeWire Multimedia Service. Sep 11 20:07:34 dellinspironn7110 systemd[1162]: Started pipewire-pulse.service - PipeWire PulseAudio. Sep 11 20:07:34 dellinspironn7110 dbus-daemon[894]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.25' (uid=105 pid=1186 comm="/usr/bin/pipewire -c filter-chain.conf") Sep 11 20:12:27 dellinspironn7110 systemd[1523]: Listening on pipewire-pulse.socket - PipeWire PulseAudio. Sep 11 20:12:27 dellinspironn7110 systemd[1523]: Listening on pipewire.socket - PipeWire Multimedia System Sockets. Sep 11 20:12:27 dellinspironn7110 systemd[1523]: Started pipewire.service - PipeWire Multimedia Service. Sep 11 20:12:27 dellinspironn7110 systemd[1523]: Started pipewire-pulse.service - PipeWire PulseAudio. Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Stopping pipewire-pulse.service - PipeWire PulseAudio... Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Stopped pipewire-pulse.service - PipeWire PulseAudio. Sep 11 20:13:26 dellinspironn7110 wireplumber[1550]: wireplumber: disconnected from pipewire Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Stopping pipewire.service - PipeWire Multimedia Service... Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Stopped pipewire.service - PipeWire Multimedia Service. Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Closed pipewire-pulse.socket - PipeWire PulseAudio. Sep 11 20:13:26 dellinspironn7110 systemd[1523]: Closed pipewire.socket - PipeWire Multimedia System Sockets. Sep 11 20:14:01 dellinspironn7110 systemd[1667]: pipewire-pulse.socket - PipeWire PulseAudio was skipped because of an unmet condition check (ConditionUser=!root). Sep 11 20:14:01 dellinspironn7110 systemd[1667]: pipewire.socket - PipeWire Multimedia System Sockets was skipped because of an unmet condition check (ConditionUser=!root). Sep 11 20:14:01 dellinspironn7110 systemd[1667]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root). Sep 11 20:14:01 dellinspironn7110 systemd[1667]: filter-chain.service: Bound to unit pipewire.service, but unit isn't active. Sep 11 20:14:01 dellinspironn7110 systemd[1667]: wireplumber.service: Bound to unit pipewire.service, but unit isn't active. Sep 11 20:14:01 dellinspironn7110 systemd[1667]: pipewire-pulse.service - PipeWire PulseAudio was skipped because of an unmet condition check (ConditionUser=!root). Sep 12 10:13:02 dellinspironn7110 systemd[5520]: Listening on pipewire-pulse.socket - PipeWire PulseAudio. Sep 12 10:13:02 dellinspironn7110 systemd[5520]: Listening on pipewire.socket - PipeWire Multimedia System Sockets. Sep 12 10:13:02 dellinspironn7110 systemd[5520]: Started pipewire.service - PipeWire Multimedia Service. Sep 12 10:13:02 dellinspironn7110 systemd[5520]: Started pipewire-pulse.service - PipeWire PulseAudio. Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Stopping pipewire-pulse.service - PipeWire PulseAudio... Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Stopped pipewire-pulse.service - PipeWire PulseAudio. Sep 12 10:21:28 dellinspironn7110 wireplumber[5547]: wireplumber: disconnected from pipewire Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Stopping pipewire.service - PipeWire Multimedia Service... Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Stopped pipewire.service - PipeWire Multimedia Service. Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Closed pipewire-pulse.socket - PipeWire PulseAudio. Sep 12 10:21:28 dellinspironn7110 systemd[5520]: Closed pipewire.socket - PipeWire Multimedia System Sockets. Sep 12 17:20:46 dellinspironn7110 systemd[10318]: Listening on pipewire-pulse.socket - PipeWire PulseAudio. Sep 12 17:20:46 dellinspironn7110 systemd[10318]: Listening on pipewire.socket - PipeWire Multimedia System Sockets. Sep 12 17:20:46 dellinspironn7110 systemd[10318]: Started pipewire.service - PipeWire Multimedia Service. Sep 12 17:20:46 dellinspironn7110 systemd[10318]: Started pipewire-pulse.service - PipeWire PulseAudio. 
What can you make of this?  Nick Gawronski
It seems your root/console user has a problem talking to the sound card because of the errors above.  It may not be an accessibility problem.  It seems one of the UDEV errors was fixed a while ago, but your system has something similar. 

https://github.com/alsa-project/alsa-utils/issues/280
You have to search the other errors and see if there is a solution for your system, or possibly ask on a different list. 

Maybe somebody has another idea.





On 9/13/2025 1:20 PM, Chevelle wrote:
Try doing a 'journalctl' as root and look for Alsa or Pipewire errors after boot. 


On 9/12/25 6:10 PM, Nick Gawronski wrote:
Hi, Just did another test and the same thing is happening on the latest development version of the debian-installer so not sure what to do at this point as I still have ssh and mate desktop access with speech just no console sounds what so ever.  Nick Gawronski 

On 9/12/2025 3:15 PM, Nick Gawronski wrote:
Hi, No speech what so ever.  If I ssh into the system and run alsamixer as root I get the error message cannot open mixer: Host is down.  If I login to the mate desktop I get orca working but no speech if I switch back to the console.  Nick Gawronski 

On 9/12/2025 1:12 PM, Chevelle wrote:
On this system I have 'espeakup' and 'speakup-tools' installed. Are you sure you don't have speech in the console, or is it just delayed.  If you login without speech, does it eventually start talking? Go into the Mate/Sound preferences and set the volume to about 65,000. 



On 9/12/25 11:37 AM, Nick Gawronski wrote:
Hi, After doing some test installations it appears that now sound is totally broken in the console even when on a fresh installation on a system where previously sound worked regardless of if you were in the mate desktop and the console but only one at a time now I only get speech in the mate desktop and in the console the same thing no speech and the alsa mixer is down when I try to run it. What information can I provide to help resolve these issues? Nick Gawronski 

On 9/11/2025 3:26 PM, Nick Gawronski wrote:
Hi, I am not sure what update caused this issue to happen but now if I boot into a console I get no speech from espeakup.  If I try espeakup or any console based audio program.  I am able to boot into the mate desktop by starting the lightdm service and orca runs just fine but at a very low volume.  Once I am in the mate desktop I go to a terminal and run alsamixer and set it back to %100 and then run as root alsactl store to save the settings and again I have to do this over and over. If I ssh into my linux system and run alsamixer when the mate desktop is not active and run alsamixer as root I get the message that the mixer device is down.  When I also try to access the speakup console with control and alt and f1 in the mate desktop I also get no speech.  This is why I usually have the mate desktop disabled as i have never managed to get both espeakup and orca working when I would like to do this.  Other then a complete reinstallation what can I do to fix this issue? Nick Gawronski
Reply to: