0

I have a Dell Inspiron 13 7000 (7373). It has a touchpad mouse device and a touchscreen. Here is my xinput:

⎡ Virtual core pointer                      id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ DELL07EB:00 06CB:7E7E Touchpad            id=12   [slave  pointer  (2)]
⎜   ↳ ELAN2097:00 04F3:2364                     id=13   [slave  pointer  (2)]

If I use the touchpad, I can click on menus just fine (e.g. File->Open etc). But if I use the touchscreen, I can click to open the menu (File), but when I try to click on the items in the menu (Open), it almost never works. Maybe one out of every 50 times it might do what I want.

I suspect the problem is related to the output I get from xinput test. This is typical of what I get from my touchpad (which works properly with menus):

motion a[0]=179 a[1]=934 
motion a[1]=935 
button press   1 
button release 1 

However this is the behavior I consistently get from the touchscreen (with motion events inserted between button press/release, even though it's the same coordinates):

motion a[0]=36122 a[1]=18899 
button press   1 a[0]=36122 a[1]=18899 
motion a[0]=36122 a[1]=18899 
button release 1 a[0]=36122 a[1]=18899 
motion a[0]=54558 a[1]=39402 
button press   1 a[0]=54558 a[1]=39402 
motion a[0]=54558 a[1]=39402 
button release 1 a[0]=54558 a[1]=39402 

Notice the coords didn't change, but it still fires a motion event before the button-release event. I'm assuming this is probably triggering some sort of "drag and drop" type routine in X-Windows, which is probably why it doesn't work correctly with the menus.

My touchscreen is using the libinput driver; here's the xinput list-props for it:

Device Enabled (143):   1
Coordinate Transformation Matrix (145): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Calibration Matrix (306):  1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Calibration Matrix Default (307):  1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
libinput Send Events Modes Available (263): 1, 0
libinput Send Events Mode Enabled (264):    0, 0
libinput Send Events Mode Enabled Default (265):    0, 0
Device Node (266):  "/dev/input/event13"
Device Product ID (267):    1267, 9060

This has been a consistent issue, in multiple environments: Ubuntu 16.04-18.04, and also in Unity, Gnome and Xfce. Currently running Xubuntu 18.04.

Does anyone know some way to get this to work correctly?

  • Usually I'd recommend to test latest libinput version, but I don't see in libinput's git-log any touchscreen-related fixes, so oh well. Please, report a bug. – Hi-Angel Aug 1 '18 at 21:36

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.