On Sun, 27 Feb 2022 10:59:33 -0500
gene heskett <gheskett(a)shentel.net> wrote:
someplace in my USB tree, there's at least one,
and probably more, FDTI
usb to serial adaptors that the installer THINKS is a Braille driver, so
it, without asking, installs brltty and orca, the speech enabled screen
reader no one can understand. And it, if you remove the stuff after the
install is done, will NOT reboot past the 10 second mark in the boot log
cuz its stuck looking for that crap and can't find it.
Very damned distracting when its trying to pronounce every key you type
and no one knows how to remove it without filling the boot drive with
/var/log/syslog until the system is unusable because of the lags imposed
by opening the log when its 50+ megabytes 18 hours after the install,
search for the end of it, writing 9 or 10 more lines of error messages
and closing the log, for every keystroke typed.
The only fix I've found that lets my machine stay up for a few days,
(uptime is 7+ days atm) is to find the .conf files in /etc, and direct
all that error output to /dev/null. That leaves one line of errors still
going to syslog about every 20 seconds as something in systemd.d keeps
looking for the speech dispatcher over blue tooth, and there isn't any of
that except the keyboad and mouse.
Sounds like you need to kill the service(s) involved using whatever
systemd's equivalent of rc-update is (or overwrite the service files
with no-ops and then make them unwritable so they can't be changed),
blacklist any kernel modules involved, and possibly write some udev
rules to force the problem device to be properly identified. Rather a
tedious process that would have to start with identifying the problem
device and its USB ID.
E. Liddell