This bug was fixed in the package speech-dispatcher - 0.11.4-2ubuntu1
---------------
speech-dispatcher (0.11.4-2ubuntu1) mantic; urgency=medium
[ Nathan Pratta Teodosio ]
* patches/systemd-socket-activation: Added.
- Enables activating Speech Dispatcher via a Systemd socket, it's needed
for confined clients to be able to activate the service (LP: #1991022).
* control: remove deprecated lsb-base package.
[ Sebastien Bacher]
* debian/control:
- Build-Depends on libsystemd-dev
* debian/speech-dispatcher.install:
- install the new systemd units
-- Sebastien Bacher <seb...@ubuntu.com> Mon, 15 May 2023 13:43:36
+0200
** Changed in: speech-dispatcher (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to speech-dispatcher in Ubuntu.
https://bugs.launchpad.net/bugs/1991022
Title:
Service activation via Systemd socket
Status in speech-dispatcher package in Ubuntu:
Fix Released
Bug description:
[Description]
Systemd socket activation for Speech Dispatcher.
- Creates the speech-dispatcher.socket;
- Modifies the server so that it can detect it was automatically launched
by that socket activation; and
- Modifies the Autotools files accordingly.
[Rationale]
It's relevance is described in [1], of which I quote the essential
parts [my notes in brackets]:
> Sandboxed applications [snaps] that use Speech Dispatcher currently bundle
it inside of the sandbox, so that each application has its own "private"
instance of Speech Dispatcher running. This works more or less, but it has the
downside that speech dispatcher cannot coordinate simultaneous messages from
multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same
time, the text reading overlaps.
>
> In order to solve this issue, I would really like to give sandboxed apps
access to the Speech Dispatcher instance of the host.
And then,
> The only issue I see is having it auto launch. I think it would
probably be a good step forward for speech-dispatcher to be auto
launched by a systemd socket like other daemons already do on demand.
That way the host speech-dispatcher with it's configuration would be
used by all snaps,
[Additional information]
The changes are already merged upstream[2], but still not released.
I have built and installed the package in Mantic and verified that
running spd-say from inside a snap causes the host's dispatcher to
spawn and emit sound — see 'Reproduction case' for more details.
The installed socket needs to be started manually to function
correctly, or else the system needs to be rebooted.
[Reproduction case]
Install the proposed speech-dispatcher from the PPA[3] and the snap[4]
with spd-say. Then,
systemctl start --user speech-dispatcher.socket
snap run --shell geheim
$ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi
[1] https://github.com/brailcom/speechd/issues/335
[2] https://github.com/brailcom/speechd/pull/763
[3] https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/26035882
[4] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
