[BRLTTY] some strange issues with brltty 5.3.1

kendell clark coffeekingms at gmail.com
Fri May 6 22:53:34 EDT 2016


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, especially because not everyone uses a gui with easy
archive extraction tools available.

Thanks
Kendell Clark


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).
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: brltty.log
Type: text/x-log
Size: 20968 bytes
Desc: not available
URL: <http://mielke.cc/pipermail/brltty/attachments/20160506/93aa06ca/attachment.bin>


More information about the BRLTTY mailing list