Logs from system-udevd might contain a clue. Hoping someone with more insight into udev's probing might be able to help. In this case, it was one minute after brltty was started by udev that it started complaining, and two minutes after that when udev killed it.
Feb 01 12:05:46 mendo.home.geeber.net brltty[3580]: BRLTTY 5.2 rev unknown [http://brltty.com] Feb 01 12:05:46 mendo.home.geeber.net brltty[3581]: BrlAPI Server: release 0.6.3 Feb 01 12:05:46 mendo.home.geeber.net brltty[3581]: Linux Screen Driver: Feb 01 12:05:46 mendo.home.geeber.net brltty[3581]: NoSpeech Speech Driver: Feb 01 12:05:46 mendo.home.geeber.net brltty[3581]: FreedomScientific Braille Driver: Feb 01 12:06:46 mendo.home.geeber.net systemd-udevd[3129]: seq 1872 '/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2' is taking a long time Feb 01 12:08:46 mendo.home.geeber.net systemd-udevd[3129]: seq 1872 '/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2' killed Feb 01 12:08:46 mendo.home.geeber.net systemd-udevd[3129]: worker [3579] terminated by signal 9 (KILL) Feb 01 12:08:46 mendo.home.geeber.net systemd-udevd[3129]: worker [3579] failed while handling '/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2' I don't see brltty losing any connectivity with the display when I start it as a service rather than letting systemctl handle it. So, why is udevd complaining about communications with the display? Any thoughts appreciated. Thanks, Keith -----Original Message----- From: Keith Wessel <[email protected]> On Behalf Of Keith Wessel Sent: Friday, February 1, 2019 11:54 AM To: [email protected] Subject: Udev being fussy Hi, all, I recently had the exciting upgrade from my very old but very reliable Power Braille 80 to a Focus Blue 5th gen 80-cell display. I'm using the display via USB on my Linux system with brltty, and wow is it ever responsive! I'm using it via Bluetooth on Windows, and it's so nice to have braille on Windows again. 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. So, this morning, I disabled it on start-up, and sure enough system-udevd did its thing, or so I thought. 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. I still haven't found anything conclusive in the output of systemctl status system-udevd to say why it's killing it, but I wondered if there might be a known issue or any suggestions from the list from experience. After this happens, it doesn't always re-detect the display if I unplug and re-connect it to the computer. Sometimes, I have to try a few times. FWIW, I'm running brltty 5.2 on Gentoo. Any thoughts? Thanks, Keith _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
