Bug#911120: espeakup fails to install

[Keith Barrett]

On 15/10/18 22:02, Samuel Thibault wrote:
> Hello,
> 
> Keith Barrett, le dim. 14 oct. 2018 16:50:08 +0100, a ecrit:
>> I removed the package with a view to reinstalling but
>>
>> invoke-rc.d: initscript espeakup, action "start" failed.
> 
> Mmm, perhaps you just need to have the speakup_soft module loaded?
> 
> I.e. just run modprobe speakup_soft before this.
Right, no joy, unfortunately.

sudo modprobe speakup_soft
No error message.

sudo apt-get install espeakup
Reading package lists...
Building dependency tree...
Reading state information...
espeakup is already the newest version (1:0.80-10).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Setting up espeakup (1:0.80-10) ...
update-rc.d: warning: start and stop actions are no longer supported; 
falling back to defaults
Job for espeakup.service failed because the control process exited with 
error code.
See "systemctl status espeakup.service" and "journalctl -xe" for details.
invoke-rc.d: initscript espeakup, action "start" failed.
● espeakup.service - Software speech output for Speakup
    Loaded: loaded 
(#]8;;file://debian/lib/systemd/system/espeakup.service#/lib/systemd/system/espeakup.service#]8;;#; 
enabled; vendor preset: enabled)
    Active: activating (auto-restart) (Result: exit-code) since Mon 
2018-10-15 23:15:52 BST; 17ms ago
      Docs: #]8;;man:espeakup(8)#man:espeakup(8)#]8;;#
   Process: 3089 ExecStart=/usr/bin/espeakup -V ${VOICE} 
#[0;1;31m(code=exited, status=2)#[0m
dpkg: error processing package espeakup (--configure):
  installed espeakup package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
  espeakup
E: Sub-process /usr/bin/dpkg returned an error code (1)
espeakup -d
Unable to open the softsynth device no such file or directory



> 

> I'll make espeakup to just load the module itself to avoid that issue.
> 
> 
> If that's not the issue, you can try to run espeakup by hand to see
> which error shows up:
> 
> espeakup -d
> 
> Samuel
>