** Tags added: jaunty
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: xorg-server
Status: In Progress = Fix Released
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: xorg-server
Status: Confirmed = In Progress
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: xorg-server
Status: Unknown = Confirmed
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=21630
Importance: Unknown
Status: Unknown
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Mathieu, upstream would like you to record the signals that the barcode sends
so they can trigger
the bug on their machines without having access to hardware (also useful for
regression tests etc).
I've tried to outline the process for you below (let me know
if any of the steps doesn't seem to
Thanks a lot for collecting all the necessary information. I have filed
an upstream bug report for the input subsystem in X.org. The upstream
bug report is available here:
https://bugs.freedesktop.org/show_bug.cgi?id=21630
It would be useful if you added yourself as a subscriber to that bug so
Nice work Mathieu. This is the stuff we need except for one thing, the
stacktrace seems to be missing function names and variables for the
evdev driver. This can be fixed quite easily though. Please add these
lines to your /etc/apt/sources.list file:
deb http://ddebs.ubuntu.com jaunty main
Martin, thanks for your easy to understand messages.
Here is the new backtrace. Good luck with it!
(both Ubuntu 8.04 and 8.10 are OK with this barcode reader, only 9.04 do
crash)
** Attachment added: gdb-Xorg.txt
http://launchpadlibrarian.net/26454608/gdb-Xorg.txt
--
Barcode reader kill X
Bryce, Martin, thank you.
Please find requested data in the attached file:
gdb-Xorg.txt
lspci-vvnn
lsusb-v
Xorg.0.log
Xorg.0.log.old
xorg.conf
If there is any other needs just let me know.
** Attachment added: 370851.tar.gz
http://launchpadlibrarian.net/26418960/370851.tar.gz
--
Barcode
Hi mathieu-benippon,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
(and maybe Xorg.0.log.old) file from after reproducing this issue. If you've
made any customizations to your /etc/X11/xorg.conf please attach that as well.
[This is an automated message.
@Mathieu, can you also attach gdb to the X process and collect a full
backtrace when it crashes? This would be super useful when we file an
upstream bug report. Instructions on how to record a backtrace is
available here: https://wiki.ubuntu.com/X/Backtracing
** Tags added: crash
--
Barcode
Barcode scan only kills X server, not the console tty.
** Package changed: ubuntu = xorg-server (Ubuntu)
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just tried, and the barcode scanner does work perfectly in console tty.
I believe this bug is well related to X.org, then.
--
Barcode reader kill X on scan
https://bugs.launchpad.net/bugs/370851
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
14 matches
Mail list logo
