Bug 995639

Created attachment 785035 [details]
File: backtrace

Created attachment 785036 [details]
File: cgroup

Created attachment 785037 [details]
File: core_backtrace

Created attachment 785038 [details]
File: dso_list

Created attachment 785039 [details]
File: environ

Created attachment 785040 [details]
File: exploitable

Created attachment 785041 [details]
File: limits

Created attachment 785042 [details]
File: maps

Created attachment 785043 [details]
File: open_fds

Created attachment 785044 [details]
File: proc_pid_status

Created attachment 785045 [details]
File: var_log_messages

Have this problem too.

Got this issue by trying to launch Orca on a freshly updated Fedora 20 installation.

Same for me on the latest Fedora 20 from today. 

Following this test case:
https://fedoraproject.org/wiki/QA:Testcase_Gnome_Accessibility

I just turned On/Off the Screen Reader setting and a while later ABRT popped up.

I got the same error here while activating the screen reader.

Package speech-dispatcher-0.8-5.fc20.x86_64

Fedora 20

This has not yet been resolved.

I believe what is happening here is that the festival 'module' subprocess is segfaulting, and that is causing systemd to think the service has failed.

If you start speech-dispatcher on the commandline, like this:

/usr/bin/speech-dispatcher -d

it happily starts up, and all the other modules end up running:

$ ps ax | grep speech
23349 pts/2    Sl     0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy /etc/speech-dispatcher/modules/dummy.conf
23352 pts/2    Sl     0:00 /usr/lib64/speech-dispatcher-modules/sd_generic /etc/speech-dispatcher/modules/generic.conf
23355 pts/2    Sl     0:00 /usr/lib64/speech-dispatcher-modules/sd_flite /etc/speech-dispatcher/modules/flite.conf
23360 pts/2    Sl     0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak /etc/speech-dispatcher/modules/espeak.conf
23365 pts/2    Sl     0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero /etc/speech-dispatcher/modules/cicero.conf
23369 ?        Ssl    0:00 /usr/bin/speech-dispatcher -d

This includes the flite module, which is also for festival - maybe we just need to stop shipping the faulty festival module ?

I disabled the festival module and enabled the flite module in speakd.conf. I started jovie and had speech immediately. I don't know which module was speaking, espeak or flite, but there was speech without any messing around.

The festival module does appear to be the problem.

Curiously, when I run ps ax | grep speech, I get:

4050 ?        Ssl    0:00 /usr/bin/speech-dispatcher -d
4056 pts/1    S+     0:00 grep --color=auto speech

The modules are not shown, as in Comment 17.

Demonstration: https://drive.google.com/file/d/0B0nwzlfiB4aQNmtPVFdIR2FKLWM/edit?usp=sharing

Still happens on first launch of Orca in a clean F20 Final TC2+ (my pre-TC3 smoketest live image) install, but Orca does actually run and work.

All those stupid modules **should not be running to begin with** if they haven't been configured to run, each module is establishing a connection to PulseAudio and keeping it open even when they are quiet, which is completely ruining my digital out.   This is making me so angry.

(In reply to Rudd-O DragonFear from comment #21)
> All those stupid modules **should not be running to begin with** if they
> haven't been configured to run, each module is establishing a connection to
> PulseAudio and keeping it open even when they are quiet, which is completely
> ruining my digital out.   This is making me so angry.

And how is a blind person suppose to be able to use the computer by default if the primary means of them navigating is disabled by default? It's not all about you and I'm sure you, as someone who appears to be an able bodied person, are more than capable of disabling it if you don't need it.

This is off topic for the bug.

same bug happens when you run KDE's screen reader thingy too, FWIW - it's called 'Jovie' (because, I don't know, I guess GNOME doesn't have a monopoly on completely cryptic names for screen readers).

Ran into this when using the "Checker Plus for Gmail" Chrome extension, when it tries to read incoming email.

Confirmed with F20.

I just surf in the Internet with epiphany and Orca enabled.

For me this happens realy often and make normal work nearby impossible :/ (because often orca can not speak anymore).

ONLY the DEFAULT module, and perhaps other activated modules needs to be running.

I never thought my comment on running many, non-configured, modules would be spun into hatred for blind people.  Thanks for that!

Got this crash today in Fedora 20 when I launched Mumble (package "mumble" from the fedora repos). ABRT told me it was already reported here.

I was also listening to some music and the music stopped playing, until I closed Mumble (that may be another problem).

Got this crash today in F20 when testing GNOME Shell > Universal Access > Screen Reader -> ON.

$ rpm -qa speech\*
speech-dispatcher-0.8-5.fc20.x86_64

F20 startup "systemctl start gdm.service" from commandline tty1: while using internet browser, well after startup, ABRT says "speech-dispatcher crashed" "sd_festival killed by SIGSEGV".  I know I have festival installed; I hadn't realized that it was "enabled" to be running in the background.  I don't even use it, or any other speech-synthesis program.

Still crashed, rawhide.

I decide to report this to upstream directly and prepare a small patch later.

Created attachment 866788 [details]
Screenshot of Gnome Control Center  Audio Section

I hope this is solved soon. :/. fedora and speech-dispatcher is a mess.
but i need this so for my orca :/.

Once again, festival crashed while signing in to espn3.com through comcast's "WatchTV" site.  I have no idea why, since I DON'T USE FESTIVAL, or any other screen reader! Should I just disable pulseaudio? Are there any workarounds for this, if not a working solution? Thanks.

'yum remove festival'?

Happens everytime I go to a video streaming website (such as www.twitch.tv) and begin watching a video stream.

Since Comment #18, I have not kept up with this. I had good results then, but did not test it extensively. I hope to get back to it soon and will report my findings.

(In reply to ILMostro from comment #34)
> Once again, festival crashed while signing in to espn3.com through comcast's
> "WatchTV" site.  I have no idea why, since I DON'T USE FESTIVAL, or any
> other screen reader! Should I just disable pulseaudio? Are there any
> workarounds for this, if not a working solution? Thanks.

Disable or remomve orca or what ever screen reader you use and you should be good. I'm looking at a fix for speechd or festival to fix this. Upstream development is a little slow

I started trying speech-dispatcherd.service out again today. I ran:

sudo systemctl enable speech-dispatcherd.service

in order to have s-d start automatically whenever I boot the computer.

After logging in, I ran:

sudo systemctl status speech-dispatcherd.service

The results were not good:

speech-dispatcherd.service - Speech-Dispatcher an high-level device independent layer for speech synthesis.
   Loaded: loaded (/usr/lib/systemd/system/speech-dispatcherd.service; enabled)
   Active: failed (Result: exit-code) since Tue 2014-03-04 21:21:40 MST; 1min 3s ago
  Process: 2051 ExecStart=/usr/bin/speech-dispatcher -d (code=exited, status=1/FAILURE)

Mar 04 21:21:40 desk.home systemd[1]: Starting Speech-Dispatcher an high-level device independent layer for speech synthesis....
Mar 04 21:21:40 desk.home speech-dispatcher[2051]: [Tue Mar  4 21:21:40 2014 : 295879] speechd: Speech Dispatcher 0.8 starting
Mar 04 21:21:40 desk.home speech-dispatcher[2051]: [Tue Mar  4 21:21:40 2014 : 297363] speechd: Can't create pid file in /root/.cache/speech-dispatcher/pid/speech-dispatcher.pid, wrong permissions?
Mar 04 21:21:40 desk.home speech-dispatcher[2051]: Can't create pid file in /root/.cache/speech-dispatcher/pid/speech-dispatcher.pid, wrong permissions?
Mar 04 21:21:40 desk.home systemd[1]: speech-dispatcherd.service: control process exited, code=exited status=1
Mar 04 21:21:40 desk.home systemd[1]: Failed to start Speech-Dispatcher an high-level device independent layer for speech synthesis..
Mar 04 21:21:40 desk.home systemd[1]: Unit speech-dispatcherd.service entered failed state.

I am unable to start s-d at all.

Just so that you know, I am running:

speech-dispatcher-0.8-5.fc20

The only modules I have enabled are:

espeak

This system is very confusing! Although the speech-dispatcher daemon is NOT RUNNING, I can start jovie and the clipboard or a file will be read!

Note that I had to further modify the speechd.conf file in the following way:

LanguageDefaultModule "en"  "espeak"
LanguageDefaultModule "cs"  "espeak"
LanguageDefaultModule "es"  "espeak"

I changed all of them to espeak and uncommented them, since I had gotten an error when starting jovie, stating that sd_festival had crashed, even though festival is NOT an enabled module (see Comment #39). I presumed that it was somehow getting pulled in by the cs and es lines, that are set to festival by default. The error appears to have ceased.

I was wrong about what I said in Comment #39: the error message that sd_festival has crashed STILL DOES occur.

I was using ocular to display a document. I noticed that the commands to speak the whole document and to speak the current page were again present (I had searched in vain for these commands a few months back). As soon as I clicked 'speak current page', an error about sd_festival crashing was generated, but the page was spoken anyway!

Well this may not have to do with orca, because one of the first things I did on my f20 install is remove orca, but I just noticed this error in ABRT, sent it, and got pinged because I was CC'ed.

The bug is commonly triggered by orca, but it is indeed really a bug in speech-dispatcher, and can be triggered by other things that use s-d.

It also happens on Linux, Fedora 20. Not only on Mac OS

I'm still getting this bug often and seemingly randomly.  It's also on F20, not just Mac.

*** Bug 1048739 has been marked as a duplicate of this bug. ***

Just turn on and off the Screen  Reader on Universal Access Panel

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/lib64/speech-dispatcher-modules/sd_festival /etc/speech-dispatcher/modules/festival.conf
crash_function: pthread_cancel
executable:     /usr/lib64/speech-dispatcher-modules/sd_festival
kernel:         3.11.10-301.fc20.x86_64
package:        speech-dispatcher-0.8-5.fc20
reason:         Process /usr/lib64/speech-dispatcher-modules/sd_festival was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

This is just ancient and I, the reporter, have experienced no problems for so long that I can't even recall why I opened this in the first place. I have also migrated (clean install) to Fedora 21, so this is outdated.