The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
gnome-shell (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
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 because the setting to set the mouse 'Acceleration Profile' to 'adaptive' is hidden in the gnome-tweak tool and set to default 'linear'. I highly suspect that this setting was on by default on X11 synaptics, because my mouse experience became equal after i turned it to adaptive when it was inferior before.
This is probably the cause of many of the mouse complaints on the ubuntu upgrade.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSign
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.8
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue May 8 09:26:49 2018
DisplayManager: gdm3
InstallationDate: Installed on 2016-09-25 (590 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to artful on 2018-05-06 (1 days ago)
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
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 scroll up (4) as buttons but it appears be impossible at this level. Maybe i was hallucinating using that area as 3rd mouse button previously?
It also recognizes single tap on the central area to button 1 (same as left mouse button), and double tap to button 3 (same as right mouse button). Very very very occasionally (like once every 30 times) it recognizes a triple tap as 2 (middle mouse) instead of (3) right click. When it doesn't disastrously move the pointer.
I'm wondering if i can use 'xinput set-button-map' to reassign the central area double tap for button 2 and leave the actual physical button right as button 3. Probably will change both with my luck and i'll not be able to right click.