Screen Temporarily Blanks When Moving Mouse Between Monitors

[Joseph Bylund]

When moving my mouse between two monitors one of the monitors (it seems to be usually the one which the mouse has just exited) goes blank for about 2 seconds. It's not entirely reproducible, but happens ~25% of the time. Not sure which package this should be filed against.

Version: Ubuntu 16.10
---
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joseph 1274 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.10
HibernationDevice: RESUME=UUID=13913206-5914-48e6-8049-82eb3b1c4e20
InstallationDate: Installed on 2016-12-21 (1 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp.
 Bus 001 Device 016: ID 093a:2521 Pixart Imaging, Inc. Optical Mouse
 Bus 001 Device 014: ID 046d:c31c Logitech, Inc. Keyboard K120
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10FM0021US
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=2fc222ff-47e5-49d0-9a7f-444236636e12 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
RelatedPackageVersions:
 linux-restricted-modules-4.8.0-22-generic N/A
 linux-backports-modules-4.8.0-22-generic N/A
 linux-firmware 1.161.1
Tags: yakkety
Uname: Linux 4.8.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/24/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: FWKT54A
dmi.board.name: SKYBAY
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN 3425058315567
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnLENOVO:bvrFWKT54A:bd06/24/2016:svnLENOVO:pn10FM0021US:pvrThinkCentreM900:rvnLENOVO:rnSKYBAY:rvrSDK0J40705WIN3425058315567:cvnLENOVO:ct3:cvrDefaultstring:
dmi.product.name: 10FM0021US
dmi.product.version: ThinkCentre M900
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1652174

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

apport information

[Joseph Bylund (joseph-bylund)]

I have removed the second monitor for now, so it was not connected when I ran apport-collect. Let me know if I need to re-connect and run again.

[penalvch (penalvch)]

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

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Joseph Bylund, to clarify, when you tested 4.10-rc1 you reconnected the second monitor and the problem was not reproducible?