- Original Message -
> Hi,
>
> for me the Virtual driver (vr) doesn't work, reproducer:
>
> $ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
> $ telnet 127.0.0.1 35752
> cells 20
>
> And nothing happened. It seems the 'vr' driver thinks there is
> no data on the socket received, i.e
- Original Message -
> - Original Message -
> > Hi,
> >
> > for me the Virtual driver (vr) doesn't work, reproducer:
> >
> > $ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
> > $ telnet 127.0.0.1 35752
> > cells 20
> >
> > And nothing happened. It seems the 'vr' driver th
hi all
I think I may have brought this up on this list before, and if so I
apologize for the duplicate. I develop along with the help of the
manjaro developers a disability specific linux distribution called
sonar. I've been trying to replace speakup with brltty as both our
console screen reader
[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
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
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
[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
[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
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: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'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 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
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
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
[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
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]
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
[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
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
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
20 matches
Mail list logo
