<div dir="ltr">Hi,<div><br></div><div>Unfortunately setting<span style="font-size:12.8px"> </span><span style="font-size:12.8px">MOZ_DISABLE_IMAGE_OPTIMIZE=1 did not make a difference. Thanks though.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Aug 27, 2016 at 6:36 PM, Ulrich Sibiller <span dir="ltr"><<a href="mailto:uli42@gmx.de" target="_blank">uli42@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Sat, Aug 27, 2016 at 5:31 PM, Jordan Sokolic <<a href="mailto:jordan@twiggle.com">jordan@twiggle.com</a>> wrote:<br>
> I should have probably mentioned that this lag also occurs when running the<br>
> X2Go client directly on the server itself, so it doesn't seem to be an issue<br>
> with the WAN link, Windows 10, etc. For the sake of comparison I ran Firefox<br>
> 48.0 via X2Go on another machine on the same 100Mbit LAN as the server, then<br>
> ran it again in a forwarded X11 SSH session (compression enabled); the<br>
> latter demonstrated no noticeable lag while the X2Go session struggled to<br>
> keep up.<br>
<br>
</span>Does setting MOZ_DISABLE_IMAGE_OPTIMIZE=1 (env var for firefox) help?<br>
<br>
Uli<br>
</blockquote></div><br></div>