hi Now I'm a little confused. Do I need a backtrace after all? I've just run brltty -n to get a copy of the error for the pulse audio people, and brltty crashed, dumped core. However, the file wasn't in my home directory, which is where I was when executing the command. Could a backtrace be helpful after all? Thanks Kendell Clark
kendell clark wrote: > hi > Amen to all that you've said. If I can get this fixed, this will likely > fix speakup's problems as well as a lot of other apps. Would you or some > other programmer be willing to hang out on their irc channel #pulseaudio > on irc.freenode.net in case I need re-enforcements? They have a bad > habbit of either simply ignoring me hoping I'll go away or saying > something to the effect of "not our issue, go bug the other guys. The > other guys being speakup when I mentioned them and espeakup, when I > mentioned that when it couldn't get sound through because pulse audio's > per user setup wasn't allowing it. Pulse audio running in system mode > isn't an option for our distro either. In addition to it being > complicated to set up, I don't like the idea of users being able to > affect other user's sounds and per application volumes being set per > system, not per user. So it's back in the trenches with me. Sometimes I > wish more people did my job ... You've been so helpful thus far I was > hoping you could shame them into helping if that's what it came down to > it. I certainly don't have much luck because I don't know how to get > them to help when they obviously don't really want to. > Thanks > Kendell Clark > > Thanks > Kendell Clark > > > Dave Mielke wrote: >> [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. >> _______________________________________________ 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
