That's odd. This was a different session (I was previously looking at the journal which brltty, started via systemd, was logging to) but I got the same behavior on the display. If I can definitively reproduce it, I'll send you that log.
Justin On Sat, Jul 30, 2022, at 17:23, Dave Mielke wrote: > [quoted lines by Justin Pospical on 2022/07/30 at 16:41 -0700] > >>Okay, so the actual error being logged is: >>> RFCOMM connect error 111: Connection refused > > That's not in the log you sent me. It shows detection of the device and > a successful driver start. > > -- > 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: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke > Phone: +1 613 726 0014 | Canada K2A 1H7 | > _______________________________________________ > 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 _______________________________________________ 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
