[quoted lines by kendell clark on 2016/05/08 at 06:04 -0500] >It's as if when I mentioned accessibility they glazed over. Oh, well we don't >know anything about that, kind of response.
You shouldn't need to mention accessibility as it isn't relevant in this case. No need to needlessly complciate an issue. Your requirement, plain and simple, is that you need to be able to create audio from an aplpication that's running as root, and why you have this requirement is none of their business. It's no more complicated than that. >What should I do next? Should I contact the pulse audio devs while you guys >look into brltty on your end? But there's nthing for us to be fixing. We're invoking eSpeak via its public interface, and we're doing that correctly. It's eSpeak that's generating the audio, and it, too, is doing that correctly. The fact is that none of us can help it if Pulse Audio chooses to crash just because it doesn't like some condition. Maybe they don't like some condition, e.g. being invoked as root, but since when does a well-designed API crash in such a circumstance. The proper action is to return an error indication so that the caller can handle the failure case. One thing I'd do is tell the PA people what the error message is, and then simply ask them what, exactly, does it mean. They shouldn't need to know anything about what you're trying to do in order to answer this question. It's their error message so they ought to know what it means, and they should freely explain that to you. That's where I'd start. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
