I would like to describe conflicts using Nvidia Prime, Displaylink and Ubuntu in my experience.

My environment: Ubuntu 18.10, Nvidia GTX 1070 (nvidia-driver-415), Displaylink 5.1, Asus MB168B+ (USB monitor), laptop Gigabyte Aero15x.

If I try to login with nvidia profile activated and anything connected in USB ports (even only a mouse), I will face a login loop. It only will stop after disconnecting all USB devices, restarting the system and then I'll be able to login into my Ubuntu. Once logged in, I can connect my USB devices and use everything included my second monitor.

If I try to login with intel profile activated. There will be no problems. Displaylink works ok.

Another interesting behavior. If I start up my laptop with all USB devices connected, of course only possible using intel profile; Displaylink will work perfectly. But if instead, during an current session I plug on my external monitor, I will always see blurry and weird definition around the mouse pointer.

If Displaylink could improve this will help lots of Linux users.
Thanks!

Hi,
I've tried the DisplayLink driver using the recommended os (Ubuntu 16.04). After connecting a secondary display (1080p) using USB-C, I had a trail of blinking mouse pointers following the real one and all the animations started glitching.

When moving the mouse over any Window except the Desktop, there would be a glitching square (about double the edge length of the mouse pointer sprite) containing the desktop background around the mouse pointer.

I've also tried Arch Linux (using the AUR package) and Debian 9 (Using the Ubuntu package) and they show the exact same behavior.
On the three operating systems, I've tried Kernel versions 4.19 and 4.20, both having the same issues.

I have a Thinkpad P1 with a Xeon E-2176M CPU (Intel UHD Graphics P630) and a Nvidia Quatro P2000 Mobile (GP107GLM). I suspect this to be an error related to the hardware I'm using; partially because I tried different operating systems and different kernel versions.

Hi,

I had to downgrade to Sierra 10.12.6 because of the multi-monitor incompatibility of Displaylink 10.13.4. I need my multi monitor setup. But the truth is that Displaylink 4.1, which is compatible with Sierra 10.12.6, deactivate iTunes movies. Here is the message:

The selected display won't play on one of your connected displays

This movie can be played only on displays that support HDCP (High-bandwidth Digital Content Protection). Try moving the iTunes window to a different display. Make sure the entire window is on the supported display.

When I remove Displaylink from OSX 10.1206, iTunes movie start to plays back. In short, Displaylink make the my iMac see it's own screen as an external monitor which is totally ridiculous from an programmer standpoint. This is not mention into know problems between Displaylink and Sierra 10.12.6. I manage to sent an email to the company without any respond. They probably did not liked the way I express myself, but I was piss.

Anyhow, anybody who can't see a movie and need multi monitor : downgrade to Sierra 10.12.6 and install Displaylink 4.1. Uninstalled it when you really want to watch a movie. Reinstalled 4,1 when you really need your multi monitor. Since I cannot upgrade in between 10.12.6 and 10.13.4 there is no way if an update between those versions would had fix this ridiculous problem. At least now, I can do My job and enjoy a movie on Saturday night by going through this annoying procedure.

Thanks

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>SignatureDoesNotMatch</Code>
<Message>
The request signature we calculated does not match the signature you provided. Check your key and signing method.
</Message>
<AWSAccessKeyId>AKIAJHGQWPVXWHEDJUEA</AWSAccessKeyId>
<StringToSign>
GET application/x-www-form-urlencoded 1550702001 /assets.displaylink.com/live/downloads/software/f1300_DisplayLink%20USB%20Graphics%20Software%20for%20Windows%209.0%20M1.exe
</StringToSign>
<SignatureProvided>NX0WcSTbHiTZJT1TZ17IRrrAulA=</SignatureProvided>
<StringToSignBytes>
47 45 54 0a 0a 61 70 70 6c 69 63 61 74 69 6f 6e 2f 78 2d 77 77 77 2d 66 6f 72 6d 2d 75 72 6c 65 6e 63 6f 64 65 64 0a 31 35 35 30 37 30 32 30 30 31 0a 2f 61 73 73 65 74 73 2e 64 69 73 70 6c 61 79 6c 69 6e 6b 2e 63 6f 6d 2f 6c 69 76 65 2f 64 6f 77 6e 6c 6f 61 64 73 2f 73 6f 66 74 77 61 72 65 2f 66 31 33 30 30 5f 44 69 73 70 6c 61 79 4c 69 6e 6b 25 32 30 55 53 42 25 32 30 47 72 61 70 68 69 63 73 25 32 30 53 6f 66 74 77 61 72 65 25 32 30 66 6f 72 25 32 30 57 69 6e 64 6f 77 73 25 32 30 39 2e 30 25 32 30 4d 31 2e 65 78 65
</StringToSignBytes>
<RequestId>CE4609F97A712A05</RequestId>
<HostId>
CLYMRUMSzZjYM5WPqY+YBzoQg0HoAPptWfpS08e9uQb9x0qfT8lWNvuZ/Mm0UiPnSlIfc+GGS7U=
</HostId>
</Error>

The Linux Foundation is the place to get things into the kernel. They will help you integrate your hardware into the mainline kernel without compromising any internal IP you may be worried about. Its really the only way to get a driver working for any OS. Work with upstream not against it.

This translates to Windows and OS X as well. I was frustrated getting my device working with Windows. Complete pain and not plug and play by any means. OS X Mojave doesn't work at all and Linux shows the same behaviour. Flickering on and off rapidly an when looking at system logs it seems to be in a constant connect / disconnect rapid loop.

Open Source the whole driver stack and work with the upstream OS developers to get support built into the kernel will make your hardware plug and play on all operating systems.