Your message dated Fri, 28 Oct 2016 18:39:19 +1030
with message-id <[email protected]>
and subject line Stylus can lock up left mouse button with no debug trail
has caused the Debian Bug report #741582,
regarding wacom: Stylus can lock up left mouse button with no debug trail
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.)


-- 
741582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741582
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xserver-xorg-input-wacom
Version: 0.23.0+20131011-1+b1
Severity: important
File: wacom

Good evening,

I use a Fujitsu Lifebook T4410, which comes with a built-in touchpad and Wacom
touch + stylus screen. In addition, I use a generic bluetooth mouse (typically
in lieu of the touchpad when I'm using it in laptop mode).

The stylus has these features:
1) tapping the pointy end normally acts like a normal left mouse button click
(LMB);
2) pressing the bottom end of the stylus button and then tapping acts like a
right mouse button (RMB);
3) pressing the top end of the stylus button and then tapping acts like a
middle mouse button (MMB); and
4) the eraser bit at the other end of the stylus appears to act like a left
mouse button click (Eraser).

I was using the stylus in Xournal when I noticed that the left regular LMB was
no longer working. I was still able to draw in Xournal, but tapping outside the
drawing area had no effect at all. The MMB and RMB continued to work normally,
except that I couldn't activate anything because the LMB wasn't working. This
behaviour affected the whole desktop, which is why I'm not filing a bug with
Xournal.

The same behaviour extended to the laptop's touchpad and my Bluetooth mouse:
right clicks, middle clicks and movement continued to work normally, but left
clicks had no response.

Using keyboard commands, I opened a terminal and tailed every log in /var/log/,
including dmesg, syslog, Xorg.0.log, messages, kdm.log, kern.log, debug and
daemon.log. I also tailed ~/.xsession-errors for good measure. None of these
logs had any mention whatsoever of the Wacom drivers during the time period
when the stylus/mouse started acting up. The only message relevant to human
input devices were dmesg entries announcing that my Bluetooth mouse had woken
up and been assigned correctly.

Accordingly, other than my epic on how my mouse got to this situation, I have
no other debugging information to offer.

I went back into Xournal and mashed the RMB and MMB a couple of times and the
LMB started working again (as did the left mouse button on my Bluetooth mouse
and touchpad). For all intents and purposes, my computer is working normally
again.

I should add that this is not the first time the LMB has locked up like this.
Sometimes, the LMB will lock in 'pressed' mode, leading to a persistent drag-
and-drop state. However, I wasn't paying close enough attention the times it
locked up before to give any useful information. I don't know how to reproduce
this problem reliably, but I can assure that it will recur if I keep using my
tablet regularly.

This issue falls into one of two categories:
1) The wacom driver doesn't throw useful logging messages when the LMB locks
up; or
2) There is some sort of bug in the Wacom driver which somehow causes LMBs from
any input source to no longer be acknowledged.

I would be grateful for any direction.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages xserver-xorg-input-wacom depends on:
ii  libc6                                  2.18-4
ii  libx11-6                               2:1.6.2-1
ii  libxi6                                 2:1.7.2-1
ii  libxinerama1                           2:1.1.3-1
ii  libxrandr2                             2:1.4.2-1
ii  xserver-xorg-core [xorg-input-abi-20]  2:1.15.0-2

xserver-xorg-input-wacom recommends no packages.

Versions of packages xserver-xorg-input-wacom suggests:
pn  xinput  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi,

I'm going to tentatively close this bug here now, since there's a pretty
good chance that it falls into the "new device, not yet properly supported"
category, and so there's a reasonably good chance that things have
improved on that front since it was reported.

If you've got 'mouse buttons' locking up, that sounds like something
more fundamental is wrong than just a glitch with the part of it in
this package.

If you're still seeing this with the kernel and drivers in unstable,
then more information might be useful - but it's the kind of bug that
is hard for anyone without the device in question to do much about.

  Ron

--- End Message ---

Reply via email to