Hi Jean-Philippe, On 19-04-17 22:28, MENGUAL Jean-Philippe wrote: > 1st, I have always had the idea the the spd service had bugs and was not > really usable: spent so resource, didn't run really, etc. Hence the fact > it's always been in "no" in defaults/speech-dispatcher. So, does that mean that speechd-up should also have such a mechanism that defaults to no? What I am now seeing is that speech-dispatcher doesn't stay running when started with it's init script. If I start it with "sudo service speech-dispatcher start" than it is in the "active (running)" state for about 20 seconds and then goes to an "active (exited)" state. I expect that speechd-up is failing to start because it actually checks if it can USE speech-dispatcher. Two things that I then noticed, the man page of speech-dispatcher mentions that it needs to be started with the "-d" option to run as daemon (which isn't present in its init file). With debugging information added I then noticed the following in /tmp/speechd-debug/speech-dispatcher.log: [Fri Apr 21 14:10:00 2017 : 638612] speechd: Currently no clients connected, enabling shutdown timer. [Fri Apr 21 14:10:05 2017 : 713820] speechd: Terminating... So it seems speech-dispatcher doesn't want to stay running as daemon. I guess this is the real issue at stake. (Should we reassign?) > 2nd, given this feedback, maybe we may try requesting to the initscript > to wait for some seconds, with a kind of pause parameter? Would it fix > the bug? Just to be sure, you mean pausing in the speech-dispatcher init script, right? Speechd-up already has that. Because of the above, this doesn't help. I even tried it (actually before I found out the above) and it didn't work. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature