[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Description changed: [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. [Impact] 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. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > 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[21][22][23], 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 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech- dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi + should say "hi" through your loudspeakers. If you have no loudspeakers + or if you are testing in a virtual machine, you can use Pavucontrol to + verify that the dummy output device meter shows activity right after you + issue the last command. + [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 ** Tags removed: kinetic ** Summary changed: - Service activation via Systemd socket + [SRU] Service activation via Systemd socket ** No longer affects: speech-dispatcher (Ubuntu Focal) -- 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: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Confirmed Status in speech-dispatcher source package in Kinetic: Confirmed Status in speech-dispatcher source package in Lunar: Confirmed 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. [Impact] 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Patch added: "speechd-jammy.debdiff" https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674811/+files/speechd-jammy.debdiff ** Changed in: speech-dispatcher (Ubuntu Jammy) Status: New => Confirmed -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: Confirmed Status in speech-dispatcher source package in Kinetic: Confirmed Status in speech-dispatcher source package in Lunar: Confirmed 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. [Impact] 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. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > 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[21][22][23], 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 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Patch added: "speechd-kinetic.debdiff" https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674789/+files/speechd-kinetic.debdiff ** Changed in: speech-dispatcher (Ubuntu Kinetic) Status: New => Confirmed -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: Confirmed Status in speech-dispatcher source package in Lunar: Confirmed 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. [Impact] 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. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > 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[21][22][23], 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 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Patch added: "speechd-lunar.debdiff" https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+attachment/5674787/+files/speechd-lunar.debdiff ** Changed in: speech-dispatcher (Ubuntu Lunar) Status: New => Confirmed -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: Confirmed 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. [Impact] 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. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > 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[21][22][23], 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 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Description changed: [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. [Impact] 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. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > 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[21][22][23], 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 'Test case' for more details. This has also been - verified in Jammy by Lissyx[3] and there is a merge proposal[4] for the - Firefox snap that assumes the incorporation of this delta in speech- + verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for + the Firefox snap that assumes the incorporation of this delta in speech- dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Then, systemctl start --user speech-dispatcher.socket snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever - reason (e.g. the user didn't start it manually nor rebooted), then - thesd_listen_fds(0) >= 1 would be false and no regression would be + reason (e.g. the user didn't start it manually nor rebooted), then the + sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 - [3] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New 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. [Impact] 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Description changed: [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] + [Impact] 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, + That can be done by implementing the action of the speech dispatcher + service via a Systemd socket: > 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. + The changes are already merged upstream[21][22][23], 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. + and emit sound — see 'Test case' for more details. This has also been + verified in Jammy by Lissyx[3] and there is a merge proposal[4] for the + Firefox snap that assumes the incorporation of this delta in speech- + dispatcher. - The installed socket needs to be started manually to function correctly, - or else the system needs to be rebooted. + Note: Either the installed socket needs to be started manually to + function correctly or the system needs to be rebooted. - [Reproduction case] + [Test case] - Install the proposed speech-dispatcher from the PPA[3] and the snap[4] - with spd-say. Then, + Install the proposed speech-dispatcher and the snap[5] containing spd- + say. Then, - systemctl start --user speech-dispatcher.socket - snap run --shell geheim - $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi + 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 + [Regression potential] + + If the socket communication were not working (e.g. connection refused), + then this would result in text-to-speech failing, even for a not + sandboxed program. + + Do note, however, that if the socket were not available for whatever + reason (e.g. the user didn't start it manually nor rebooted), then + thesd_listen_fds(0) >= 1 would be false and no regression would be + observed, as then the program would fallback to its usual operation. + + [1] https://github.com/brailcom/speechd/issues/335 + [21] https://github.com/brailcom/speechd/pull/763 + [22] https://github.com/brailcom/speechd/pull/776 + [23] https://github.com/brailcom/speechd/pull/817 + [3] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html + [4] https://github.com/canonical/firefox-snap/pull/12 + [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New 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. [Impact] 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"
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
** Also affects: speech-dispatcher (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: speech-dispatcher (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: speech-dispatcher (Ubuntu Focal) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Jammy) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Kinetic) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Lunar) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: speech-dispatcher (Ubuntu Focal) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Jammy) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: speech-dispatcher (Ubuntu Lunar) Importance: Undecided => High -- 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 Status in speech-dispatcher source package in Focal: New Status in speech-dispatcher source package in Jammy: New Status in speech-dispatcher source package in Kinetic: New Status in speech-dispatcher source package in Lunar: New 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
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 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
[Desktop-packages] [Bug 1991022] Re: Service activation via Systemd socket
Thanks Nathan, uploaded! ** Changed in: speech-dispatcher (Ubuntu) Status: In Progress => Fix Committed -- 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 Committed 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
