And...this problem goes away if I run the same "tail -f" or "read -t 1"
loop on a text-only TTY, or under a "screen" session within a terminal
emulator.
So it's probably a problem with the terminal emulators (MATE terminal
and konsole). I'm guessing screen is able to insulate the TTY
environment
Further info:
This happens even if I start my "tail -f" process or "read -t 1" loop
within a chroot environment running a completely different distro, under
an Ubuntu 18.04 terminal. The distro in question (really a custom from-
scratch distro) has never had this problem when running as the real
Also encountering this issue with "tail -f ", for a log file
produced by a script with a LOT of rapid output.
Similar issues happen with a simple bash builtin like "read -s -t 1 -N 1
": it periodically gets in a state where it immediately reports
"read: 0: read failed: Resource temporarily
