Your message dated Sun, 6 Feb 2011 12:50:54 +1030
with message-id <[email protected]>
and subject line Re: Bug#578075: [xserver-xorg-input-wacom] Stylus and touch
interaction causes jumping cursor
has caused the Debian Bug report #578075,
regarding [xserver-xorg-input-wacom] Stylus and touch interaction causes
jumping cursor
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
578075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=578075
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xserver-xorg-input-wacom
Version: 0.10.5+20100415-1
Severity: normal
--- Please enter the report below this line. ---
When I use my stylus on my Thinkpad X61t, putting any more than the slightest
pressure causes the cursor to jump rapidly back and forth between the stylus
position and the lower-right corner of the screen.
I believe this is the same bug reported here:
http://sourceforge.net/tracker/index.php?func=detail&aid=2952501&group_id=69596&atid=525124
I have the same "bad magic" warnings in Xorg.0.log as the original reporter
there. However, I'm not sure how to apply the patch posted there against the
Debian sources (if it is even compatible) or to build the Git sources into
Debian.
Curiously, this problem is present in both testing (0.10.3+20100109-1)
and unstable (0.10.5+20100415-1), even though the unstable version's number
suggests that it is a very recent Git pull.
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.32-3-amd64
Debian Release: squeeze/sid
500 unstable www.debian-multimedia.org
500 unstable debian.lcs.mit.edu
500 testing security.debian.org
500 testing debian.lcs.mit.edu
500 stable security.debian.org
500 stable debian.lcs.mit.edu
1 experimental debian.lcs.mit.edu
--- Package information. ---
Depends (Version) | Installed
=======================================-+-==================
xserver-xorg-core (>= 2:1.6.99.900) | 2:1.7.6-2
libc6 (>= 2.7) | 2.10.2-6
libx11-6 (>= 0) | 2:1.3.3-3
libxi6 (>= 2:1.2.0) | 2:1.3-4
Package's Recommends field is empty.
Suggests (Version) | Installed
=======================-+-===========
xinput | 1.5.1-1
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Since I haven't seen any followup to this, and all indications from
the upstream tracker are that it was already fixed in the version
that we have in squeeze now, I'm going to close it here.
Cheers,
Ron
On Sat, Apr 17, 2010 at 02:21:45AM +0930, Ron wrote:
>
> Hi Andrew,
>
> On Fri, Apr 16, 2010 at 12:05:51PM -0400, Andrew Gainer wrote:
> > Package: xserver-xorg-input-wacom
> > Version: 0.10.5+20100415-1
> > Severity: normal
> >
> > --- Please enter the report below this line. ---
> >
> > When I use my stylus on my Thinkpad X61t, putting any more than the
> > slightest
> > pressure causes the cursor to jump rapidly back and forth between the stylus
> > position and the lower-right corner of the screen.
> >
> > I believe this is the same bug reported here:
> > http://sourceforge.net/tracker/index.php?func=detail&aid=2952501&group_id=69596&atid=525124
> > I have the same "bad magic" warnings in Xorg.0.log as the original reporter
> > there. However, I'm not sure how to apply the patch posted there against the
> > Debian sources (if it is even compatible) or to build the Git sources into
> > Debian.
> >
> > Curiously, this problem is present in both testing (0.10.3+20100109-1) and
> > unstable (0.10.5+20100415-1), even though the unstable version's number
> > suggests that it is a very recent Git pull.
>
> Yes, that's git HEAD from yesterday ...
>
> If you'd like to bring this to the linuxwacom list, that's probably
> the best place to work out what is going on. Possibly the bug has
> been reintroduced, or possibly it was just never fixed for all devices.
>
> Cheers,
> Ron
>
>
>
>
--- End Message ---
