[BRLTTY] Udev being fussy

[Dave Mielke]

[quoted lines by Keith Wessel on 2019/02/01 at 11:54 -0600]

>Since this new display is so portable, I'm sometimes disconnecting it and
>taking it with me, but I find myself having to restart brltty to get it to
>re-connect after plugging it back in. This, of course, was because I was
>running brltty out of system on start-up, not letting the udev rules start
>and stop brltty. 

No, that can't be the reason because the driver does try to reclaim the device.
Perhaps, though, there's a conflict between your manual starting of brltty and
the udev detection which, too, tries to start it.

>My problem is udevd seems to be randomly killing off brltty, even though the
>display is still connected. It'll detect and start up brltty but, several
>minutes later, it'll terminate. 

Your log first says "taking too long", and then, a bit later, "killed". This is
what happens if the udev rules are there but the systemd unit isn't started.
Ever since udev became a component of systemd it expects systemd to do the
scheduling and won't allow anything that it itself starts to run for very long.

This being said, brltty does provide a udev-wrapper script that takes care of
this problem. I'm suspecting, therefore, that you don't have it. Also, there
are brltty systemd units which you also may not have. What does "systemctl
status btrltty" say?

Could you attach a copy of your brltty udev rules file (probably in
/etc/udev/rules.d/), as well as copies of brltty's systemd units (probably in
/usr/lib/systemd/system/), to a message so that we can have a look at them?

-- 
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada  K2A 1H7   |