You should not run the x2gokdriveclient directly. X2Go client is using it exactly same way as it's using nxproxy. Just in the session config of x2go client you need to select checkbox "run in x2gokdrive" and be sure that all needed components are installed (x2gokdriveclient on the client and x2gokdrive on the server). Apart of this, the configuration of the session is the same as when using NX protocol. X2Gokdrive also adapting the image quality to the network. When the picture is "static" it redraws it using PNG compression, so there are no JPG artifacts anymore.

PS
If you are using Windows, the "default" Windows client is too old and don't have the x2gokdriveclient. But there is my custom build for Windows somewhere on the packages.x2go.org


Am 17.12.24 um 14:23 schrieb [email protected]:
Hello!

I already tested Chrome, Palemoon and all the browsers I could find “back 
then”. As a result, there was either no relevant difference in terms of 
stuttering, or the application that was most important to us was not running in 
the respective browser. The latter was and is the case with PaleMoon, which 
freezes when using the application.

I also tested various desktops and there were no relevant improvements in terms 
of stuttering.
I already know the comparison video from back then.

The browser application is a very fast-running, industry-specific application 
over the web, without any fuss, and we need it 24/7. There is practically no 
alternative for us.

Therefore, I had no choice but to switch to LTSP. Since then, I've missed the 
nice option of having my desktop available anywhere without
having to log out, etc.

Alex's report sounds very positive.
So I just tried installing kdrive, but somehow the client doesn't want to work. 
Either I got an ancient installation description or it's too complicated for 
me. But I'll take another look at it. Everything was much easier with x2go.

###

~$ x2gokdriveclient

(x2gokdriveclient:156382): dbind-WARNING **: 21:14:51.559: Couldn't register 
with accessibility bus: Did not receive a reply. Possible causes include: the 
remote application did not send a reply, the message bus security policy 
blocked the reply, the reply timeout expired, or the network connection was 
broken.
qt.svg: Cannot open file ':/img/pin.svg', because: No such file or directory
qt.svg: Cannot open file ':/img/pin.svg', because: No such file or directory
../src/client.cpp:781:connectToServer():  Connecting to remote host 
localhost:15000 over TCP
../src/client.cpp:2121:socketError():  Connection refused
../src/client.cpp:2649:reinitCaches():  Clearing all caches
../src/client.cpp:2663:reinitCaches():  Done

###


But I'll take another look at it.

Thanks in advance for the feedback!

Olaf





Am Wed, 11 Dec 2024 00:37:03 +0100
schrieb Ulrich Sibiller <[email protected]>:

For me Chrome is much faster than Firefox. You can try x2gokdrive,
maybe it is faster

Uli


Am Wed, 11 Dec 2024 15:28:50 +0100
schrieb Stefan Baur <[email protected]>:

Am 10.12.24 um 20:26 schrieb [email protected]:
Hello!
Some time ago after years of use I largely replaced x2go with LTSP
because surfing in the browser was no longer practical. It jerked
so much that we couldn't work with it.

Is there a real solution for this now?
Several, actually. Depending on how you use X2Go.
First of all, Single Application Mode/Published Application Mode seems
to be particularly ugly with browsers. I think it has to do with lack
of XDAMAGE support in that mode or something like that? (Devs, feel
free to chime in here, with a technical explanation)
So using a Desktop Session (I would suggest MATE or XFCE with
Compositing disabled, or something even more minimalistic like
OpenBox) would improve things if you were using Single Application
Mode/Published Application Mode in the past.

Next, there is one browser that we know of that was forked off of
Firefox before they introduced all the things that kill browser
performance on remote displays. It's called Pale Moon. You might have
to use the GTK2 version, though (they offer GTK2 and GTK3)? Again,
something that the Devs should be able to answer in more detail.

Last, as Uli already mentioned, you could try using X2Go-KDrive
instead of X2Go-NX. This protocol was designed to allow the use of
"modern", eye-candy-rich desktops like Gnome3 and KDE4 and above, but
it also speeds up browser performance. Here's a quick video comparing
the Chromium web browser using X2Go-NX on the left and using the new
X2Go-KDrive on the right: <https://youtu.be/2n0IZo02Zrc>

Kind Regards,
Stefan Baur


Am Thu, 12 Dec 2024 17:07:25 +0100 (CET)
schrieb [email protected]:

Hello Olaf,

my customers are using x2gokdrive productively since 2019. This
protocol doesn't have the limitations of NX. It requires however
better network than NX. In my opinion, if you are not hanging behind
some old DSL connection, there is no reason to use NX anymore. I can,
for example, watch full screen youtube videos with good quality in my
office in Germany from my home in Mexico through VPN. Be sure that
you are using the latest versions from heuler repo for both server
and client when you are trying.

regards,
Alex


_______________________________________________
x2go-user mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-user


--
-----------------------------------------------------------
Oleksandr Shneyder        | Email: [email protected]
phoca GmbH                | Tel. : 0911 - 14870374 0
Schleiermacherstr. 2      | Fax. : 0911 - 14870374 9
D-90491 Nürnberg          | Mobil: 0163 - 49 64 461

Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder

Amtsgericht München       | http://www.phoca-gmbh.de
HRB 196 658               | http://www.x2go.org
USt-IdNr.: DE281977973
-----------------------------------------------------------

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
x2go-user mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-user

Reply via email to