http://bugzilla.opensuse.org/show_bug.cgi?id=981271 Bug ID: 981271 Summary: KTTSMgr cannot use festival 2.4 in 13.1 or 13.2 or 42.1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 URL: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2657 OS: Other Status: NEW Keywords: accessibility Severity: Normal Priority: P5 - None Component: Sound Assignee: tiwai@suse.com Reporter: mrmazda@earthlink.net QA Contact: qa-bugs@suse.de CC: anixx@opensuse.org Found By: --- Blocker: --- To reproduce: 1.ensure sound system works reliably 2.install festival and kdeaccessibility3 or trinity-tdeaccessibility from standard repos 3.enable festival with chkconfig (no systemd service for it exists) 4.open a KDE3 or TDE session 5.open KTTSMgr 6.try to add or edit a talker (talker tab) Actual behavior: 1.voice query fails 2.Enable on General tab cannot be selected 3.TTS cannot produce sound Expected behavior: 1.voice query succeeds 2.enabling on General tab is possible 3.TTS works as expected (e.g. speak clipboard) Notes: 1-KDE3's KTTSMgr on 13.1 on host Easystreet made sound until most recent updating, which replaced festival 2.1 with 2.4. Reverting to festival 2.1 from OSS repo restored sound. 2.KDE3' KTTSMgr on 13.2 had never been made to find voices or make sound on host Easystreet. I was only able to make it find voices and make sound after replacing its installed festival 2.4 from KDE3 repo with 2.1 from OSS repo. 3.TDE's KTTSMgr on 42.1 on hosts Easystreet and gx62b would not find voices or make sound until I replaced their festival 2.4 with the 2.1 version from 13.2's OSS repo. 4.TDE's KTTSMgr on Debian stretch on host Easystreet works as expected with its own festival 2.4. Yet to do is figure out why same OS/KTTSMgr/festival on host big41 does not output sound, though it does claim to find voices and appear fully configured to output sound, and other apps do output sound. 5.mailing list thread: http://trinity-users.pearsoncomputing.net/?0::10248 -- You are receiving this mail because: You are on the CC list for the bug.