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 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 brltty to crash, the first thing I do after starting brltty is to
press alt+control+f2 to jump to a text console, which triggers the
error. We've tried tweaking the config file but nothing we do seems to
have any effect. Note that this only happens if the config is correct.
If there are any errors in the config file, such as brltty not being
able to load a speech or braille driver, it doesn't get killed, it just
keeps running. I'm stumped. What steps can we take next to fix this?
A gdb backtrace of the crash would be helpful. That, of course, works best with
an unstripped executable. If you're using the released tarball then that won't
be the case. If you're building your own then the brltty executable in the
build tree won't be stripped. Even with a stripped executable, though, the
backtrace should still be helpful.
Also, please add lines like these to brltty.conf, and then post the log so that
we can have a look at it:
log-file /path/to/logfile
log-level debug
Please also let us know which version of systemd you're using, and post your
brltty systemd service unit(s) as well as your brltty.conf.
If you're building your own brltty, please post config.log (from the top level
of the build tree).
_______________________________________________
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
