Bug 24225 - espeak does not work as subprocess
Summary: espeak does not work as subprocess
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-23 01:29 CET by Alex Loginov
Modified: 2019-02-14 09:17 CET (History)
3 users (show)

See Also:
Source RPM: espeak, portaudio
CVE:
Status comment:


Attachments

Description Alex Loginov 2019-01-23 01:29:55 CET
Description of problem:
espeak works in console, but not as subprocess of program.
eduactiv8 uses espeak as subprocess and it does not work in my tests absolutely and in tests of other person it works bad: after clicking on 8 letters (sometimes more) it stops as if the eSpeak subprocess stopped accepting new text to process.

Version-Release number of selected component (if applicable): espeak-1.48.04-3.mga7.x86_64.rpm


How reproducible: always


Steps to Reproduce:
1. install eduactiv8 and to try to pronounce for example, abcs
2. it does not speak or speaks temporary

Console output looks not good:

espeak -vru "Привет"
Full dictionary is not installed for 'ru'
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2565:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_route.c:869:(find_matching_chmap) Found no matching channel map
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
ALSA lib pcm_oss.c:377:(_snd_pcm_oss_open) Unknown field port
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams, &alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 924
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams, &alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 924
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
Expression 'parameters->channelCount <= maxChans' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1514
Expression 'ValidateParameters( outputParameters, hostApi, StreamDirection_Out )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1846
[AVAudioResampleContext @ 0x7f451c05e140] Value 320.000000 for parameter 'phase_shift' out of range [0 - 30]
Comment 1 Alex Loginov 2019-01-23 05:30:03 CET
I guess problem is in portaudio, snapshot20161030 is too old.

Source RPM: espeak => espeak, portaudio

Comment 2 Marja Van Waes 2019-01-25 20:09:34 CET
(In reply to Alex Loginov from comment #1)
> I guess problem is in portaudio, snapshot20161030 is too old.

Assigning to all packagers collectively, since there are no registered maintainers for espeak and portaudio.

CC'ing two portaudio committers

CC: (none) => lists.jjorge, marja11, rverschelde
Assignee: bugsquad => pkg-bugs

Comment 3 Alex Loginov 2019-02-14 07:25:53 CET
It works now.

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED

Comment 4 Marja Van Waes 2019-02-14 09:17:59 CET
(In reply to Alex Loginov from comment #3)
> It works now.

I don't understand why this report was closed as wontfix... because no newer portaudio was pushed and espeak is still the same, too?

I prefer closing as "worksforme", because there is no longer anything left to fix.

Resolution: WONTFIX => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.