Comment 9 for bug 1499416

Reading the manual, I see that the DS4208 is talking via RS-232, which would make xterm's
role in this mostly as a bystander, since (unless you've made your keyboard the serial device,
it would only be echoing something).

The -l option doesn't show me much either, except for your shell prompt (which looks a
little odd with the doubled ^G and the tilde). Perhaps if you had added that as an attachment,
I could see better what it's recording. However, what that records is a little downstream of
the actual input -- it's possible that something is lost in the story. As I noted, the usual problem
is due to some incomplete control sequence, for which there are documented workarounds.

"accepting input as root" raises the possibility that your shell prompt isn't the same, and
that there's something amiss there. A "typescript" from "script" (as an attachment) would
show what is sent to the terminal, and is helpful in spotting broken control sequences.

Capturing all of the input sent from the scanner is harder, since that's received in xterm
as a series of X events - which are processed into characters.

There are perhaps better ways to trace this, but generally I build xterm with a debugging
trace, which would show all of the input events.