Processing control commands:
> reassign -1 speech-dispatcher
Bug #859926 [speechd-up] speechd-up: fails to install
Bug reassigned from package 'speechd-up' to 'speech-dispatcher'.
No longer marked as found in versions speechd-up/0.5~20110719-6.
Ignoring request to alter fixed versions of bug #8599
Control: reassign -1 speech-dispatcher
Control: retitle -1 breaks with pulse-audio as output when spawned by
speechd-up from init system
Control: affects -1 speechd-up
On 22-04-17 22:01, Paul Gevers wrote:
> On 22-04-17 21:26, Cobra wrote:
>> I was thinking of reassigning to the current speech-di
Hi Cobra,
On 22-04-17 21:26, Cobra wrote:
> On 2017-04-22 19:51, Paul Gevers wrote:
>> On 22-04-17 00:26, Cobra wrote:
>>> The directories are different when starting at boot:
>> This doesn't sound good. I think it shouldn't matter how you call an
>> init-script, it should behave the same. I guess
[CC-ing tts-project@l.a.d.o as they are the maintainer of
speech-dispatcher; although I believe most contributers there also read
d-a11n.]
On 22-04-17 00:26, Cobra wrote:
> Looks like we're chasing a pulseaudio<->speech-dispatcher bug now. Fun.
I concluded the same based on my logs. Although ther
Hi
On 21-04-17 16:21, Cobra wrote:
> The man page states:
> "speech-dispatcher is usually started automatically by client libraries
> (i.e. autospawn), so you only need to run it manually if
> testing/debugging, or when in other explicit need for a special setup."
>
> So this behaviour doesn't s
Hi,
On 2017-04-21 14:18, Paul Gevers wrote:
> 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-dispa
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
Hi,
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.
2nd, given this feedback, maybe we may try requesting to the initscript
to wait for some se
On 4/18/17, Paul Gevers wrote:
> Hi all,
>
> I don't know what to make of it, but when I first start the speechd-up
> daemon by hand, then the init script succeeds (because it finds the
> daemon already running). But now it comes, I then can stop and start the
> daemon successfully, but only when
Hi all,
I don't know what to make of it, but when I first start the speechd-up
daemon by hand, then the init script succeeds (because it finds the
daemon already running). But now it comes, I then can stop and start the
daemon successfully, but only when I am quick enough. This is
reproducible, sl
On 4/17/17, MENGUAL Jean-Philippe wrote:
> Hi,
>
> We're going to have a look, but here I cannot reproduce. On Stretch, I
> install the package without problems. So I am surprised. I may have
> systemd-sysv, indeed, but not much more.
>
Hi.. I follow accessibility lists and thought I recognized t
Hi Jean-Philippe,
On 17-04-17 11:19, MENGUAL Jean-Philippe wrote:
> We're going to have a look, but here I cannot reproduce. On Stretch, I
> install the package without problems. So I am surprised. I may have
> systemd-sysv, indeed, but not much more.
Seems like your system is the only system whe
Hi,
We're going to have a look, but here I cannot reproduce. On Stretch, I
install the package without problems. So I am surprised. I may have
systemd-sysv, indeed, but not much more.
Regards,
Le 16/04/2017 à 22:17, Paul Gevers a écrit :
> Hi
>
> On 16-04-17 21:51, Paul Gevers wrote:
>> I have
Hi
On 16-04-17 21:51, Paul Gevers wrote:
> I haven't figured out the difference yet.
Probably somebody who knows systemd should have a look. I have the
feeling it is interfering with the script and not doing what I read.
I have no clue where to find the input (the service file?) that systemd
is
Hi all,
On 16-04-17 11:32, Cobra wrote:
> I did some tests and installing speechd-up failed the same way.
Same for me.
I added some debugging info to /etc/init.d/speechd-up, and it turns out
that the error is generated because the /proc/$pid in running_pid()
doesn't exist. It should exist as the
Hello
On 04/09/2017 10:10 PM, Samuel Thibault wrote:
Control: retitle -1 speechd-up: fails to install
Hello,
Mika Hanhijärvi, on dim. 09 avril 2017 13:42:36 +0300, wrote:
When I try to install speechd-up package I get this error:
E: speechd-up: subprocess installed post-installation script
Processing control commands:
> retitle -1 speechd-up: fails to install
Bug #859926 [speechd-up] fails to install
Changed Bug title to 'speechd-up: fails to install' from 'fails to install'.
--
859926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859926
Debian Bug Tra
Control: retitle -1 speechd-up: fails to install
Hello,
Mika Hanhijärvi, on dim. 09 avril 2017 13:42:36 +0300, wrote:
> When I try to install speechd-up package I get this error:
>
> E: speechd-up: subprocess installed post-installation script returned error
> exit status 1
Do you happen to hav
18 matches
Mail list logo
