[BRLTTY] some strange issues with brltty 5.3.1

[kendell clark]

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 and the braille display driver. Dave mielke helped
out a lot with the brltty configuration, and for that I'm very greatful.
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.

● brltty.service - Braille Console Driver
   Loaded: loaded (/usr/lib/systemd/system/brltty.service; enabled;
vendor preset: disabled)
   Active: failed (Result: signal) since Fri 2016-05-06 20:59:22 CDT;
16s ago
  Process: 14022 ExecStart=/usr/bin/brltty --pid-file=/run/brltty.pid
(code=exited, status=0/SUCCESS)
 Main PID: 14024 (code=killed, signal=ABRT)

May 06 20:59:20 tigger brltty[14022]: BRLTTY 5.3.1 rev unknown
[http://brltty.com/]
May 06 20:59:20 tigger systemd[1]: Started Braille Console Driver.
May 06 20:59:20 tigger brltty[14024]: BrlAPI Server: release 0.6.4
May 06 20:59:20 tigger brltty[14024]: cannot get input device identity:
js0: Invalid argument
May 06 20:59:21 tigger brltty[14024]: Linux Screen Driver:
May 06 20:59:22 tigger brltty[14024]: key already pressed: 29
May 06 20:59:22 tigger brltty[14024]: key already pressed: 56
May 06 20:59:22 tigger systemd[1]: brltty.service: Main process exited,
code=killed, status=6/ABRT
May 06 20:59:22 tigger systemd[1]: brltty.service: Unit entered failed
state.
May 06 20:59:22 tigger systemd[1]: brltty.service: Failed with result
'signal'.

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?
Thanks
Kendell Clark