hi all
I reported a couple of weeks ago that I'm trying to configure brltty as
a console screen reader. It does start and speak now. But it restarts
itself after it speaks it's name and version, and it won't speak on
command. After every five or ten seconds, it will restart, and repeat
it's name an
[quoted lines by kendell clark on 2016/06/09 at 08:56 -0500]
>I reported a couple of weeks ago that I'm trying to configure brltty as
>a console screen reader. It does start and speak now. But it restarts
>itself after it speaks it's name and version, and it won't speak on
>command. After every fi
hi
Got it. I'll set up a log-file setting in our brltty config before
rebuilding another image. I'll attach the log to another message.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/06/09 at 08:56 -0500]
>
>> I reported a couple of weeks ago that I'm trying to c
[quoted lines by kendell clark on 2016/06/09 at 09:12 -0500]
>Got it. I'll set up a log-file setting in our brltty config before
>rebuilding another image. I'll attach the log to another message.
If I'm understanding you correctly, this is happening on other systems - not
your own. That, of cour
hi
This happens on my system as well. It happens most on the live images I
build of sonar and then boot to make sure everything works like it
should. I'm burning the image to a flash drive and I'm also generating
that log you need. I'll attach it to another message to this list.
Thanks
Kendell Clar
hi
I've got the log file. i set the log level to debug, so as to give you
guys as much info as possible. This is from the latest live image build,
booted from a flash drive. Log file is attached.
Thanks
Kendell Clark
Dave Mielke wrote:
> [quoted lines by kendell clark on 2016/06/09 at 08:56 -050
[quoted lines by kendell clark on 2016/06/09 at 10:02 -0500]
>I've got the log file. i set the log level to debug, so as to give you
>guys as much info as possible.
:-( You didn't read. The debug log level just means to log all of the
uncategorized messages. You still need to enable the categor
In the log you posted, brltty looks like it's crashing just after the eSpeak
speech driver started. Since you're saying that you're hearing it speak one
thing, I'm guessing that that's where the crash is. I wonder why I'm suspecting
a Pulse Audio crash. :-(
What happens if you specify the "no"
hi
Oops, sorry about that. It is fairly late so I'll blame it on the hour.
Still, I should've read the entire line before saving and closing. I'll
generate another log file. I'll also use ulimit -c unlimited to see if
I'm getting a core file, and if I am, I'll attach that as well.
Thanks
Kendell Cl
hi
I don't know if it's pulse or not, but I'll get that log file for you.
I'll get the log file, and then I'll specify the no speech driver to see
if brltty stays running.
Thanks
Kendell Clark
Dave Mielke wrote:
> In the log you posted, brltty looks like it's crashing just after the eSpeak
> spe
hi
Got another log file. The log level this time was set to:
debug,speech,brldrv,inpkts,outpkts. Resulting file is attached. I
checked for a core file, but didn't see one. I ran ulimit -c unlimited
before killing brltty with systemd after several restarts.
Thanks
Kendell Clark
Dave Mielke wrote:
[quoted lines by kendell clark on 2016/06/09 at 10:23 -0500]
>It is fairly late so I'll blame it on the hour.
:-) What time zone are you in? Where are you? Your email header shows UTC-5 (so
North America Eastern).
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God
[quoted lines by kendell clark on 2016/06/09 at 10:29 -0500]
>Got another log file. The log level this time was set to:
>debug,speech,brldrv,inpkts,outpkts.
Thanks. By the way: As long as debug is specified, the log level and enabled
categories are logged right up near the top. In your log this
hi
Would you mind looking up the ulimit info? I'm afraid that systemd is
quite complex, and I don't really understand much about it except how to
start, stop and inspect services. What would you like me to do next so I
can help you guys track down what's going on? I think I'll go get some
more coff
In the service section of your unit file type the following (case
sensitive)
LimitCORE=infinity
Hope that helps.
kendell clark wrote:
> hi
> Would you mind looking up the ulimit info? I'm afraid that systemd is
> quite complex, and I don't really understand much about it except how to
> start,
hi
This helps immensely. I'll modify my service file now.
Thanks
Kendell Clark
cov...@ccs.covici.com wrote:
> In the service section of your unit file type the following (case
> sensitive)
> LimitCORE=infinity
>
> Hope that helps.
>
> kendell clark wrote:
>
>> hi
>> Would you mind looking up the
Also, don't attach the core file, just a backtrace.
kendell clark wrote:
> hi
> This helps immensely. I'll modify my service file now.
> Thanks
> Kendell Clark
>
>
> cov...@ccs.covici.com wrote:
> > In the service section of your unit file type the following (case
> > sensitive)
> > LimitCORE=
hi
I believe I have the correct core file. How do I do a backtrace again?
Sorry It's late and I'm exhausted. There are a lot of core files and
coredumpctl is being difficult about giving me the most recent brltty one.
Thanks
Kendell Clark
cov...@ccs.covici.com wrote:
> Also, don't attach the core
[quoted lines by kendell clark on 2016/06/09 at 11:32 -0500]
>I believe I have the correct core file. How do I do a backtrace again?
linux> script
script> gdb /path/to/brltty-executable /path/to/core-file
gdb> bt
gdb> q
script> exit
linux>
The gdb output will be in the file typescript.
--
Dave
19 matches
Mail list logo
