Right touchpad button doesn’t work after fwupdate

[dev-da77]

I have: Pinebook Pro (ANSI) + Manjaro Gnome Edition

I executed pinebook-pro-keyboard-updater (v0.0.3-2, v0.0.3-4) like discribed:

sudo pbp-fwupdater step-1 sudo poweroff sudo pbp-fwupdater step-2 ansi sudo poweroff sudo pbp-fwupdater flash-kb firmware/default_ansi.hex //pulled files from here (github)

Touchpad works better as before, BUT I have the issue that my rigth touchpad button doesn’t work anymore. I cannot open a contextmenu as example

I don’t find any hints or issue reports on that. I repeated the update two times with no change. Update runs without error messages.

[MFAshby]

I have a similar issue, but I suspect it's related to manjaro gnome since I was using i3 when I did the firmware update and it worked ok there/

[9R]

I have the same issue.

Here is the output of xev when pressing the left and right button:

ButtonPress event, serial 38, synthetic NO, window 0x5200001,
    root 0x42d, subw 0x0, time 18603881, (112,167), root:(162,280),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 38, synthetic NO, window 0x5200001,
    root 0x42d, subw 0x0, time 18604009, (112,167), root:(162,280),
    state 0x100, button 1, same_screen YES

ButtonPress event, serial 38, synthetic NO, window 0x5200001,
    root 0x42d, subw 0x0, time 18609449, (112,167), root:(162,280),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 38, synthetic NO, window 0x5200001,
    root 0x42d, subw 0x0, time 18609617, (112,167), root:(162,280),
    state 0x100, button 1, same_screen YES

It seems they are both registered as "button 1"

[9R]

I have tested with diffferent window managers under X and wayland. behavior is the same.

With sudo cat /dev/input/mice | od -An -t x1 -w1 I catch the raw bytes coming from the mouse and they seem to be identical for left & right click:

#left press
 09
 00
#left release
*
 08
 00
*

#right press
 09
 00
*
#right release
 08
 00
*

So to me it looks like the issue is indeed on the kernel or firmware level. @MFAshby can you still reproduce the working behavior you saw on i3?