Shouldn’t both be installed?
Hmmm 
I don’t think so because before update, I just had espeak-ng and it was working fine. Also as @soundofthunder mentioned it is enough to install espeak-ng:
Why not simply try to install it in addition?
Manjaro extra repository package espeak-ng is working on my system using PulseAudio
PipeWire latest version 1:0.3.83-1 has been released to unstable and testing branches, but not to stable branch yet
packages.manjaro.org – pipewire
$ pamac info espeak-ng | grep Conflicts
Conflicts With : espeak-ng-espeak espeak
1 Like
Since espeak and espeak-ng are in conflict I can just install one of them.
But as you suggested I gave it a try, I mean I uninstalled the espeak-ng and installed espeak from AUR (It seems It compiled it from source).
$ pacman -Qs espeak
local/espeak 1:1.48.04-4
Text to Speech engine for English, with support for other languages
Fortunately, at least espeak shows some log instead of just hanging out:
$ espeak "hello"
ALSA lib pcm_dsnoop.c:567:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_a52.c:1001:(_snd_pcm_a52_open) a52 is only for playback
ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Any suggestion?
I would think it’s worth a try what package works better for you, then you better can decide what of the both package you like to keep.
I suggested earlier that the issue looks more related to PulseAudio/PipeWire, than with Espeak/Espeak-ng – the @nikgnomic post indicates an espeak conflict; and Pipewire 1:0.3.83-1 would seem to address the issue. We’ll see.
Without resorting to switching branches, the best resolution is now to simply wait until Pipewire 1:0.3.83-1 filters down to Stable; probably only a matter of days; or hours; maybe even now.
Hopefully that will resolve your issue; if not, 
.
Aside:- Interestingly, I haven’t experienced any similar issue with espeak-ng; perhaps never having installed espeak from the AUR has made the difference.
1 Like
Terminal messages are showing attempts to create audio connections to ALSA and JACK but not PipeWire. This is probably from portaudio that is not required by espeak-ng in Manjaro repositories
I installed espeak from AUR to replace espeak-ng from repository. Running espeak from terminal produced similar messages about ALSA and JACK, but espeak worked when it found an ALSA plugin for PulseAudio. If PulseAudio is stopped (systemctl --user stop pulseaudio.socket pulseaudio.service) espeak can also play to an ALSA device via Portaudio
So if the issue is only related to PipeWire, espeak should be able to play to an ALSA device if the systemd units for PipeWire are stopped (pipewire-pulse.socket and pipewire-pulse.service, maybe also wireplumber.service)
PipeWire v0.3.83 is now available on Manjaro stable branch. If that does not resolve PipeWire issue with espeak there is a new version of PipeWire (0.3.84) in unstable branch that should be in the next stable update release
It has been almost a month since we last heard from you. Did either of the newer versions of PipeWire mentioned by @nikgnomic solve your issue?
Oh, sorry for not providing an update.
I just left it without any changes. After that, it worked randomly sometimes. But after 3 or 4 restarts, it is now working normally.
As matter of fact, because of this undeterministic behavior I left it unchanged and didn’t provide any update. It is now working always but I didn’t find what was the problem.
I notice pipewire has received an update, or two, in the meantime. It’s likely one of those corrected the issue, as I previously suggested might happen.
Now that espeak is working for you I have marked mark this thread as solved. Naturally, feel free to change that if you need to. Cheers.
1 Like
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.