the thread "pulseaudio and espeakup" beginning with this message :
> > https://lists.debian.org/debian-accessibility/2017/12/msg00089.html
>
> Yes, thus documenting on the wiki, so people can configure it even if
> pulseaudio maintainers prefer not to set it by default.
>
I took a look at the wiki, and it documents running pulseaudio as root.
Would that work?
>From the pulseaudio side, running pulseaudio in system mode has a few
drawbacks:
1. Users can eavesdrop on each other.
2. Any user can DoS others by interfering with pulseaudio.
But it seems to me these drawbacks are not quite avoidable in a a11y
scenario? At least not when using dmix?
--
Saludos,
Felipe Sateler
ng VT.
The second one is a dbus negotiation protocol. It is described
here[1]. Currently it is respected by at least pulseaudio, jack2 and
kodi. The pulseaudio support is implemented in src/modules/reserve*.
[1] http://git.0pointer.net/reserve.git/tree/reserve.txt
--
Saludos,
Felipe Sateler
abled? This information should
appear in the pactl list output.
IIRC, suspension cannot happen as long as any stream is connected, even
when corked.
Saludos,
Felipe Sateler
non-root as Lennart suggested. AFAICT, the only reasong for
running as root is to access the softsynth device, but that could be
managed via regular uaccess and group mechanism like /dev/snd/* does. We
shouldn't require running pulseaudio as root, as it would be better if
espeakup would run unprivileged.
I'll leave it to the espeakup maintainers to adjust severity.
--
Saludos,
Felipe Sateler
ig/pulse/default.pa file:
>
> #!/usr/bin/pulseaudio -nF
> #
>
> # load system wide configuration
> .include /etc/pulse/default.pa
>
> ### unload driver modules for Bluetooth hardware
> .ifexists module-bluetooth-policy.so
> unload-module module-bluetooth-policy
> .endif
>
> .ifexists module-bluetooth-discover.so
> unload-module module-bluetooth-discover
> .endif
>
> How would this break accessibility?
>
My own thought is that if your only speakers are BT, how are you going to
have the screen read if there is no BT?
--
Saludos,
Felipe Sateler
On 3 July 2016 at 16:44, Samuel Thibault wrote:
> Felipe Sateler, on Sun 03 Jul 2016 17:38:58 -0300, wrote:
>> On 3 July 2016 at 16:33, Samuel Thibault wrote:
>> > Felipe Sateler, on Sun 03 Jul 2016 17:31:14 -0300, wrote:
>> >> I think the daemonization needs to mov
On 3 July 2016 at 16:33, Samuel Thibault wrote:
> Felipe Sateler, on Sun 03 Jul 2016 17:31:14 -0300, wrote:
>> I think the daemonization needs to move later as well:
>
> Why?
Because the usual protocol is "fork when ready". This way you can
simply do stuff like:
$ sud
{
- perror("Unable to create pid file");
- return 2;
- }
- }
-
/* initialize espeak */
espeak_Initialize(AUDIO_OUTPUT_PLAYBACK, 0, NULL, 0);
@@ -147,6 +136,16 @@ int main(int argc, char **argv)
return 4;
}
+ if (!debug) {
+ /* become a daemon */
+ daemon(0, 1);
+ /* write our pid file. */
+ if (create_pid_file() < 0) {
+ perror("Unable to create pid file");
+ return 2;
+ }
+ }
+
/* run the main loop */
main_loop(&s);
--
Saludos,
Felipe Sateler
body needing
> espeakup will get an unusable box).
>
> I guess the upgrade path needs something to enable it automatically?
I think it is missing dh_systemd integration: add dh-systemd to
Build-Depends and pass --with systemd to dh.
--
Saludos,
Felipe Sateler
Yes, that works as well. Thanks!
--
Saludos,
Felipe Sateler
Package: libatk-wrapper-java-jni
Version: 0.33.0-4.1~
Severity: serious
Justification: Crashes programs using this library
Hi,
I have been experiencing crashes on netbeans, with SIGSEGV on startup. I
managed to trace this to libatk-wrapper-jni. I applied the following
patch to make this work:
--
11 matches
Mail list logo
