Can you try to kill DisplayLinkManager when this happens?
A harsh "sudo killall DisplayLinkManager" would do.
This will tell us on which side the issue is.
It would also be useful to have logs following
http://www.displaylink.com/support/ticket.php?id=269
Please collect the logs just after killing DisplayLinkManager when the issue has occurred
Cheers
Carlo