Bug 5928

Summary:	speech synthesis stops working after small number of utterances
Product:	Mageia	Reporter:	Neil Darlow <neil>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	alien, marja11, rwobben
Version:	Cauldron	Keywords:	UPSTREAM
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	speech-dispatcher-0.7.1-3.mga2.src.rpm	CVE:
Status comment:

Description Neil Darlow 2012-05-16 12:57:27 CEST

Description of problem:
If, for example, the KDE clock applet is configured to speak the time, it generally speaks the time once and at the next speech interval the dummy output module takes over and indicates that no valid output module is available.


Version-Release number of selected component (if applicable):
speech-dispatcher-0.7.1-3.mga2.i586.rpm

How reproducible:
Every time but some randomness as to when speaking stops.
The steps described below assume default settings are used but the problem occurs even if a talker is added in jovie settings e.g. English|Male 1 (which is the default).

Steps to Reproduce:
1. Ensure jovie is installed so that speech-dispatcher, espeak et. al. are also
2. Use default settings supplied in /etc/speech-dispatcher/speechd.conf i.e. don't configure jovie's settings.
3. Configure the KDE clock applet to speak time under General settings. Say every minute.
4. The time will be spoken initially but at next speech interval or thereafter the dummy module will indicate that no valid output module was found.

Comment 1 Neil Darlow 2012-05-16 13:11:42 CEST

The problem appears to be related to opening the jovie settings module. These Red Hat and KDE bugs describe what I am seeing:

https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=742747
https://bugs.kde.org/show_bug.cgi?id=270478

speech-dispatcher reports the problem but it could be jovie at fault. Go figure!

AL13N 2012-05-16 20:46:14 CEST

CC: (none) => alien

Manuel Hiebel 2012-05-17 01:40:13 CEST

Keywords: (none) => UPSTREAM

Comment 2 Neil Darlow 2012-05-17 10:35:42 CEST

OK, I have it working reliably now by the following method:

1) Disable the systemd-speech-dispatcher service that starts at boot. jovie starts its own instance for the user so a system-wide one is not required and might cause problems (it wastes resources at least).

2) Add jovie to the KDE autostart settings. The clock applet will start jovie if speaking is enabled but it only does it for the session in which it was enabled. Afterwards jovie has to be started explicitly.

3) If any changes are made to jovie's settings e.g. configuring a talker or changing a talker's settings then it seems a reboot is necessary. I haven't investigated this part thoroughly but considering the tender nature of this system a reboot is probably sensible.

Comment 3 Marja Van Waes 2012-05-26 13:01:49 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 roelof Wobben 2013-01-04 12:47:33 CET

Please report whether this bug is still valid for Mageia 2 or Cauldron

Thanks :)

Roelof

CC: (none) => r.wobben

Comment 5 Marja Van Waes 2014-05-04 11:12:40 CEST

This bug was filed against 
speech-dispatcher-0.7.1-3.mga2.src.rpm
and we have 
speech-dispatcher-0.8-10.mga4.src.rpm
in cauldron now.

So closing as old.

Feel free to reopen and adjust the version of the .src.rpm if you still find this problem in fully updated cauldron (there wasn't a lot of action in the upstream KDE bug report)

Keywords: NEEDINFO => (none)
Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD