[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
current wacom has that change. ** Changed in: xf86-input-wacom (Ubuntu) Status: Confirmed => Fix Released -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
A new wacom udev rule (or a config snippet, eheh) is needed to let evdev handle it. I've got it in a ppa where it failed to build though, forgot to autoreconf it before building the source package. -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
On Sat, Mar 20, 2010 at 04:38:14PM -, Robert Hooker wrote: > Indeed that is the intended behavior and what I meant by fixes part of > in the changelog, its good to hear evdev does work though! tjaalton > asked me to assign a bug to him reminding him to lock down the wacom > rules so they aren't loaded for all tablet devices so I'm doing that > here. Hi guys, I'm a bit fuzzy on the status of this bug - it sounds like there's still some work needed? Or is it working properly now? -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Indeed that is the intended behavior and what I meant by fixes part of in the changelog, its good to hear evdev does work though! tjaalton asked me to assign a bug to him reminding him to lock down the wacom rules so they aren't loaded for all tablet devices so I'm doing that here. ** Changed in: xf86-input-wacom (Ubuntu) Importance: Undecided => Medium ** Changed in: xf86-input-wacom (Ubuntu) Status: New => Confirmed ** Changed in: xf86-input-wacom (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Now that the freeze has been lifted I upgraded to the new -evdev. Things don't work, but if I move 69-xserver-xorg-input-wacom.rules out of the way and reboot, they work fine with -evdev. So I'd say those rules need to be modified to not be picking up this panel still. ** Also affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
This bug was fixed in the package xserver-xorg-input-evdev - 1:2.3.2-3ubuntu2 --- xserver-xorg-input-evdev (1:2.3.2-3ubuntu2) lucid; urgency=low * 65-xorg-evdev.rules: only set x11_driver for event devices, and also extend to work for tablet devices. Fixes part of LP: #537801 -- Robert HookerMon, 15 Mar 2010 21:05:29 -0400 ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Fix Committed => Fix Released -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Thanks for the explanation. So input_id seems to do the right thing, and the uploaded -evdev should get the device to work mostly (and we just might need to ship more rules for fine-tuning the options) ** Changed in: udev (Ubuntu) Status: Incomplete => Invalid ** Changed in: udev (Ubuntu) Assignee: Martin Pitt (pitti) => (unassigned) -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
It's kind of a semantics problem, it's really a resistive tablet overlay with stylus support connected internally over USB instead of being an actual touchscreen with BTN_TOUCH events. I'm pretty sure evdev will work properly will the device though, and fedora is also assigning evdev initially for ID_INPUT_TABLET devices. Looks like it was just an oversight that that part was missing from the evdev rules. There are proprietary drivers specifically for this device from the manufacturer with xserver 1.7 support that look like they would work, but dell distributes an older version for 9.04/9.10 only - http://www.ideacom.com.tw/DR_UTS6680.htm Here is the old fdi for this device under evtouch in karmic- evtouch raw 50 30 15 true 50 460 7920 750 7660 if evdev doesn't work, xserver-xorg-input-evtouch currently looks like it doesn't work properly unless someone has a manual xorg.conf set up for the device. it only installs a rule to create a symlink for evtouch devices and needs fixing to also load evtouch for the devices and set the default options, and our old fdi's need porting to that udev rule as well. -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Ah, I just noticed your xserver-xorg-input-evdev upload, thus setting this to fix committed. So is treating this touchscreen as a "tablet" actually semantically correct, and we're really just missing setting a driver for it? ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: (unassigned) => Robert Hooker (sarvatt) ** Changed in: udev (Ubuntu) Status: Triaged => Incomplete -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
> ACTION=="add|change", SUBSYSTEM=="input", ENV{ID_INPUT_TABLET}=="?*",
> ATTRS{idVendor}=="056a", ENV{x11_driver}="wacom"
>
> This is reliant on evdev actually being able to drive his device
I'm confused -- if the driver is set to "wacom", why does evdev need to
be able to drive this?
--
Touchscreen doesn't work after karmic->lucid upgrade
https://bugs.launchpad.net/bugs/537801
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
> Also I'm not sure if the udev test needs updating, it assigns it ID_INPUT_TABLET correctly because it does report having a BTN_TOOL_PEN or BTN_STYLUS. But if it isn't a tablet, and really a touchscreen, it should get fixed. Mario, any chance you could attach the output of lshal, so that we can compare? -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
** Tags added: karmic -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Also I'm not sure if the udev test needs updating, it assigns it ID_INPUT_TABLET correctly because it does report having a BTN_TOOL_PEN or BTN_STYLUS. -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Right, it does handle some non wacom tablets and will need to also match
n-trig id's at some point but the non-wacom ones it handles are
accounted for by the pnp subsystem matches at the top. The evdev rules
change was already sponsored by bryce for me but we're in freeze at the
moment. Wacom will need changing to something like this I believe
(syntax is probably incorrect)?
ACTION=="add|change", SUBSYSTEM=="input", ENV{ID_INPUT_TABLET}=="?*",
ATTRS{idVendor}=="056a", ENV{x11_driver}="wacom
This is reliant on evdev actually being able to drive his device which
needs testing though but it should, and I mentioned to him in IRC that
he'll have to keep 69-xserver-xorg-input-wacom.rules out of the way for
now to test it if evdev works before we look at making evtouch work
which previously handled it in karmic but used hal fdi's and hasn't been
ported to udev.
--
Touchscreen doesn't work after karmic->lucid upgrade
https://bugs.launchpad.net/bugs/537801
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Robert,
so the wacom driver isn't meant to drive all tablets, just a few of
them? As long as the wacom rules still have
ACTION=="add|change", SUBSYSTEM=="input", ENV{ID_INPUT_TABLET}=="?*",
ENV{x11_driver}="wacom"
then an evdev catchall won't do anything?
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
Touchscreen doesn't work after karmic->lucid upgrade
https://bugs.launchpad.net/bugs/537801
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Adding an udev task to fix input_id here. I'll investigate the udev dump in detail, I imight come up with some further questions later on. ** Changed in: xserver-xorg-input-evdev (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Also affects: udev (Ubuntu) Importance: Undecided Status: New ** Changed in: udev (Ubuntu) Importance: Undecided => Medium ** Changed in: udev (Ubuntu) Status: New => Triaged ** Changed in: udev (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
Looked into it a bit more.. It looks like the udev is tagging it as
ID_INPUT_TABLET=1 because its a resistive touchscreen not a capacitive
one with BTN_TOUCH, and our /lib/udev/rules.d/65-xorg-evdev.rules is
missing a catchall for tablet devices -
ENV{ID_INPUT_TABLET}=="?*", ENV{x11_driver}="evdev"
currently only the wacom udev rule is matching ID_INPUT_TABLET and its
universally loading wacom which should be tightened down a bit to only
load with a wacom vendor ID (serial tablets from other vendors are
handled before the catchall) to accompany this change.
** Package changed: xf86-input-evtouch (Ubuntu) => xserver-xorg-input-
evdev (Ubuntu)
--
Touchscreen doesn't work after karmic->lucid upgrade
https://bugs.launchpad.net/bugs/537801
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
** Package changed: xf86-input-wacom (Ubuntu) => xf86-input-evtouch (Ubuntu) ** Changed in: xf86-input-evtouch (Ubuntu) Status: New => Confirmed -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537801] Re: Touchscreen doesn't work after karmic->lucid upgrade
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/40842487/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/40842488/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/40842489/Dependencies.txt ** Attachment added: "GdmLog.txt" http://launchpadlibrarian.net/40842490/GdmLog.txt ** Attachment added: "GdmLog1.txt" http://launchpadlibrarian.net/40842491/GdmLog1.txt ** Attachment added: "GdmLog2.txt" http://launchpadlibrarian.net/40842492/GdmLog2.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/40842494/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/40842495/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/40842496/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/40842497/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/40842498/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/40842499/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/40842500/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/40842501/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/40842502/UdevLog.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/40842503/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/40842504/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/40842505/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/40842506/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/40842507/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/40842508/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/40842509/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/40842510/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/40842511/xkbcomp.txt -- Touchscreen doesn't work after karmic->lucid upgrade https://bugs.launchpad.net/bugs/537801 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
