desktop-packages team mailing list archive

[Thomas Dickey <dickey@xxxxxxx>]

This sounds like a problem with the application rather than xterm.
For instance, there are a few applications which have hardcoded
escape sequences for Linux console's nonstandard color palettes.
XTerm has a workaround for that (the brokenLinuxOSC resource setting).

Some other applications do... interesting things because they do not
know about 8-bit controls.  Again, xterm has a workaround for those
(the allowC1Printable resource setting).

Finally, there are others which (again relying upon some misfeatures
in Linux console) can be worked around using brokenStringTerm.

These are all in the manpage - http://invisible-
island.net/xterm/manpage/xterm.html

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xterm in Ubuntu.
https://bugs.launchpad.net/bugs/1499416

Title:
  xterm freeze when accepting input from usb scanner

Status in xterm package in Ubuntu:
  New

Bug description:
  I have a symbol DS4208 Wired USB barcode scanner hooked up to a
  machine running Ubuntu 14.04 via a USB connector.  When using xterm
  and attempting to scan a 1D or 2D barcode the xterm window will accept
  in a couple characters from the USB scanner not in the correct order,
  and then lockup. The number of characters accepted varies, and is
  never in the correct order.

  This also happens from any child process launched from the xterm
  window.

  This issue is not present when I first sudo -s to obtain a root shell.
  Scans will be interpreted properly and characters are entered into
  child processes, or command line correctly depending on where the
  cursor is situated.

  This issue is not present in other terminal emulators such as
  lxterminal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1499416/+subscriptions