The #31 does work for me on a HP tm2 laptop. Anton, perhaps you could
use "uname -r" and " dpkg -s linux-image-3.5.0-16-generic" to verify
that you are running the right kernel with package version
3.5.0-16.25~lp1033783v1 ?
--
You received this bug notification because you are a member of Ubuntu-
I can confirm that installing the 3.6rc5 mainline kernel solves this
issue. I'm marking this bug as affecting the kernel and I'm marking it
invalid for the other packages.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xf86-input-wacom
Status: Ne
I'm trying Anton's suggestion of installing 3.6 now. I will report back
to confirm whether this solves the issue.
Anton, do you have a source for your statement? That may help people
identify the right changeset and maybe backport it to 3.5.
--
You received this bug notification because you are
Off the top of my head: I think that the changes to utouch-grail and
utouch-frame have been committed to trunk, so they are probably in
precise too. I don't think the patch to xserver-xorg-input-evdev (taking
advantage of it) ever got applied.
--
You received this bug notification because you are
** Also affects: xserver-xorg-input-evdev (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-
Bryce: before you spend too much time on it: I cannot immediately
reproduce this last crash in Oneiric. So perhaps you only want to take a
superficial look at it.
I may be able in the near future to switch to Oneiric for 'production';
from that point onwards I'll be able too see if the incidental
I have been running Bryce's patched version of Xorg for a while. I still
experience occasional crashes. However, I haven't succeeded in crashing
X by moving my stylus along the screen like a madman (like what I
described earlier).
I found out that I can reliably produce a crash by running the
fing
Thank you Bryce for finding a possible cause. I'm building your patched
version now. (I couldn't use the ppa because its version doesn't
supersede the version I have installed (2:1.10.2-1ubuntu1.2~utouch1), so
it would cause all drivers to be removed). I will call back here as soon
as I can give mo
Turns out I can more or less reliably reproduce a crash by frantically
moving my pen along the tablet for about a minute or two. That allowed
me to attach gdb and get a backtrace (attached).
It seems that I get a different backtrace at different times. For
simplicity, I will assume it is all relat
Here's Xorg.0.log.old right after a crash. I did install debugging
symbols but I don't see them in the backtrace it contains. Are there any
utouch specific debugging symbol packages I should install?
I could not find the core dump that is mentioned in
https://wiki.ubuntu.com/X/Backtracing. I also
Thanks, I installed the debug symbol packages and will call back here
when I have a backtrace.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/764700
Title:
Xorg crashed with SIGABRT in ut
Hi Chase,
Thanks for taking a look. I still have occasional X crashes ( every 3 -
4 days) with the utouch and utouch-unstable repositories enabled (in
particular, I am using the wacom-dkms module from unstable, and I
uninstalled xserver-xorg-input-wacom). I have no way of telling whether
these are
Chase, sorry for not having had time to provide the files that you
requested. But I can confirm that the issue with the coordinate matrix
has been fixed (by you?) in a recent update (xserver-xorg-input-
evdev=1:2.6.0-1ubuntu12 right now). Thanks!
--
You received this bug notification because you
Wait, I mean [0.0, 0.5] for the touch input.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
multitouch events do not respect swap/invert axes properties
__
Chase: do you have any guess as to why the touch input would be
normalized differently (I'm guessing [-0.5, 0.5]) than the pen input
([0.0, 1.0]) ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.l
Chase: thanks for the wiki article, it is very helpful! I have found
that on my devices, the affine coordinate translation is done in
normalized floating point coordinates and not in pixel coordinates. And
the normalization is different for different devices. For example, to
rotate 180 degrees, I n
** Also affects: utouch
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
multitouch events do not respect swap/invert
Chase: thanks for looking into this again. I also had to explicitely
configure the Wacom device in the Gimp. One would also do so in a real
use case, for the pressure sensitivity.
Your guess about where the bug could be sounds reasonable. Let me know
if there is anything I can help you with.
--
apport information
** Attachment added: "xkbcomp.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940431/+files/xkbcomp.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940430/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940425/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "setxkbmap.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940429/+files/setxkbmap.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "peripherals.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940428/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940427/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.la
apport information
** Attachment added: "locale.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940426/+files/locale.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940424/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940423/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940411/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940422/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https:/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940421/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940420/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940419/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940418/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bug
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940417/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940416/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940415/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940414/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940413/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.la
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/742567/+attachment/1940412/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.la
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
I'm using the (unstable) evdev driver from the utouch ppa
(1:2.6.0-1ubuntu11~utouch2). The bug title says it all: touch and multitouch
events are not translated according to the swap/invert axes properties.
---
Architecture: am
** Bug watch added: SourceForge.net Tracker #3244118
http://sourceforge.net/support/tracker.php?aid=3244118
** Also affects: xournal via
http://sourceforge.net/support/tracker.php?aid=3244118
Importance: Unknown
Status: Unknown
--
You received this bug notification because you ar
This trivial patch to xournal is a workaround. The surrounding code (a
function called 'fix_xinput_coordinates') suggests that this bug has
existed (in xinput? gdk?) for some time already. It just manifests
itself slightly differently with these new packages, which makes
Xournal's workaround fail.
I can reproduce this problem on a fresh daily live-usb with only xournal
and ppa:utouch-team/unstable as extra software. I uninstalled xserver-
xorg-input-wacom to make the evdev driver take over.
I can reproduce it both with my tablet's built-in wacom, and with my
girlfriend's Bamboo Pen&Touch. I
Chase: I'm running cellwriter. I will try to disable it and see what
happens.
My girlfriend has a different Wacom tablet, so I will see if I can
reproduce this with her hardware, too. I will also try a live-usb
(+utouch ppas). I'll post my results here when I've gotten round to it.
One more thoug
Sorry Henrik for my miss-spelling your name. Thanks for your help, I'll
see what I can find out and report the bug elsewhere if needed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://bugs.launchpad.net
Hendrik, do you have any ideas as to where the problem may be? I can
imagine that the problem is over for you when it is not in evdev, but
for me it is not!:-)
As far as I can tell now, gdk_event_get_coords() returns garbage y
coordinates exactly when these events occur. Some layer between evd
Here's an xinput test recording. What strikes me as odd is that there
are motion events with only an a[0] coordinate, and no a[1] coordinate.
This seems related.
As far as I can interpret the wacom-pen2.record, it also seems odd that
an x-axis event is not always followed by a y-axis event, like h
Just one more comment: at first I thought that it could be due to
Xournal, because it has some weird event handling trying to work around
xinput shortcomings. But I can also reproduce in the Gimp.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to x
Thanks for having a look. I found out how to 'play' the recording. The
old recording indeed doesn't show the weird behaviour, but the attached
version does.
** Attachment added: "wacom-pen2.record"
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1930224/+files/wacom-pen2.record
--
** Attachment added: "wacom-pen.record"
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1921145/+files/wacom-pen.record
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/b
Here's the requested evemu properties and recording.
** Attachment added: "wacom-pen.prop"
https://bugs.launchpad.net/utouch/+bug/736500/+attachment/1921144/+files/wacom-pen.prop
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-i
This is working right now with the wacom-dkms package in ppa:utouch-
team/utouch. It does require removing the xserver-xorg-input-wacom
package. However, stylus input continuous to work as well.
It is not yet usable because gesturetest always shows two-finger events,
even when touching lightly wit
I have the same bug on a HP TouchSmart tm2, with the added bonus that
the backlight problems also happen at startup every now and then.
The easiest way I have found to trigger this situation is to set
brightness to 0 on a terminal (as root)
echo 0 > /sys/class/backlight/acpi_video0/brightness
An
53 matches
Mail list logo
