Am 29.01.2012 00:46, schrieb Mike Gabriel:
From my point of view it is indeed not necessary to recompile NX to be used with libjpeg-turbo. People may correct me if that is not true.
So for a running X2Go server and client you can drop in
on squeeze: apt-get install libjpeg-turbo62 on wheezy, sid: apt-get install libjpeg-turbo8
And your host should then run with libjpeg-turbo instead of libjpeg. Please note, that this change affects every application on that system. So... no warranty given from our side. Also, if testing libjpeg-turbo, please read the documentation of libjpeg-turbo:
Guys,
it would be really helpful if someone could type up a step-by-step guide for testing. I'd love to try this out, but either I *did* something wrong or something *goes* wrong, as the following had no positive effect whatsoever:
The only effect I saw was a "screen hang" when leaving YouTube for another web site, and no speed increase whatsoever. :-(
Looking at the discussion in this thread and at the libjpeg-turbo documentation leaves me even more confused than before.
My questions, in particular, are: libjpeg-turbo - gain less speed than a fullscreen session - but that was
years ago and may have changed and may not apply to X2Go at all, I don't know.) 3) Is the library required on both the server *and* on the client? 4) Should it work "out of the box" after installing the package, or do I have to change some file somewhere to add the library path? 5) Do I have to restart a daemon after changing this file? 6) Why was I able to install the package without apt-get telling me it would remove the "non-turbo" library package? To make this clear, I don't complain about a lack of a warning (Mike did provide such a warning in his posting), but I'm surprised about the lack of *action* i.e. no library package has been removed when I installed the libjpeg-turbo62 package.
Kind Regards, Stefan