Confirmed.
Touch has actually been working for a while on my TX2, so I think this
bug can be closed.
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Confirmed.
Touch has actually been working for a while on my TX2, so I think this
bug can be closed.
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
The touchscreen works now with the new utouch efforts.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Confirmed => Fix Released
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are
** Tags removed: regression-potential
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
not quite. As Shaved Wookie mentioned above, touch moves the cursor
(which it didn't before the kernel update), but doesn't register clicks.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Fix Released => Confirmed
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
http
ok, so this bug seems to be solved then.
you need to file another bug against qt regarding the support there.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Incomplete => Fix Released
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/5
Actually, I just realised - I *do* get pressure for the stylus in GTK
apps. I just forgot to configure extended input devices in Gimp. :-/
Still no pressure in QT apps...
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this
Having updated and restarted today, it seems to give stylus tracking and
clicks, but no pressure (in GTK and QT apps). Touch moves the cursor,
but doesn't seem to register clicks. When I use a self compiled hid-
ntrig.ko for myself, I get pressure in GTK apps and touch clicks, but
currently I only
aiui both the kernel and the wacom x driver have pulled the n-trig
changes, so things should work better?
** Changed in: xf86-input-wacom (Ubuntu)
Status: Confirmed => Incomplete
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
Yo
Also, I actually *am* using the latest dev version of Kubuntu, if you
count updating daily . If you'd like me to download Beta 1 / the daily
iso and test that just let me know and I will.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Invalid => Confirmed
--
Touchscreen working on Lucid
** Attachment added: "udevdb output with (working) compiled hid-ntrig.ko"
http://launchpadlibrarian.net/42124558/udevdb.txt
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member o
I'd also like to add that stylus pressure only works in GTK apps and not
in KDE based ones. My research seems to sugest though that this is a bug
in QT only looking for tablets with particular names that is patched
around in OpenSuse and has a patch accepted to QT 4.6.3 by Lukas Tvrdy.
--
Touchsc
Ok, thanks for the kick in the pants to get this posted. Anyway, I
digress...
I did, in fact, get the touchscreen and stylus working, but only by following
the instructions for Lucid here:
http://ubuntuforums.org/showthread.php?t=1252492
This compiles a new hid-ntrig.ko module as well as changin
We're closing this bug since it is has been some time with no response from the
original reporter. However, if the issue still exists please feel free to
reopen with the requested information. Also, if you could, please test against
the latest development version of Ubuntu, since this confirm
Please attach the _full_ Xorg.0.log after you've plugged it in, and also
the resulting file of 'udevadm info --export-db > udevdb.txt'.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Confirmed => Incomplete
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bug
** Tags added: kubuntu
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
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
> I felt pretty presumptuous second guessing "you" when your little
finger knows more about X than I'll likely learn in the next decade!
Glad to hear I wasn't entirely insane (at least this time).
Triaging bugs is time consuming and tedious so I created scripts to do
it for me. However they're fa
** Tags added: regression-potential
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
This regression is not fixed by xf86-input-wacom.
** Changed in: xf86-input-wacom (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: tx2
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification bec
No improvement so far. I can give logs if needed.
Quick question:
How do I actually try xf86-input-wacom? It's listed at
packages.ubuntu.com as being in main, but Kpackagekit / Synaptic / Apt
don't see any package by that name after updating. I found it on
launchpad, but https://launchpad.net/ub
Thanks Bryce,
I felt pretty presumptuous second guessing "you" when your little finger
knows more about X than I'll likely learn in the next decade! Glad to
hear I wasn't entirely insane (at least this time).
xf86-input-wacom doesn't seem to have made it down the line yet, in fact
after updating
[Sorry, the automatic refiler guessed -ati but it guessed wrong]
Try recent updates. Between alpha-2 and now we've reworked wacom.
Actually now it's provided by a different package xf86-input-wacom,
which uses udev instead of hal.
** Package changed: xserver-xorg-video-ati (Ubuntu) => xf86-input
Gah. After some updates I was able to install xserver-xorg-input-wacom.
No change. Probably the most interesting part was this excerpt from
Xorg.0.log:
(**) Option "Device"
"/dev/input/by-path/pci-:00:13.1-usb-0:2:1.0-event-mouse"
(**) stylus: always reports core events
(**) Option "Mode" "Ab
I don't pretend to know anything about this area. I am curious though,
why would an input device problem would be assigned to the ati video
driver?
I looked through XOrg.0.log and found a whole bunch of references to the
wacom module not being found. That led me to noticing that xserver-xorg-
inpu
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
Touchscreen working on Lucid Alpha 2, Breaks with Recent Upgrades
https://bugs.launchpad.net/bugs/510311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38161840/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/38161841/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/38161842/Dependencies.txt
** A
26 matches
Mail list logo