View Single Post
Old 02-10-2016, 07:45 AM   #3
Junior Member
Join Date: Feb 2016
Posts: 1
Default The bug root cause and workaround

Everything is quite simple: the reason is the bug in the DisplayLinkManager binary blob, it creates /root/.dl.xml once (resembling m$ windows registry hive?) and doesn't validate it properly later as also does not catch exceptions, just aborts. So, if it saved empty /root/.dl.xml, it fails. The workaround is to delete this file before running DisplayLinkManager. Also, it will help in the case if usb tree structure is changed and it can't find displays.

There is also a second bug in the driver, frequently preventing xrandr from being executed. DPI resolution is improperly set to the totally wrong value (minimal signed 32-bit integer value) and xrandr doesn't check the DPI value validity and aborts with FPE.
deztructor is offline   Reply With Quote