Public bug reported:
The system for this bug is running Trusty with xvfb 2:1.15.1-0ubuntu2.7
Xvfb fails to launch after being used for a couple days and I can't see
any reason to why it wont launch.
We have inetd.conf setup to run an x11vnc script with the following
command whenever a
I worked with Zebra on this and was able to get the scanner working by
reducing the USB polling interval on the scanner to 8msec, the default
is to poll every 3msec. I still believe this is a bug in how xterm
accepts input because of the following:
A) This issue does not occur when accepting
Thanks for the response Thomas. The DS4208 has multiple cables that it
can be plugged in with, the xterm issues are when it is plugged in over
USB. RS232 is not used for doing direct-text input.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
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
Thomas,
The characters being sent/received are normal ASCII characters, we're doing
Vin code scanning so it's even in the domain A-Z 0-9 like I said, it was
working fine on an older version of xterm.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks, I'll try running with -k8 and other settings to see if I can't
get it to respond differently!
--
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
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
Here's what xterm is apparently seeing when I scan a barcode and use the
-l option to log the output.
^[]0;isisup@LUBE151: ~^Gisisup@LUBE151:~$ 1G
The 1G is the first 2 printed characters of the barcode in this case,
but there are 15 more it should have kept reading instead locking up.
Using
Any chance a fix for this is being proposed for inclusion into Trusty?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1387346
Title:
cancel -a not working per documentation
Status in
Cups has submitted a patch which can be found here:
https://www.cups.org/str.php?L4513 for the cancel -a issue. Inclusion
of the fix would be great.
- Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Added as: https://www.cups.org/str.php?L4513+P-1+S-2+C0+I0+E0+Q
The fact that I was requested to signup for an account on cups
bugtracker, and then asked to submit directly to them kind of irks me.
Shouldn't a team member from the ubuntu cups team be handling these kind
of requests?
--
You
Public bug reported:
Attempted to cancel all print jobs on the system using cancel -a.
Expected: all print jobs are removed.
What happened:
No print jobs were removed from the system.
Workaround:
I was only able to get the print jobs removed by specifying cancel -a
destination
The man page
Also affected:
lprm -
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1387346
Title:
cancel -a not working per documentation
Status in “cups” package in Ubuntu:
New
Bug description:
13 matches
Mail list logo
