[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu.

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

** Description changed: First, the obvious: the mouse experience out of the box (at least on ubuntu 17.04) is bad. I thought this was because Wayland is slightly slower on animations + mouse movement but although this is happening for some reason (memory leak, whatever) it's mostly

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

Please try to only report one issue per bug report. The first issue you report is in an area that has been bugging me for a few years too (see bug 1607677). Please reword the bug title and description to just be about that first issue. The second issue you report is possibly bug 1759300. **

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

Your bug report appears to be from Ubuntu 17.10. Please consider upgrading to Ubuntu 18.04 LTS. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu.

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

No, that 'area' setting doesn't work on my touchpad for some reason. A alternative i found at https://askubuntu.com/questions/881939/libinput- how-to-map-different-tappings-to-buttons-tappingbuttonmap-has-no-effe/ does something useful that i'd like to be a setting in the future, exchange the

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

For your middle click and right click issues, please see the Mouse Click Emulation section in GNOME Tweaks > Mouse & Touchpad. Does setting that to Area do what you expect? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are

[Desktop-packages] [Bug 1769845] Re: The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

Mmm. I used 'xev' as per this link: https://wiki.archlinux.org/index.php/Libinput#Manual_button_re-mapping to find which buttons are triggering o keypad interactions. Sadly, apparently taps to the touchpad 'column' are are not even recognized (or double taps). I recognizes scroll down (5) and