[Lenovo Yoga 300-11IBY] Right click not working

Bug #1773516 reported by Phill
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

The right click is not working on Lenovo Yoga touch pad after upgrade to 18.04, worked minutes before on 17.10.

I think it works on the Think Pad out-of-the-box (after upgrade from 17.10), if that helps.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat May 26 10:34:57 2018
DistUpgraded: 2018-05-25 23:14:56,258 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display [17aa:3908]
InstallationDate: Installed on 2018-01-18 (128 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: LENOVO 80M0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-05-25 (0 days ago)
dmi.bios.date: 07/30/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: C0CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Mini
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J33995WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 300-11IBY
dmi.modalias: dmi:bvnLENOVO:bvrC0CN31WW:bd07/30/2015:svnLENOVO:pn80M0:pvrLenovoYOGA300-11IBY:rvnLENOVO:rnMini:rvrSDK0J33995WIN:cvnLENOVO:ct10:cvrLenovoYOGA300-11IBY:
dmi.product.family: IDEAPAD
dmi.product.name: 80M0
dmi.product.version: Lenovo YOGA 300-11IBY
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
Phill (phill.l) wrote :
penalvch (penalvch)
tags: added: latest-bios-c0cn31ww
Revision history for this message
penalvch (penalvch) wrote :

Phill, thank you for reporting this and helping make Ubuntu better.

1) To clarify, how are you attempting to right click, tapping two fingers on the clickpad, clicking the bottom right area of the clickpad?

2) If you boot into a kernel from 17.10 does right clicking work again?

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
summary: - Right click not working on Lenovo touchpad
+ [Lenovo Yoga 300-11IBY] Right click not working
Revision history for this message
Phill (phill.l) wrote :

Although the buttons are integral to the touchpad, they are clearly marked with a dividing line. Having read the proposed duplicate, while this issue may have the same underlying cause, this is not a mere configuration preference on this device because it has clearly identified buttons, albeit with nothing more than a coloured dividing line.

Revision history for this message
penalvch (penalvch) wrote :

Phill, if you install gnome-tweak-tool and configure GNOME Tweak Tool > Keyboard & Mouse > Mouse Click Emulation > Area checked then it is a configuration issue, and in turn, a duplicate.

However, if you have this configured and it still doesn't work, that's a different issue.

Could you please advise?

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.