Touchpad buttons don't work on Vaio laptop

Support
1

I just got a Notebook VAIO Core i3-8130U 4GB 1TB Tela 15.6” Windows 10 FE15 VJFE51F11X-B0111H. I plan to dual boot it with Ubuntu. I wrote manjaro-xfce-20.1-minimal-200911-linux58.iso to a usb drive and booted the new computer with that usb. I chose XFCE as the desktop environment. The bootup went as expected and the Manjaro/XFCE seemed to load fine.

However, the touchpad buttons don’t work completely. By completely, I mean I can’t click with those buttons. I can move the cursor around with the touchpad. The left button works for scrolling. That is, if I put the cursor over a scrollbar in a window which has one, if I hold down the left button I can scroll, but as I said before, I can’t use that button or the other button to click. I can do a “left-click” by tapping the touchpad and right click by doing a 2-finger tap.

I tried booting with an ubuntu usb and had the same problem.

How can I get these two buttons to click?

2

If I understand it correctly, the touchpad works, but not the button(s) in the touchpad. Does it have dedicated buttons for left/right click or it’s a clickpad?

3

Yes, the touchpad works. I can move the cursor around with it and if a window has a scrollbar, I can move the cursor onto the scrollbar, hold down the left button (yes, there are 2 dedicated buttons, left and right - there is no center button) and drag the scrollbar as needed.

4

Please install evtest and run it, then select the touchpad device, and see if any events appear when you press the dedicated buttons of the touchpad.

5

I haven’t installed Manjaro yet, I’m using a live usb. Is it possible to install evtest before I actually install to hard drive?

6

It should be. sudo pacman -Sy evtest should work.

7

OK, I ran evtest. When I press the buttons I get a series of events reported (SYN REPORT) It’s a bunch of type 4 (EV_MSC), code 5 (MSC_TIMESTAMP) reports and then a type 1 (EV_KEY), code 272 (BTN_Left) report.

Same thing with the right button, except there’s a code 273 instead of 272.

8

Note: In the settings for Mouse and Touchpad, the devices indicated are:
SYNA3602:00 0911:5266 Mouse
and
SYNA3602:00 0911:5266 Touchpad

9

Normally it would like this (tested on my Lenovo G50-30) when i click the buttons only and don’t touch the pad:

Testing ... (interrupt to exit)
Event: time 1601217922.424423, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
Event: time 1601217922.424423, -------------- SYN_REPORT ------------
Event: time 1601217922.541181, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
Event: time 1601217922.541181, -------------- SYN_REPORT ------------
Event: time 1601217923.246235, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 1
Event: time 1601217923.246235, -------------- SYN_REPORT ------------
Event: time 1601217923.361231, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 0
Event: time 1601217923.361231, -------------- SYN_REPORT ------------

Please post always the output here… not a description of the output :smiley: Thanks.

10

I described the output because I don’t see how to “capture” the output. Every time I move the cursor a bunch of new output scrolls in the terminal window. My output looks very similar to what you showed.

11

Never mind. I realized I could stop the test.

Event: time 1601210227.644070, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 91100
Event: time 1601210227.644070, -------------- SYN_REPORT ------------
Event: time 1601210227.646075, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 93400
Event: time 1601210227.646075, -------------- SYN_REPORT ------------
Event: time 1601210227.648067, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 95700
Event: time 1601210227.648067, -------------- SYN_REPORT ------------
Event: time 1601210227.650059, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 98000
Event: time 1601210227.650059, -------------- SYN_REPORT ------------
Event: time 1601210227.652055, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 100300
Event: time 1601210227.652055, -------------- SYN_REPORT ------------
Event: time 1601210227.654050, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 102600
Event: time 1601210227.654050, -------------- SYN_REPORT ------------
Event: time 1601210227.656041, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 104900
Event: time 1601210227.656041, -------------- SYN_REPORT ------------
Event: time 1601210227.658034, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 107200
Event: time 1601210227.658034, -------------- SYN_REPORT ------------
Event: time 1601210227.660032, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 109500
Event: time 1601210227.660032, -------------- SYN_REPORT ------------
Event: time 1601210227.662038, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 111800
Event: time 1601210227.662038, -------------- SYN_REPORT ------------
Event: time 1601210227.664043, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 114100
Event: time 1601210227.664043, -------------- SYN_REPORT ------------
Event: time 1601210227.666152, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 116500
Event: time 1601210227.666152, -------------- SYN_REPORT ------------
Event: time 1601210227.668156, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 118700
Event: time 1601210227.668156, -------------- SYN_REPORT ------------
Event: time 1601210227.670112, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 121100
Event: time 1601210227.670112, -------------- SYN_REPORT ------------
Event: time 1601210227.672105, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 123400
Event: time 1601210227.672105, -------------- SYN_REPORT ------------
Event: time 1601210227.674112, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 125800
Event: time 1601210227.674112, -------------- SYN_REPORT ------------
Event: time 1601210227.676127, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 128000
Event: time 1601210227.676127, -------------- SYN_REPORT ------------
Event: time 1601210227.678121, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 130400
Event: time 1601210227.678121, -------------- SYN_REPORT ------------
Event: time 1601210227.680113, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 132700
Event: time 1601210227.680113, -------------- SYN_REPORT ------------
Event: time 1601210227.682109, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 135000
Event: time 1601210227.682109, -------------- SYN_REPORT ------------
Event: time 1601210227.684104, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 137300
Event: time 1601210227.684104, -------------- SYN_REPORT ------------
Event: time 1601210227.686097, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 139600
Event: time 1601210227.686097, -------------- SYN_REPORT ------------
Event: time 1601210227.688090, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 141900
Event: time 1601210227.688090, -------------- SYN_REPORT ------------
Event: time 1601210227.690084, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 144200
Event: time 1601210227.690084, -------------- SYN_REPORT ------------
Event: time 1601210227.692078, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 146500
Event: time 1601210227.692078, -------------- SYN_REPORT ------------
Event: time 1601210227.694085, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 148800
Event: time 1601210227.694085, -------------- SYN_REPORT ------------
Event: time 1601210227.696093, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 151100
Event: time 1601210227.696093, -------------- SYN_REPORT ------------
Event: time 1601210227.698110, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 153400
Event: time 1601210227.698110, -------------- SYN_REPORT ------------
Event: time 1601210227.700266, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 155700
Event: time 1601210227.700266, -------------- SYN_REPORT ------------
Event: time 1601210227.702230, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 158200
Event: time 1601210227.702230, -------------- SYN_REPORT ------------
Event: time 1601210227.704226, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 160500
Event: time 1601210227.704226, -------------- SYN_REPORT ------------
Event: time 1601210227.706226, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 162800
Event: time 1601210227.706226, -------------- SYN_REPORT ------------
Event: time 1601210227.708215, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 165100
Event: time 1601210227.708215, -------------- SYN_REPORT ------------
Event: time 1601210227.710209, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 167400
Event: time 1601210227.710209, -------------- SYN_REPORT ------------
Event: time 1601210227.712212, type 1 (EV_KEY), code 273 (BTN_RIGHT), value 0
Event: time 1601210227.712212, type 4 (EV_MSC), code 5 (MSC_TIMESTAMP), value 169700
Event: time 1601210227.712212, -------------- SYN_REPORT ------------

I clicked the left button and then the right button WITHOUT moving the cursor between clicking the buttons. It displated a line with the 272 left button code, but when I clicked the right button, it displayed MANY lines of report and even though I scrolled up quite a while, I couldn\t find the left button report.

12

Can you test it with libinput debug-events if the problem is still relevant?

13