[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#859926: speechd-up: fails to install



Hi,

On 2017-04-18 22:27, Paul Gevers wrote:
> 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, sleep 4 works always, sleep 5 always fails (so far).

That's consistent to what I found earlier: systemd restart works after
manually starting speechd-up. The timing influence is interesting.

> The big question is why systemd can't get speech-dispatcher up before
> speechd-up wants to talk to it. One thing I noticed is that
> /etc/default/speech-dispatcher has RUN=no, so starting speech-dispatcher
> with the init script succeeds, but doesn't do anything. I think that
> that may cause the confusion of systemd as the speechd-up init script
> depends on the speech-dispatcher init script.
>
> Setting RUN=yes, allows systemd to start speech-dispatcher, but
> apparently that isn't enough, because it still fails to start
> speechd-up. Speech-dispatcher isn't running anymore after starting
> speechd-up while it was running before calling the init script, so it
> looks like systemd tries to restart speech-dispatcher and fails doing
> that properly.

Interesting, but I'm wondering why starting speechd-up via
start-stop-daemon works. That doesn't take care of any dependencies.

Anyway, I fired up my vm again and switched init systems.
Using systemd-sysv, the installation and daemon start fail.
Using sysvinit-core, the installation completes without any error, but
restarting or starting speechd-up fail:

Selecting previously unselected package speechd-up.
(Reading database ... 113373 files and directories currently installed.)
Preparing to unpack .../speechd-up_0.5~20110719-6+b1_amd64.deb ...
Unpacking speechd-up (0.5~20110719-6+b1) ...
Setting up speechd-up (0.5~20110719-6+b1) ...
[....] Starting Interface between speakup and speech-dispatcher : speechd-up[Wed Apr 19 19:59:28 2017] speechd: Configuration has been read from "/etc/speechd-up.conf"
Starting speechd-up...
To work, speechd-up needs speakup and speakup_soft modules.
They are loaded automatically. If you don't want, type
rmmod speakup speakup_soft
. ok 
Processing triggers for systemd (232-22) ...

$ sudo service speechd-up restart
[....] Restarting Interface between speakup and speech-dispatcher: speechd-upStopping speechd-up and unloading speakup modules...
[Wed Apr 19 20:00:07 2017] speechd: Configuration has been read from "/etc/speechd-up.conf"
Starting speechd-up...
To work, speechd-up needs speakup and speakup_soft modules.
They are loaded automatically. If you don't want, type
rmmod speakup speakup_soft
 failed!

$ sudo service speechd-up status 
[FAIL] Checking status of Interface between speakup and speech-dispatcher: speechd-up apparently not running failed!

$ sudo service speechd-up start
[....] Starting Interface between speakup and speech-dispatcher : speechd-up[Wed Apr 19 20:00:52 2017] speechd: Configuration has been read from "/etc/speechd-up.conf"
Starting speechd-up...
To work, speechd-up needs speakup and speakup_soft modules.
They are loaded automatically. If you don't want, type
rmmod speakup speakup_soft
 failed!

Rebooting the machine doesn't change anything, it still fails.

So the installation works, but the package is still unusable.

I rebooted each time after changing the init system before trying to
install speechd-up. Installing everything below except sysvinit-core
doesn't help when running systemd.
Diffing the package lists, for the record:
38a39
> ii  cgmanager                             0.41-2                            amd64        Central cgroup manager daemon
215a217,218
> ii  initscripts                           2.88dsf-59.9                      amd64        scripts for initializing and shutting down the system
> ii  insserv                               1.14.0-5.4+b1                     amd64        boot sequence organizer using LSB init.d script dependency information
335a339
> ii  libcgmanager0:amd64                   0.41-2                            amd64        Central cgroup manager daemon (client library)
663a668,669
> ii  libnih-dbus1                          1.0.3-8                           amd64        NIH D-Bus Bindings Library
> ii  libnih1                               1.0.3-8                           amd64        NIH Utility Library
1196a1203
> ii  startpar                              0.59-3.1                          amd64        run processes in parallel and multiplex their output
1204c1211,1213
< ii  systemd-sysv                          232-22                            amd64        system and service manager - SysV links
---
> ii  systemd-shim                          10-3                              amd64        shim for systemd
> ii  sysv-rc                               2.88dsf-59.9                      all          System-V-like runlevel change mechanism
> ii  sysvinit-core                         2.88dsf-59.9                      amd64        System-V-like init utilities

Out of curiosity, I then removed systemd completely and kept only
libsystemd0. Speechd-up still fails the same way, so I don't think
systemd can be blamed here.
Manually starting speechd-up with start-stop-daemon still works, but
service restart and stop/restart still fail.
I also noticed that there's a sleep 10 when restarting with service
between the stop and start. Reducing DIETIME to 2 lets me restart
speechd-up via service after launching it with start-stop-daemon,
matching Paul's observations. Doesn't help with start, though.

Now I'm really wondering how people manage to run speechd-up
successfully.


Reply to: