DisplayLinkManager always crashes with "Aborted"

[psypete]

Every time I try to run DisplayLinkManager, it exits with "Aborted":

linux:/opt/displaylink# /opt/displaylink/DisplayLinkManager -debug -logging
GFYFEKZlPOOleEFNXqYmG7953hBLErVY3zvTX7HRDTdP7ZfDDi77fJ6N50XlLv+fIuB8kJJP8hqlPNFcm6tyOLmXV0q4XUWv4f9tG0Q8+tO/dOhfAQZkQ7ed4zW6MxBGdUSKbO/nTZQdVUPE410qdqzmTZtb+EHUcPB2Xcw2kfEDS6W0Pqji9yDSQ0lXC1I+Jy0GgTFENQfiGP4Gu829z+64n2z58M/f3IiD0pD0DEsl8dmgqbIzyU+DzQfZ7c46GkrD4GYIbCWq1wNlNvhRS+maszrkRVYhj+QghyhaNMA=
+1udEOrFVdWSCylUQB25/y6Ief2H2i31P9YDOKi59f49oa+bj/2tFJ3nI6n22uL1caVyDx4dlNbmnxbukYoC7K0cdUJC9ONSy6A05eja0hnwKLogA2kVx0PGzrCfTbE686sJxrJ7YrOCfPi7Zk4cNQ==
o7T0RWiCR5P+fcrZrvAVMl2m6nfF4polw/ls7fdkSZ1hx583Vi1w92+u0gKdl1DInHcywNq2TOp2n4PR4sHuWQTFBb4/oKHnW+nrKynMTIhuIO0n7Cn01LphAJVuGYuGeSVDxRw308jfJ3WsfYZMYOmHOh9l1WvbUAlZPgp6jVY=
Y7T7YJTOK1m8ZtgLASvnc7L4Ag5VkZt41j4tNZfd+blyGiOkTf5PnXuHWzoSTl4fo1G7URIjc0ZJYs+uuQjoucyOCjeIYhhgLENPASl6c4wZ1orDRYRdp6ZY8KYBlCcjtYoTExYMwSHCVfusWIAvHu/Y82b0JQzthVVp9hdP4Ak=
CmDtHsZegBsNNQ6vmo8wbzs1ji/5c7TcriH47u7o2ZyVWUuMjCDzZUwqhHCGXlmJaBQ0tSDfMZBdp68BFRF09VcEm8xUGLOJ0aaSKTiqEk8oW8Bld0BYwDlR8SJtT8m+b/7gA/a+DTx5UpHTysaIjA==
lKfw/DQfaw0EXa9rfa/zA7xIVwF4GggBkQZTbQJejsC3FoOHxijlNi9NoqHP6o0vFkh50gdDuLca8UplcrqZNlXjsu8qhBzMgd0Tc7pHBhfRT01g+CscS9JSeDeg0U7AznIPQ9pdbRAh+h2+nUf7ZgZ/NqLOGciNOlLB508GQVc=
vtTgIFZ/blTLenwKdg+hdUkbM7G15zyQxaYP6x/ghEGN/+i3CWaZa0ygoi7RHRT2ahJcdZRbl/bjwPfy4QfxyjcwuuC+iF3RRx4LeMx509KqnGli+pcD9F8D1dvCEIrpG5BEWpVWmhOU5M59+7t/qg==
s2cs6J8WlU/0e6lJqzy7/InNnF8EGEESAZLPlRWf4jKClWK+otoEkfb6eNYr0JvcM3ACJqs9qxqK/p6bCeEh3x9wSLmdzBu9aKyAVCLXsoiICz5FowJsXzHR7H2b15oX
Aborted
linux:/opt/displaylink#

Can someone please interpret the debugging output??

[rboerner]

Originally Posted by psypete

Every time I try to run DisplayLinkManager, it exits with "Aborted":

linux:/opt/displaylink# /opt/displaylink/DisplayLinkManager -debug -logging
GFYFEKZlPOOleEFNXqYmG7953hBLErVY3zvTX7HRDTdP7ZfDDi77fJ6N50XlLv+fIuB8kJJP8hqlPNFcm6tyOLmXV0q4XUWv4f9tG0Q8+tO/dOhfAQZkQ7ed4zW6MxBGdUSKbO/nTZQdVUPE410qdqzmTZtb+EHUcPB2Xcw2kfEDS6W0Pqji9yDSQ0lXC1I+Jy0GgTFENQfiGP4Gu829z+64n2z58M/f3IiD0pD0DEsl8dmgqbIzyU+DzQfZ7c46GkrD4GYIbCWq1wNlNvhRS+maszrkRVYhj+QghyhaNMA=
+1udEOrFVdWSCylUQB25/y6Ief2H2i31P9YDOKi59f49oa+bj/2tFJ3nI6n22uL1caVyDx4dlNbmnxbukYoC7K0cdUJC9ONSy6A05eja0hnwKLogA2kVx0PGzrCfTbE686sJxrJ7YrOCfPi7Zk4cNQ==
o7T0RWiCR5P+fcrZrvAVMl2m6nfF4polw/ls7fdkSZ1hx583Vi1w92+u0gKdl1DInHcywNq2TOp2n4PR4sHuWQTFBb4/oKHnW+nrKynMTIhuIO0n7Cn01LphAJVuGYuGeSVDxRw308jfJ3WsfYZMYOmHOh9l1WvbUAlZPgp6jVY=
Y7T7YJTOK1m8ZtgLASvnc7L4Ag5VkZt41j4tNZfd+blyGiOkTf5PnXuHWzoSTl4fo1G7URIjc0ZJYs+uuQjoucyOCjeIYhhgLENPASl6c4wZ1orDRYRdp6ZY8KYBlCcjtYoTExYMwSHCVfusWIAvHu/Y82b0JQzthVVp9hdP4Ak=
CmDtHsZegBsNNQ6vmo8wbzs1ji/5c7TcriH47u7o2ZyVWUuMjCDzZUwqhHCGXlmJaBQ0tSDfMZBdp68BFRF09VcEm8xUGLOJ0aaSKTiqEk8oW8Bld0BYwDlR8SJtT8m+b/7gA/a+DTx5UpHTysaIjA==
lKfw/DQfaw0EXa9rfa/zA7xIVwF4GggBkQZTbQJejsC3FoOHxijlNi9NoqHP6o0vFkh50gdDuLca8UplcrqZNlXjsu8qhBzMgd0Tc7pHBhfRT01g+CscS9JSeDeg0U7AznIPQ9pdbRAh+h2+nUf7ZgZ/NqLOGciNOlLB508GQVc=
vtTgIFZ/blTLenwKdg+hdUkbM7G15zyQxaYP6x/ghEGN/+i3CWaZa0ygoi7RHRT2ahJcdZRbl/bjwPfy4QfxyjcwuuC+iF3RRx4LeMx509KqnGli+pcD9F8D1dvCEIrpG5BEWpVWmhOU5M59+7t/qg==
s2cs6J8WlU/0e6lJqzy7/InNnF8EGEESAZLPlRWf4jKClWK+otoEkfb6eNYr0JvcM3ACJqs9qxqK/p6bCeEh3x9wSLmdzBu9aKyAVCLXsoiICz5FowJsXzHR7H2b15oX
Aborted
linux:/opt/displaylink#

Can someone please interpret the debugging output??

DisplayLink logs are encrypted in order to protect their intellectual property, so you will not be able to decrypt them.

If you have not done so already, I would suggest reporting the issue by following the process outlined here --> https://support.displaylink.com/know...to-displaylink