Comment 2 for bug 1499416

Revision history for this message
Nick Minkler (nick-minkler) wrote :

Thomas: This issue is reproducible simply by attempting to scan a barcode into the xterm window NOT a child process, I was simply indicating that it happened in both places. The USB scanner is acting as a basic character-input device when used like this. There's no special application running it's just detected by Ubuntu as a Symbol Scanner and then I'm opening an xterm window and trying to scan something, at this point xterm completely locks up, can't cntrl-c can't click X to kill it. Have to manually open another terminal and kill the xterm process. However, the Scanner will work properly using any other application that was not launched using xterm. For instance I can launch lxterminal and it accepts the scan as text input just fine, same with a web browser, or leafpad.

Also, this is not an issue on our previous system installation which uses Ubuntu Maverick & has xterm 261-1ubuntu3 installed, it's only happening on Trusty with xterm 297-1ubuntu1.