hi
Looking at the build script, it looks like espeak ng uses pulse audio
first, and if that fails it will use port audio.
Thanks
Kendell Clark
On 5/8/2016 6:13 PM, Dave Mielke wrote:
[quoted lines by kendell clark on 2016/05/08 at 17:41 -0500]
I'm using the espeak fork called espeak ng.
[quoted lines by kendell clark on 2016/05/08 at 17:41 -0500]
>I'm using the espeak fork called espeak ng. Espeak was forked about a
>year ago because the original developer, jonathan duddington, stopped
>responding too all attempts to get ahold of him. The fork has a lot of
>the older espeak remov
hi
That's an option. Have a hybrid approach, one part in kernelspace and
one part in userspace? I'm no expert on this by any means, but it's an
option. I'm still going to try to get the pulse folks to fix their bug,
and it is their bug. If I can, it will fix a bunch of issues that were
nearly impos
hi
Oops, I forgot that step. I'll do that now. Sorry for that mistake lol.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/05/08 at 07:06 -0500]
>
>> I don't have a backtrace, yet. I'm still trying to find this illusive
>> core file. No idea where it's at
> Did y
hi
I'm using the espeak fork called espeak ng. Espeak was forked about a
year ago because the original developer, jonathan duddington, stopped
responding too all attempts to get ahold of him. The fork has a lot of
the older espeak removed, including the wx widgets that used to be
needed to compile
[Dave]
[...]
> Yes, running Pulse Audio as a system daemon will resolve your problem. That's
> exactly what I myself do. Note that you'll still need to put root into the
> pulse-access gtroup.
I also did need to put the pulse user into the audio group. Before
doing that, I only got access to t
On Sun, 8 May 2016, Dave Mielke wrote:
> Are you building eSpeak or are you using a prebuilt package? I don't (at
> least
> yet know what options it has, but it may need to be rebuilt to use ALSA
> rather
> than PA.
Note that when PA is installed, the default ALSA pseudo device routes
audio
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/05/08 at 07:06 -0500]
> >and this coredumpctl utility is turning out to be a bit difficult to use.
>
> That's only for when systemd is being used.
I needed to use it last week.
Just running coredumpctl as root will show you all of t
[quoted lines by kendell clark on 2016/05/08 at 07:06 -0500]
>I don't have a backtrace, yet. I'm still trying to find this illusive
>core file. No idea where it's at
Did you first do "ulimit -c unlimited"? The usual default is to impose a size
limit on core files of 0 so they don't get created
[quoted lines by kendell clark on 2016/05/08 at 07:04 -0500]
>I didn't mean shame literally, I meant ... if they start
>to blow me off you could say something that would convince them to help.
Maybe. I don't possess any special powers. :-)
>I think what I'll do first is try to get this fixed at
hi
I don't have a backtrace, yet. I'm still trying to find this illusive
core file. No idea where it's at and this coredumpctl utility is turning
out to be a bit difficult to use. I'll keep at it though. Just about to
sleep now, but I'll pick back up with this in the afternoon when I wake up.
Thank
hi
Good points, all of them. I'm tired, it's nearly 7 AM and my brain's a
little fuzzy. I didn't mean shame literally, I meant ... if they start
to blow me off you could say something that would convince them to help.
I think what I'll do first is try to get this fixed at the pulse level.
If that f
[quoted lines by kendell clark on 2016/05/08 at 06:46 -0500]
>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
[quoted lines by kendell clark on 2016/05/08 at 06:34 -0500]
>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?
I myself don't like hanging out on IRC channels because it means that I have to
read thro
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
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
[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 complcia
hi
Thank you very much for offering to help me. I'll gladly accept. I've
tried working with the pulse people before, and while they didn't blow
me off, they seemed a little bit ... reluctant to help. It's as if when
I mentioned accessibility they glazed over. Oh, well we don't know
anything about t
[quoted lines by kendell clark on 2016/05/07 at 23:22 -0500]
In my opinion - for what it may not be worth - it's a Pulse Audio issue and I
find myself sympathizing with the Speakup people's position. In any event, the
more important issue, by far, is that your problem be resolved. To that end,
hi
oh no, I didn't mean to insinuate that you guys were squabbling at all.
My ire falls squarely on the pulse audio people for not swallowing their
pride and working with other software projects to make sure they can all
play nicely together. Having said all of that, I'll try to run
pulseaudio in
[quoted lines by kendell clark on 2016/05/07 at 18:48 -0500]
>Yup, speech-driver = no fixes the problem. Of course then there's no
>speech, but this'll get fixed so I'm not worried about it. Is there
>anything else I can do to help? I'm the one who reported it it seems
>only fair that I do as much
kendell clark wrote:
I've never been able to get this to work. Is there a guide I can follow
to try this?
It has been a very long time since I played with pulse. There might be
something on the arch wiki though.
___
This message was sent via the B
hi
I've never been able to get this to work. Is there a guide I can follow
to try this? If this fixes the problem I'll just run pulse in system
mode in sonar. This will only be a temporary fix though. Espeakup needs
a maintainer since the original developer is deceased, and of course no
one has ste
kendell clark wrote:
> Speakup has never played very nice with pulse audio. The issue seems to
> be that after you log in, all speech in the console stops.
Running pulse in system mode was supposed to have fixed that. Is this no longer
the case?
___
Th
hi
Speakup has never played very nice with pulse audio. The issue seems to
be that after you log in, all speech in the console stops. I've tried
going to both the speakup and the pulse audio channels but rather than
trying to fix the problem, they both seem content to squabble over who's
bug it is.
kendell clark wrote:
> Of course then there's no
> speech, but this'll get fixed so I'm not worried about it.
Why would you want speech in Brltty anyway, when you have speakup? Brltty's
primary purpose is for driving braille devices.
Just wondering.
___
hi
Yup, speech-driver = no fixes the problem. Of course then there's no
speech, but this'll get fixed so I'm not worried about it. Is there
anything else I can do to help? I'm the one who reported it it seems
only fair that I do as much as I can to help you guys solve it.
Thanks
Kendell Clark
Dav
[quoted lines by kendell clark on 2016/05/07 at 01:13 -0500]
>I might finally have something. Here's a typescript of launching brltty
>with the -n option via sudo. It seems to fail when interfacing with
>pulseaudio.
Yes, I agree. It looks like brltty itself isn't crashing so a bactrace probably
[quoted lines by kendell clark on 2016/05/07 at 01:36 -0500]
>I use the systemd service file that comes with brltty. Or to be
>correct, I use the one that comes in the brltty package. Are they the
>same file?
The one that comes in the tarball for teh release you're using is the correct
one. Sou
hi
I use the systemd service file that comes with brltty. Or to be correct,
I use the one that comes in the brltty package. Are they the same file?
I don't modify systemd files unless I know what I'm doing, and I usually
don't.
Thanks
Kendell Clark
On 5/6/2016 11:34 PM, Dave Mielke wrote
hi
I might finally have something. Here's a typescript of launching brltty
with the -n option via sudo. It seems to fail when interfacing with
pulseaudio. Here's the script attached. I'll still get that backtrace
for you if you want as well.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines
[quoted lines by kendell clark on 2016/05/06 at 23:33 -0500]
>Where would the core file be stored when and if it crashes? The directory
>where I am when it's launched? Thanks Kendell Clark
Yes.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0
[quoted lines by kendell clark on 2016/05/06 at 23:10 -0500]
Are you using the systemd service unit that comes with brltty or did you write
your own?
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bi
hi
Gotcha. Sorry for my ignorance. Where would the core file be stored when
and if it crashes? The directory where I am when it's launched?
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/05/06 at 23:10 -0500]
>
> No, it doesn't exit. It goes into the background.
[quoted lines by kendell clark on 2016/05/06 at 23:10 -0500]
No, it doesn't exit. It goes into the background. If you do ps, you'll see it.
If you'd like it to stay in the foreground then use its -n option.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone:
hi
Now this is odd. When running brltty manually, I get brltty speaking in
a very monotonic espeak voice, brltty 5.3.1 rev unknown, then
immediately returning me to my prompt. It doesn't seem to crash, it just
immediately exits. Running echo $?, which prints out the exit code of
the last run comman
hi
You know, that's definitely a better approach. I'll do that now, and
then generate a backtrace. Sometimes I wonder where my brain is, I never
even considered doing that lol.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/05/06 at 22:11 -0500]
>
> Why not try t
[quoted lines by kendell clark on 2016/05/06 at 22:11 -0500]
Why not try to run brltty by hand, rather than by systemd, to see if you still
get the problem. If you do, then getting a core file is much easier.
>From the shell that you'll start brltty from, do: ulimit -c unlimited
That removes an
hi
I'll try all of those. Thanks for the pointers. I'll first try disabling
the speech driver. If it still crashes, I'll re-enable the speech driver
and disable the braille driver. If it still does I'll disable the brlapi
server. We'll get this figured out eventually.
Thanks
Kendell Clark
Dave Mi
[quoted lines by kendell clark on 2016/05/06 at 21:45 -0500]
Something else I think would be worth trying is to eliminate components. You
could try with "speech-driver no", for example, to see if the crash is being
caused by the speech driver (or, maybe, eSpeak). You could try with "no-api
yes"
hi
I think this is where I had trouble last time. I couldn't find a core
file. I kept running into references to coredumpctl, but couldn't figure
out how to get systemd to cough up the core file. When brltty crashes
I'm not seeing a core file anywhere. There's a /proc/kcore file, but
that's the fil
[quoted lines by kendell clark on 2016/05/06 at 21:53 -0500]
>As soon as I get a command to generate a backtrace i'll do it and attach that
>to an email to the list as well.
You'll need to be sure you're getting a core file from the crash. Then:
linux> gdb /path/to/brltty /path/to/core
gd
[quoted lines by kendell clark on 2016/05/06 at 21:45 -0500]
>Can you give me a command to run to get the log you need? I'm adding the lines
>to brltty.conf right now.
Adding those lines will do it. The log-file directive tells brltty to create
the log file, and the log-level directive tells it
hi
I've got the brltty log file. I'm attaching it to this email, compressed
so it doesn't take up as much space. As soon as I get a command to
generate a backtrace i'll do it and attach that to an email to the list
as well. On second thought, it's only 20 kb so I'll leave it
uncompressed, especiall
hi
First, I'll run a backtrace on the stripped executible, since it's the
system installed copy. Can you give me a command to run to get the log
you need? I'm adding the lines to brltty.conf right now.
Thanks
Kendell Clark
On 5/6/2016 9:36 PM, Dave Mielke wrote:
[quoted lines by kendell
[quoted lines by kendell clark on 2016/05/06 at 21:03 -0500]
>But myself and Bernhard have run into a strange error. As soon as brltty
>starts it is immediately killed. The exact error is as follows. Note
>that this is gotten by running "systemctl status brltty" in a command shell.
...
>To get brl
46 matches
Mail list logo
