With the recent drivers the behavior of the task icon changed. It is now always visible. It would be great to add an option so that the user could define the preferred behavior.

Dual Displays on Android App

On my Windows 7 x64 computer, in times of heavy CPU usage, the mouse cursor becomes extremely choppy. This is because DisplayLinkManager's priority is the same as that of the process using all the CPU time.

I have found that if I set DisplayLinkManager.exe to High priority, the mouse cursor remains mostly smooth. Please consider defaulting DisplayLinkManager.exe priority to High at startup. This is an easy change in code and would solve one big irritation with this product.

Add these controls to the current displaylink taskbar application.

You don't have to reinvent the wheel: https://github.com/AdnanHodzic/displaylink-debian

That also would make it easy for Deepin Linux to adapt the drivers. Deepin is Linux distro #1 in China! Just think: Deepin + Lenovo (Thinkpad)

The script deployed by the displaylink installer at /opt/displaylink/udev.sh is triggered by udev rules and will run:

systemctl start displaylink-driver

Under certain conditions this will trigger "udevadm settle" to block forever as it leaved processes left and can't return.

I found https://github.com/NixOS/nixpkgs/pull/51760/commits/c72bb28b9cb5138d39647f8fa12394443fea682d which fixes the issue for them.
Applying the same to /opt/displaylink/udev.sh in Ubuntu 20.04 works just fine, the boot is fast again and functionality had no negative impact.

So please could you change this line in your code to be like:
systemctl start --no-block displaylink-driver

Manuals and better support for all products you sell

With 5.1.1 on MacOS 10.14.5, screen zoom/pan (Ctrl-Scroll Up) does not work properly on the DisplayLink screen... it tears and only zooms part of the screen.

It would be good if you could configure to disable the icon of the DisplayLink manager in the menu bar (on macOS).

The logfiles in /var/log/displaylink currently contain hashed garbage. It would be nice if I could read them.

In older versions of Windows there use to be a capability to have different profiles for a "docked" PC and an "unlocked" PC. This would be a great capability for you to add into your product since it is now a corporate mandate.

My main issue is that I set up my desktop the way I like it and then when I either connect the USB or disconnect the USB all my settings are lost and I can't find my desktop icons anymore. This is a negative impact on my productivity.

See:
https://pagure.io/dlm/blob/master/f/init/dlm.service

It would be better if it could fail with an error in case the file already
exists and is not authentic (from previous installation).

Thanks for considering.

My external monitor (Acer ET322QK) is detected with the 5.1 Displaylink driver, but only at 1080p resolution or lower. Any resolution above 1080p is unavailable for selection

This DisplayLink driver will slowly and continuously cache RAM on the system. After about 12 hours, for me it'll consume nearly 8GB of RAM and force a restart. Rinse and repeat.

Can confirm as no memory leak occurs when not using the dock.

We are trying to automate software updates and track inventory of DisplayLink drivers in our macOS environment. Trying to parse versions when the value reports as 4.1 (11) or DisplayLink Driver 4.1.11 - Copyright 2003... makes it difficult.

In the driver Info.plist file, please set the CFBundleShortVersionString key in the x.x.xx format. Even better, clean up the CFBundleGetInfoString

17 inch version of the ASUS MB169B+

While the firmware update is Silent, in large scale deployments it would be useful to know / be able to report on the Firmware version.
This would enable admins to rule-out old firmware as the cause of faults and detect where an older client is still in use.

If this information is readily available it could be added as another command in the Dock Management Tool, or in the Support Info Tool

This would allow Mac Admins to automate the process of downloading DisplayLink software whenever there is a new version using open-source projects such as autopkg. The implementation of a ToS page breaks our current functionality.

Perhaps even make a specific URL for admins, that when used implies that we agree to the ToS.

This would allow us to push DisplayLink updates to our users much faster.