Mouse button stops working

[Dmitry Zaitsev]

The left button may not work because the mouse generates a constant pressing a service button.

My mouse have "hidden" button 20-21-23, that "click" when I switch profiles. When all button is released, then mouse work as expected. In other cases, left button does not work anywhere else, although its operation can be seen in xinput, for example.

I was able to get out of situation just by turning off the service button in the xorg.conf (writing zeros in their place):

Section "InputClass"
    Identifier "Mouse Remap"
...
    Option "ButtonMapping" "1 2 3 4 5 0 0 8 9 10 11 12 13 14 15 16 17 18 19 0 0 0 0 0"
...
EndSection

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 355.06 Tue Jul 28 21:26:50 PDT 2015
 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Oct 7 03:44:33 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
DpkgLog:

GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7917]
 NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3170]
MachineType: MSI MS-7917
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=14ae1968-3ddd-4a72-94a4-41f681469efe ro nomodeset
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd12/23/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65+git20150922.f3c6740f-0ubuntu0ricotz~vivid
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.0~git20150916+11.0.c4bae579-0ubuntu0sarvatt~vivid
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.0~git20150916+11.0.c4bae579-0ubuntu0sarvatt~vivid
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Oct 7 03:39:42 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.1-0ubuntu3.1

[Dmitry Zaitsev (hhrhhr)]

> If you update to this ... does it change anything?
now BIOS updated, but problem remains.

> provide the output of the following terminal command:
````
:~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.12
08/11/2015
````

In addition, I recorded a a short video with output commands 'xinput query-state' and 'evtest | grep -E "code (4|287|288|289)"' (events for profile button) - https://youtu.be/SLuYli09mWs

comments:
i'm run tools and press repeatedly Profile Button. evtest catch this:

profile 1 -> profile 2
Event: time 1444185699.098578, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90010
Event: time 1444185699.098578, type 1 (EV_KEY), code 287 (?), value 0
Event: time 1444185699.098578, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90011
Event: time 1444185699.098578, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1

profile 2 -> profile 3
Event: time 1444185700.749620, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90011
Event: time 1444185700.749620, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1444185700.749620, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90012
Event: time 1444185700.749620, type 1 (EV_KEY), code 289 (BTN_THUMB), value 1

profile 3 -> profile 1
Event: time 1444185702.766625, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90010
Event: time 1444185702.766625, type 1 (EV_KEY), code 287 (?), value 1
Event: time 1444185702.766625, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90012
Event: time 1444185702.766625, type 1 (EV_KEY), code 289 (BTN_THUMB), value 0

so, when profile 1 is active and happen "EV_KEY code 287" ("button[20]=down" as xinput say) then left button stop working.

[penalvch (penalvch)]

Dmitry Zaitsev, to see if this is already solved, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

[Dmitry Zaitsev (hhrhhr)]

I can test this in Live-session? honestly to make a full installation is not much desire.

[Dmitry Zaitsev (hhrhhr)]

ok, even in Wili Live bug is repeated - https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1503540

[penalvch (penalvch)]

Dmitry Zaitsev, to advise, you don't need to create additional reports on top of one you reported already.

Despite this, did this problem not occur in a release prior to Vivid?

[Dmitry Zaitsev (hhrhhr)]

> to advise, you don't need to create additional reports...
I have been guided by this:
2. Please do not speculate on what you think is or isn't a duplicate report.
8. Please do not stack multiple issues into one report.
but well, as you say.

> did this problem not occur in a release prior to Vivid?
This problem exists at least version 14.04 LTS, I can not verify it exists in earlier versions. The problem does not exist in other desktop environments, such a LXDE or XFCE even in 15.04.

[penalvch (penalvch)]

Dmitry Zaitsev:
>"I have been guided by this: 2. Please do not speculate on what you think is or isn't a duplicate report."

You aren't doing much speculation, so I'm not sure why this was brought up.

>"8. Please do not stack multiple issues into one report. but well, as you say."

Using Wily doesn't mean you are stacking multiple issues into one report. You have the same one issue, reproducible in two different releases.

>" The problem does not exist in other desktop environments, such a LXDE or XFCE even in 15.04."

Sounds like some user space correlation. I'll mark it Triaged for now, given you've tested the latest Ubuntu release.

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.