Issues with LibreOffice on additional monitors

[pjlbyrne]

Hi,

this issue affects me too. I have a recently purchased Dell XPS13 9360 and a Dell 3100 dock.

From here:
https://ask.libreoffice.org/en/quest...pletely-blank/
I see this may be an OpenGL issue.

From here:
https://www.dell.com/community/Lapto...s/td-p/5171483

RE: Latitude E5570, D6000 dock, 3D Hardware/OpenGL issues
It's because the D6000 uses a DisplayLink chip rather than allowing the displays to be driven directly be the GPU. From my post in another thread: DisplayLink means that technically the dock can support extra displays (and at higher resolutions) compared to more traditional options, but DisplayLink achieves this by not having the displays actually driven by the system's GPU. Instead, the system's CPU and GPU compress display data for transmission as standard USB data, and the DisplayLink chip in the dock then decompresses it before sending it to the displays. This allows displays to be attached over regular USB (rather than just USB-C, which actually does have a native GPU output wired to it), but the compression also means that when large portions of the display area change at once, such as when watching full screen video or gaming, the display can appear to bog down and/or show compression artifacts. This can also occur when a lot of USB activity is occurring with another device (such as a file transfer to/from an external hard drive) because there's bandwidth contention on the USB bus, and finally if you're running some other CPU -intensive task, which will create resource contention for the display data compression.

DisplayLink also drains battery life significantly more quickly, which admittedly isn't an issue with a dock setup, but DisplayLink products exist in other form factors.

Bottom line: You should consider using a traditional E-Port dock instead, which will allow your displays to be driven directly by the GPU.

So, is this a bug, or does the dock just not support opengl rendering on the external montitors? Has anyone found a workaround or solution for this?

Regards
Patrick