Hi Michal,
Ok, so there seems like several different things going on on my machine - Id been previously using the nvidia X server + intel X server (I need the nvidia one for USBC monitor support) but using the intel server, changed via nvidia-settings, for use with the external monitor on the road as that worked OK with driver 1.1.62.
Now, it seems that if I try to install or uninstall with the intel server in use, the machine locks up completely with no associated information in syslog.
So off the back of that I've rolled everything back to use nouveau temporarily. Now it seems I can reinstall 1.3.52 which I've plugged in and left for a few minutes. It still doesn't work but syslog looks as follows which is a step closer but repeats ad-nauseum :
Feb 20 15:22:16 zed systemd[1]: Started Session c3 of user pev.
Feb 20 15:22:19 zed kernel: [ 40.769570] usb 1-1: new high-speed USB device number 7 using xhci_hcd
Feb 20 15:22:19 zed kernel: [ 40.949372] usb 1-1: New USB device found, idVendor=17e9, idProduct=ff05
Feb 20 15:22:19 zed kernel: [ 40.949374] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 15:22:19 zed kernel: [ 40.949375] usb 1-1: Product: E1659Fwu
Feb 20 15:22:19 zed kernel: [ 40.949376] usb 1-1: Manufacturer: DisplayLink
Feb 20 15:22:19 zed kernel: [ 40.949377] usb 1-1: SerialNumber: GFKE1JA000408
Feb 20 15:22:19 zed mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Feb 20 15:22:19 zed mtp-probe: bus: 1, device: 7 was not an MTP device
Feb 20 15:22:19 zed gnome-session[2734]: (gnome-software:2893): Gs-WARNING **: failed to call gs_plugin_add_updates_historical on fwupd: failed to start fwupd: Error calling StartServiceByName for org.freedesktop.fwupd: GDBus.Error
rg.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.fwupd': timed out
Feb 20 15:22:19 zed gnome-session[2734]: (gnome-software:2893): Gs-WARNING **: failed to call gs_plugin_refine on appstream: cannot process file of type text/plain
Feb 20 15:22:20 zed systemd[1]: Starting DisplayLink Manager Service...
Feb 20 15:22:20 zed sh[3454]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:20 zed sh[3454]: Module evdi/1.3.52 already installed on kernel 4.4.0-59-generic/x86_64
Feb 20 15:22:20 zed sh[3454]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:20 zed systemd[1]: dlm.service: Control process exited, code=exited status=1
Feb 20 15:22:20 zed systemd[1]: Failed to start DisplayLink Manager Service.
Feb 20 15:22:20 zed systemd[1]: dlm.service: Unit entered failed state.
Feb 20 15:22:20 zed systemd[1]: dlm.service: Failed with result 'exit-code'.
Feb 20 15:22:20 zed systemd-udevd[3429]: Process '/opt/displaylink/udev.sh /dev usb-001-007-DisplayLink_E1659Fwu_GFKE1JA000408 /dev/bus/usb/001/007' failed with exit code 1.
Feb 20 15:22:25 zed systemd[1]: dlm.service: Service hold-off time over, scheduling restart.
Feb 20 15:22:25 zed systemd[1]: Stopped DisplayLink Manager Service.
Feb 20 15:22:25 zed systemd[1]: Starting DisplayLink Manager Service...
Feb 20 15:22:25 zed sh[3578]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:25 zed sh[3578]: Module evdi/1.3.52 already installed on kernel 4.4.0-59-generic/x86_64
Feb 20 15:22:25 zed sh[3578]: modprobe: ERROR: could not insert 'evdi': Invalid argument
Feb 20 15:22:25 zed systemd[1]: dlm.service: Control process exited, code=exited status=1
Feb 20 15:22:25 zed systemd[1]: Failed to start DisplayLink Manager Service.
Feb 20 15:22:25 zed systemd[1]: dlm.service: Unit entered failed state.
Feb 20 15:22:25 zed systemd[1]: dlm.service: Failed with result 'exit-code'.