Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#67420 - [festival] text2wave segmentation fault (core dumped)
Attached to Project:
Arch Linux
Opened by I Said Socks (socks) - Tuesday, 28 July 2020, 02:22 GMT
Last edited by freswa (frederik) - Tuesday, 28 July 2020, 12:42 GMT
Opened by I Said Socks (socks) - Tuesday, 28 July 2020, 02:22 GMT
Last edited by freswa (frederik) - Tuesday, 28 July 2020, 12:42 GMT
|
DetailsDescription:
While `festival --tts <<< test` works (i.e. $ text2wave -o t.wav <<< test [1] 307267 segmentation fault (core dumped) text2wave -o t.wav <<< test (BTW, I first discovered this issue on Feb. 11, 2020. But since I rarely run text2wave, I'm guessing it's probably stopped working since festival 2.5.0.) Additional info: * package version: festival 2.5.0-3 |
This task depends upon
The workaround/solution provided by telegenetic (post id 2606684, idk how to link to it.) did work for me, surprisingly. Patch text2wave thus:
- (let ((wholeutt (utt.synth (Utterance Text ""))))
+ (let ((wholeutt (Utterance Text "")))
However, this smells weird. Because text2wave worked for me early last year, when festival was at version 2.4.x.
I have checked the file festival/examples/text2wave.sh in the source tarball has not changed a bit between 2.4 and 2.5.0.
And that Gentoo Forums post was from 2005, when festival was at 1.x!
Reported upstream: https://github.com/festvox/festival/issues/33