Mouse flickers and disappears on primary monitor when additional monitor is connected

Bug #1655828 reported by Mauricio Maluff Masi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Any time I connect my Acer G236HL LCD monitor with VGA via my Dell Adapter (Part# 470-ABHH, DisplayLink driver version 1.2.65), the mouse flickers and disappears in the primary monitor. It displays perfectly on the additional monitor. It also displays perfectly after the additional monitor is disconnected.

I see that there are a number of similar bug reports:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001

WORKAROUND: Bypass the DisplayLink adapter and plug computer directly into a monitor with mini-DP.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:

ApportVersion: 2.20.3-0ubuntu8.2
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: Tue Jan 10 22:34:58 2017
DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8))
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DistroCodename: yakkety
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError! Could not locate dkms.conf file.
 File: does not exist.

 bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell HD Graphics 5500 [1028:0665]
InstallationDate: Installed on 2016-01-26 (350 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25
MachineType: Dell Inc. XPS 13 9343
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=485e1110-0879-413f-b537-6b5b97353478 ro quiet splash usbcore.autosuspend=-1 "acpi_osi=Windows 2013" vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to yakkety on 2016-10-23 (79 days ago)
XorgLogOld:

dmi.bios.date: 08/29/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/29/2016:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
xserver.bootTime: Tue Jan 10 20:18:19 2017
xserver.configfile: default
xserver.errors: modeset(G0): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 5152
 vendor SHP
xserver.version: 2:1.18.4-1ubuntu6.1

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

@penalvch: I subscribed you per your request in a few of the related bugs.

Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi, thank you for reporting this and helping make Ubuntu better.

1) Did this issue not occur for you personally (not someone else) in a Ubuntu release prior to 16.10?
2) Could you please advise to the full manufacturer and model of the device you are using that requires the DisplayLink driver?
3) What version of the DisplayLink driver are you using?
4) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

tags: added: latest-bios-a09
Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

1. Yes, to me personally at least since 16.04. I can't positively remember if it was happening in 14.04, but I *think* it was.
2. Acer G236HL LCD monitor connected via VGA.
3. 1.2.65, the latest version.
4. I'll have to test that over the weekend. I should have a chance by 1/18 at the latest.

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

Also, thanks to you for helping with this!

Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi, in addition to 4), could you please provide the full manufacturer and model as noted on the sticker of the DisplayLink adapter itself (not from the Bug Description, or the result of a terminal command)?

tags: added: xenial
description: updated
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

The label is pretty faded, so I'm not positive on this. But I think it's:

Make: DisplayLink
Model: E364109

Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi:

>" The label is pretty faded, so I'm not positive on this. But I think it's: Make: DisplayLink Model: E364109"

AFAIK, DisplayLink doesn't sell adapters as a manufacturer. Other hardware manufacturers integrate DisplayLink technology in their products and then brand it differently. Hence, the device you have wouldn't have DisplayLink as either the manufacturer or the make.

Also, I wasn't able to find any device from any manufacturer with model E364109. Would this device have any other sticker, markings, or logos? Would you have a receipt for this device to reference?

Also, have you tried testing earlier versions of the DisplayLink driver to see if this is a regression of it via http://www.displaylink.com/downloads/ubuntu ?

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

That's really all I could make out from it, sorry. I'm attaching a picture in case you can see something I can't. The receipt was not very helpful, it just says something generic like "Dell Adapter USB 3.0."

I did find the Dell part number: 470-ABHH

Here's a link to the current listing on their website: http://www.dell.com/en-us/shop/dell-adapter-usb-3-0-to-hdmi-vga-ethernet-usb-2-0/apd/470-abhh/handhelds-tablet-pcs

They give this code for the Manufacturer part: H5G60

But that's as far as I could make it.

I'll try the current version of Ubuntu tomorrow, as promised.

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

I'm having some trouble booting into 17.04 to test this. I posted a question here: http://askubuntu.com/questions/873812/cant-boot-into-separate-ubuntu-version

I'll keep trying this evening.

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

No luck with Ubuntu in a separate partition--would it be just as good if I tested from a live USB?

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

All right, I tried to install the latest version of DisplayLink, but it failed. I'm attaching the make.log.

It seems to have been caused by this patch: https://lists.freedesktop.org/archives/intel-gfx/2016-August/103278.html

Which removed the dirty_info_property from drm_mode_config.

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

Success (sort of)! I pulled up the evdi source, commented out the references to dirty_info_property from evdi_connector.c, and the reference to drm_mode_create_dirty_info_property in evdi_modeset.c. I compiled the whole driver manually, and I was able to install it successfully in 17.04.

I can still see the flickering, though it does seem slightly less pronounced than usual. I haven't used it very heavily, but I can definitely see the flickering.

penalvch (penalvch)
tags: added: zenial
tags: added: zesty
removed: zenial
Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi, to clarify:
1) If you connect a monitor directly to your laptop via mini-DP (i.e. bypassing the Dell adapter) is the flickering reproducible? This will help confirm if the issue is related to the DisplayLink driver or not.
2) Also, as per https://help.ubuntu.com/community/DisplayLink one wouldn't have to compile the drivers, but instead run an install script. Could you please advise?

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote :

1. I bought a new monitor and have been using it via the mini-DP port for the past week, and have not noticed the flickering.
2. I'm not sure what the second question is referring to. If it's about post #13: The install script didn't work in 17.04, so I had to make some changes and compile it manually. It turns out the latest version of the evdi module already incorporates the changes I made, but the released version included with the DisplayLink installer does not.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg (Ubuntu):
status: Incomplete → Expired
penalvch (penalvch)
Changed in xorg (Ubuntu):
status: Expired → New
Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi, given this issue is correlated to using the DisplayLink driver/adapter, in order to report this issue to them, could you please test the latest driver version (1.3.52) via http://www.displaylink.com/downloads/ubuntu and advise to the results?

description: updated
Changed in xorg (Ubuntu):
status: New → Incomplete
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote : Re: [Bug 1655828] Re: Mouse flickers and disappears on primary monitor when additional monitor is connected
Download full text (9.6 KiB)

Actually I got tired of this and got a new monitor that supports the DP
port on my laptop. I no longer have the old one, so I can't test this any
further. I suppose that means it can be closed?

On Sat, May 6, 2017, 21:15 Christopher M. Penalver <
<email address hidden>> wrote:

> Mauricio Maluff Masi, given this issue is correlated to using the
> DisplayLink driver/adapter, in order to report this issue to them, could
> you please test the latest driver version (1.3.52) via
> http://www.displaylink.com/downloads/ubuntu and advise to the results?
>
> ** Description changed:
>
> - Any time I connect my Acer G236HL LCD monitor with VGA via my
> - Displaylink adapter (DisplayLink driver version 1.2.65), the mouse
> + Any time I connect my Acer G236HL LCD monitor with VGA via my Dell
> + Adapter (Part# 470-ABHH, DisplayLink driver version 1.2.65), the mouse
> flickers and disappears in the primary monitor. It displays perfectly on
> the additional monitor. It also displays perfectly after the additional
> monitor is disconnected.
>
> I see that there are a number of similar bug reports:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1645891
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629300
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1613001
> +
> + WORKAROUND: Bypass the DisplayLink adapter and plug computer directly
> + into a monitor with mini-DP.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.10
> Package: xorg 1:7.7+13ubuntu4
> ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
> Uname: Linux 4.8.0-34-generic x86_64
> NonfreeKernelModules: wl
> .tmp.unity_support_test.0:
>
> ApportVersion: 2.20.3-0ubuntu8.2
> 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: Tue Jan 10 22:34:58 2017
> DistUpgraded: 2016-10-23 13:14:39,472 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
> execute child process "./xorg_fix_proprietary.py" (No such file or
> directory) (8))
> DistributionChannelDescriptor:
> # This is a distribution channel descriptor
> # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> canonical-oem-somerville-trusty-amd64-20140620-0
> DistroCodename: yakkety
> DistroVariant: ubuntu
> DkmsStatus:
> bcmwl, 6.30.223.248+bdcom, 4.8.0-32-generic, x86_64: installedError!
> Could not locate dkms.conf file.
> File: does not exist.
>
> bcmwl, 6.30.223.248+bdcom, 4.8.0-34-generic, x86_64: installed
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00
> [VGA controller])
> Subsystem: Dell HD Graphics 5500 [1028:0665]
> InstallationDate: Installed on 2016-01-26 (350 days ago)
> InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
> 20140620-04:25
> MachineType: Dell Inc. XPS 13 9343
> ...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Mauricio Maluff Masi, closing as per your request in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1655828/comments/18 .

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.