The Settings->Devices menu in gnome-shell Wayland doesn't provide enough configurations options, and there is no cfg file to work around it

Bug #1769845 reported by i30817
6
This bug affects 1 person
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
ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
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)

Revision history for this message
i30817 (i30817) wrote :
description: updated
description: updated
description: updated
description: updated
i30817 (i30817)
description: updated
description: updated
description: updated
description: updated
i30817 (i30817)
description: updated
description: updated
description: updated
description: updated
i30817 (i30817)
description: updated
Revision history for this message
i30817 (i30817) wrote :

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.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

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
Revision history for this message
i30817 (i30817) wrote :

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 'double finger tap' by the 'triple finger tap' that is double finger tap is mouse 3.

Unfortunately i also can't make it work. I suspect my driver is always being set to synaptics.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

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
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

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.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
i30817 (i30817)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.