[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#860086: marked as done (qtbase5-dev: QApplication does not receive QEvent::TabletEnterProximity)

Your message dated Wed, 14 Mar 2018 18:02:43 -0300
with message-id <29259083.XPGAfDciyW@tonks>
and subject line Re: Bug#860086: Unreproducible, moreinfo
has caused the Debian Bug report #860086,
regarding qtbase5-dev: QApplication does not receive QEvent::TabletEnterProximity
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 owner@bugs.debian.org
immediately.)


-- 
860086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860086
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: qtbase5-dev
Version: 5.7.1+dfsg-3+b1
Severity: normal

I'm using a Lenovo ThinkPad Yoga 2, which has a touch screen and a stylus.
The stylus triggers Qt tablet events.

Trying to fix a problem in Okular [0], I noticed that the QApplication class
does not receive the events TabletEnterProximity and TabletLeaveProximity,
even though it should, according to the Qt documentation [1].  To test this,
try the example tablet application from [1].  It should change the cursor
shape whenever the stylus comes near the screen, but the cursor never changes.
Adding a debug line into TabletApplication::event (which inherits from QApplication)
shows that QApplication actually receives very few events at all.
Basically only QApplicationStateChangeEvents and QTimerEvents.

On the other hand, my system does know about the stylus being close to the
screen. xev sees it, and in the example from [1] the cursor moves to the
correct position when I move the stylus close to, but not onto the screen.

This is a regression.  It used to work with a Debian testing installation from
about six month ago when I first wrote the patch in [0].  Has there been some
change to Qt in the meantime that could trigger this?  What can I do to debug
this further?

Thanks for your help!


[0]: https://git.reviewboard.kde.org/r/128858/
[1]: http://doc.qt.io/qt-5/qtwidgets-widgets-tablet-example.html 

-- System Information:
Debian Release: 9.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qtbase5-dev depends on:
ii  libgl1-mesa-dev [libgl-dev]    13.0.6-1
ii  libglu1-mesa-dev [libglu-dev]  9.0.0-2.1
ii  libqt5concurrent5              5.7.1+dfsg-3+b1
ii  libqt5core5a                   5.7.1+dfsg-3+b1
ii  libqt5dbus5                    5.7.1+dfsg-3+b1
ii  libqt5gui5                     5.7.1+dfsg-3+b1
ii  libqt5network5                 5.7.1+dfsg-3+b1
ii  libqt5printsupport5            5.7.1+dfsg-3+b1
ii  libqt5sql5                     5.7.1+dfsg-3+b1
ii  libqt5test5                    5.7.1+dfsg-3+b1
ii  libqt5widgets5                 5.7.1+dfsg-3+b1
ii  libqt5xml5                     5.7.1+dfsg-3+b1
ii  libxext-dev                    2:1.3.3-1+b2
ii  qt5-qmake                      5.7.1+dfsg-3+b1
ii  qtbase5-dev-tools              5.7.1+dfsg-3+b1
ii  qtchooser                      63-g13a3d08-1

Versions of packages qtbase5-dev recommends:
ii  libqt5opengl5-dev  5.7.1+dfsg-3+b1

Versions of packages qtbase5-dev suggests:
ii  default-libmysqlclient-dev  1.0.2
pn  firebird-dev                <none>
pn  libegl1-mesa-dev            <none>
ii  libgl1-mesa-dev             13.0.6-1
ii  libpq-dev                   9.6.2-2
ii  libsqlite3-dev              3.16.2-3
ii  unixodbc-dev                2.3.4-1

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 5.9.2+dfsg-12

El miércoles, 14 de marzo de 2018 17:59:26 -03 Oliver Sander escribió:
> Thanks for asking.  In fact, the problem disappeared automatically
> during some Qt update (sorry, I don't know which one).
> So the bug can be fixed.

Thanks a lot for the follow up!

I'm closing this bug with the current version in testing, although it might 
have been fixed before.


-- 
  "Waaah! Debian never keeps its release schedules!"
Okay, lets make a Debian-like distribution that hits its schedules and is
close to bleeding edge.
  "Waaah! Ubuntu ships buggy stuff!"
Grrrrrr.
(Not aimed at jwb in particular, BTW. Just pointing out that there's always
going to be some disappointed people.)
  vmole (subscriber, #111) - http://lwn.net/Articles/279111/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: