Community
Participate
Working Groups
This error has occurred since the release of Linux on Linux, as the touchpad driver! When we use this driver with the use of two fingers to show the context menu (right mouse button) it does not show the context, but it acts the same as if you were clicking with the (left mouse button) only in project explorer. A workaround is using synaptics drivers, but is deprecated...
(In reply to Gustavo Menezes from comment #0) > This error has occurred since the release of Linux on Linux, as the touchpad > driver! > > When we use this driver with the use of two fingers to show the context menu > (right mouse button) it does not show the context, but it acts the same as > if you were clicking with the (left mouse button) only in project explorer. > > A workaround is using synaptics drivers, but is deprecated... using libinput the bug occurs
Fedora 32 with Wayland (and thus libinput as synaptics is not an option at all under wayland) two fingers click works just fine for me.
(In reply to Alexander Kurtakov from comment #2) > Fedora 32 with Wayland (and thus libinput as synaptics is not an option at > all under wayland) two fingers click works just fine for me. Ubuntu 20.04 with Xorg
I may be having the same problem. Not sure. I have a fresh source build of 2020-09 on Fedora 33 AARCH64 with STS4 and CDT. I am running eclipse with ssh -Y from a Mac running XQuartz. I have a workspace with both Java and C projects. If I 2-finger click the trackpad on a Java source file in Project Explorer I get a context menu. If I 2-finger click the trackpad on a C source file, the context appears and then immediately disappears. OCCASIONALLY, If I get things just right, I am able to 2-finger click-and-hold and the context menu will stay up. Then I can release one finger and move the mouse pointer in the context menu. My success rate is probably 1 in 5. Is this the same issue?
Do you guys still face the issue?
I am no longer having the issue. I'm not sure why it's working now as I have not upgraded eclipse at all. I have however upgraded to Fedora 34. That may have fixed it.