Unity8/Mir: Bottom right area of touchpad no longer treated as right click

[fcole90]

Using the touchpad I was not able to trigger any right click (with a single finger in the bottom right area), and I tought it was a problem of how unity8 handled the right clicks. Instead I just tried with a mouse and right click trigger different actions from left clicks.

In the end the problem is that my touchpad right click is considered a left click by the system. This does not happen with an usb mouse.

[Daniel van Vugt (vanvugt)]

Right click on Unity8 desktop -> duplicate of bug 1539957

Right click on webbrowser-app -> Works for me... In Ubuntu 16.10 I get a menu and can open links in a new page.

So let this bug be about the second issue. Seems to be invalid and/or fixed already.

[Stephen M. Webb (bregma)]

I do not get anything when I right-click in the webbrowser-app.

[fcole90 (fcole90)]

Neither do I, trying it on 16.10

[fcole90 (fcole90)]

Sorry, I don't think it's a duplicate of 1539957. I can't even right click on the launcher to pin apps for example.

[Daniel van Vugt (vanvugt)]

OK, confirmed by comment #2. Although right click works fine for me (Unity8 in Ubuntu 16.10 desktop).

[fcole90 (fcole90)]

When I do right click it is considered as a left click for me. This happens in the webbrowser-app too. If I right click a link, the browser follows the link. If I right click on the close button (in the window decoration) of an app, it gets closed. I'm definitely reporting a different bug. Should I open a different one?

[Daniel van Vugt (vanvugt)]

For a moment I hit the same bug. Then I realised it was user error:

Right click in webbrowser-app only works on links and text selections. Right clicking elsewhere on a page is apparently not meant to do anything (and on some pages like news.google.com will act like a left click).

[fcole90 (fcole90)]

It always work as a left click for me, even outside of the browser. Is there any scenario where a right click does a different action from left click, under unity8, that I can try to test if that's an input problem or just the way the system reacts to right clicks?

[fcole90 (fcole90)]

I just tryed again with a mouse connected and the right click actually works, so the problem happens only with the touchpad's right click.

[Daniel d'Andrada (dandrader)]

Just tried on the touchpad of my Dell XPS L502x (2012 model).

Its touchpad has physical left and right buttons. They work fine with the webbrowser app. The touchpad right click over a link opens a dialog, just like with the mouse.

Maybe it's a hardware-specific issue.

[Daniel d'Andrada (dandrader)]

From discussing with a colleague I assume you have a clickpad (no separate buttons, the whole touchpad is a single physical button). Updating title accordingly

[fcole90 (fcole90)]

Yes, it has no physical button

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

I've been testing right clicking in Unity8 and other Mir servers today and it works.

I'm using an Apple Magic Trackpad and of course using two fingers for a right click. Are you using two fingers or expecting the bottom right corner of your clickpad to do it with one finger?

[Lukáš Tinkl (lukas-kde)]

I am expecting the bottom right corner of my clickpad to work since that always used to work until a few weeks ago.

[fcole90 (fcole90)]

I tried with the bottom right corner too.

[Daniel van Vugt (vanvugt)]

I think this should be Low actually...

Like other modern platforms we should move to only using and expecting right click via two fingers, rather than designating the bottom right area (which only exists as paint, not in the electronics).

If you're using a modern clickpad it's really annoying in Unity7 that clicking in the wrong area on the clickpad does something different. Unity8/Mir should behave like macOS and ChromeOS in that you can only right click with two fingers by default.

Make it an option to use the bottom-right by all means (so keep this bug open), but I think we've got the default setting right...

[Lukáš Tinkl (lukas-kde)]

... except it never works unless you enable "Tap to click" in System Settings (which is off by default)

[Launchpad Janitor (janitor)]

This bug was fixed in the package gsettings-ubuntu-touch-schemas - 0.0.7+16.10.20160730-0ubuntu1

---------------
gsettings-ubuntu-touch-schemas (0.0.7+16.10.20160730-0ubuntu1) yakkety; urgency=medium

  * Enable TouchpadTwoFingerScroll and TouchpadTapToClick by default
    (LP: #1603183, #1604032)

 -- Lukáš Tinkl <email address hidden> Sat, 30 Jul 2016 21:17:59 +0000

[Daniel van Vugt (vanvugt)]

Weird. Another bug marked Fix Released or Committed when the actual code change hasn't landed yet(!?)

[Daniel van Vugt (vanvugt)]

Triaged, thanks to comment #18.

Upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=105446

[Daniel van Vugt (vanvugt)]

Incomplete for libinput. I misread comment 18.

Is there still a bug at all?

[Patrick Kilgore (patrick-kilgore)]

@vanvugt I think this is still a big problem lots of 16.04 -> 18.04 upgraders will run into.

This one blew my mind after installing 18.04 today. If this is going to be the new default, we need to warn users, because those of us not using Apple/ChromeOS hardware *expect* clickpads to work like they have for a decade now so it feels like an Ubuntu regression / issue.

The easier solution may be to do a little bit of hardware detection before Ubuntu configures this one for the users, and set the relevant hardware accordingly (Apple/ChromeOs->"fingers"; Dell/Lenovo/Etc->"areas").

Currently (18.04), the easy fix for this is to set:

    $ gsettings set org.gnome.desktop.peripherals.touchpad click-method areas

My bug 1767383 is almost certainly a dupe of this one (sorry, I was originally searching for it against the old driver), but I'll let someone else decide that.

[Daniel van Vugt (vanvugt)]

Libinput does not related to this bug.

Maybe see bug 1759300 instead.

[Daniel van Vugt (vanvugt)]

This bug relates to Unity8 and Mir only.

Gnome Shell users please see bug 1759300 instead.