Open balfred opened 7 years ago
I reverted back to 2.0 to see if I would have the same problem still and I do. The tap to click is sketchy in 2.0 and 2.1. Let me know if there is any specific information that will help as I really want to use gallium but need the tap to work.
There's an updated touchpad config for CAVE in the "prerelease" repo which might help.
You can test it with:
sudo galliumos-repodist --enable prerelease
galliumos-update
reboot
This new config will probably be included in 2.1 final, which should release shortly (and at which point you can --disable
the prerelease repo if you like.
Awesome thanks! I will try that. What was it that changed that you suspect will fix this problem?
Bummer, whatever the update was didnt work. Tap to click is still sporadic at best and the checkbox frequently changes its value on its own. If there is a way to confirm that I got the update applied successfully I am happy to look.
I'm experiencing a lot of "phantom" clicks as well, where after initially clicking somewhere, the mouse will register a second or even third click without my being even remotely close to the touchpad. Running latest.
I've been having problems with the Asus C302 touchpad and GalliumOS 2.1. Some notes:
xinput watch-props "Elan Touchpad"
shows the checkbox in the settings is actually reversed if tap-to-click is on before opening the dialog: checking it on turns tap-to-click off and vice versa. (Actually, it's even stranger -- any selection of the touchpad from the drop down will toggle it).evemu-record
it apparently counts as a tap BTN_TOOL_FINGER with no pressure. This means that when tap-to-click is enabled you can literally just "tap" your finger half an inch about the touchpad and it will register.xserver-xorg-input-synaptics
helps with the tap to click issue (once the finger pressure parameters are fixed) but the cursor is then somewhat laggy -- I suspect this is because it is missing some acceleration profile parameters that are available on Mint.The touchpad under Mint is okay, the touchpad under ChromeOS is fine, so I'm hoping that this issue is easily fixable. I have pulled down the Chromium OS source to see if I can see what parameters they are using for CAVE, but any suggestions for diagnostics / areas to look at would be greatly appreciated.
Unfortunately, ChromeOS is no longer using Xorg, so using their trackpad drivers can be tricky. Additionally, I don't think we currently have any desire to work on the synaptics driver that ships with most other Linux distributions. It's not impossible, but highly improbable.
I also have a CAVE with 2.1 and I can confirm @brool 's report is still the case:
any selection of the touchpad from the drop down will toggle it
Steps to Reproduce: