kttsmgr, can't add "command" talker (for espeak)

[Jonathan Duddington]

Binary package hint: kttsd

In order to use the espeak speech synthesizer with kttsd, I need to add a "Command Talker" in kttsmgr. This is not possible (is broken) in Kubuntu 9.10 Alpha6.

In the kttsmgr "Configure" window, I click "Add". In the "Add Talker" dialog, I select the "Show All" radio button next to "Synthesizer". The Synthesizer list now includes "Command" as one of its options.

I select "Command" and click the "OK" button. The "Add Talker" window now closes, instead of allowing me to enter details of the Command Talker.

[Dave Walker (dogatemycomputer)]

I can confirm this bug. Here are the steps necessary to recreate this bug:

1 - Launch KTTSMGR
2 - Click on "Talkers" tab
3 - Click ADD
4 - Click SHOW ALL radio button to the right of SYNTHESIZER
5 - Select COMMAND from the pulldown then click OK.
6 - The window will close without any additional prompting.

This may or may not be a bug. The problem is the language field (which in my case was previously set to "English (United States of America) is de-populated when selecting COMMAND from the SYNTHESIZER pulldown menu. The language menu option should read SELECT A LANGUAGE, the previous language selected should be kept or the user should be prompted for a valid language when trying to click OK to close the window.

WORKAROUND: In step 5 you should also click on the LANGUAGE pulldown and select OTHER from the list.

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Harald Sitter (apachelogger)]

Hi there!

 Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

 Thanks!