Mouse buttons don't work on second display

Bug #1691852 reported by Andrew Vian
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am running Ubuntu 16.04.2 LTS with the 4.8.0-52-generic kernel. The computer is a MacBook Pro 10,1. I am using the proprietary Nvidia display driver 375.66. I have encountered a new bug multiple times today, that I have never seen before. I would guess this is an xorg problem, but nothing has been changed there to cause this bug to appear today.

Expected Behavior: Mouse pointer properly interacts with all open windows and UI buttons on both monitors.

Problem Behavior: Mouse works properly for interactions on monitor 1. Mouse pointer moves properly on monitor 2, but mouse buttons have no impact on anything when the pointer is on the second monitor. Windows functioning properly on display 1 fail to respond to mouse buttons when moved to display 2. When a window is partially displayed on both monitors, the mouse works properly for the part of the window shown on monitor 1, but does not work for the part of the window shown on monitor 2.

This behavior only began today, which is odd because the only software changes today were updates to iproute2:amd64 and libjasper1:amd64. This issue remains following a reboot, and impacts the second monitor for all workspaces. I had upgraded packages yesterday and had no problems then, just problems follwing the upgrade today.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017
 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu May 18 14:00:35 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00f7]
 NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
InstallationDate: Installed on 2016-05-04 (378 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic root=UUID=398390d3-f6be-4e80-8a20-f036f9ec4d26 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B09.1506081405
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B09.1506081405:bd06/08/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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: Thu May 18 13:22:43 2017
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:

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

xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

Revision history for this message
Andrew Vian (drewvian) wrote :
Revision history for this message
Paul White (paulw2u) wrote :

We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time.

Thank you for helping make Ubuntu better.

Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

I'm closing this issue earlier than normal as I'm moving away from reviewing bug reports that have received little or no attention in recent times and there have been no comments to suggest that the reported problem is still an issue when using a currently supported release of Ubuntu.

Please feel to revert the status of this bug report to a previous status if this is still an issue while using a currently supported release of Ubuntu.

Changed in xorg (Ubuntu):
status: Incomplete → Invalid
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.