17 May
2023
17 May
'23
7:33 p.m.
Hi, Michele
05.05.23 15:55, Michele Calgaro via tde-users wrote:
So, the KRFB hungs at wrong passwords and crashes at the session closing
are from one source and that is the thread force closing and that I have
fixed long ago by the patch *krfb-crash_at_disconnect.patch* —
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2972.
And the performance decreasing is a real regression of the VNC libraries
due to switching to some hungrier compression algorithms what causes:
• removing support of the "Low quality" in the server library, when the
client one still works and fast;
• high CPU load on server, especially for the "High quality";
• high CPU load on client at enabling the scale.
Once I am going to compare performance of the new libraries in 14.1 and
old ones in 14.0 and maybe return the old one at very high difference
taking in account of missing any advantage in the new ones.
The second patch *krfb-new_symbols_appending.patch* is for many special
symbols support, which are also all symbols different from ASCII-Latin,
especially the Cyrillic ones which I can enter only about 10 and next I
get only ASCII. This code is missing in the VNC server library, hosted
in vncserver and I have adapted it long ago for KRDC with notifying in
Bugzilla — http://bugs.pearsoncomputing.net/show_bug.cgi?id=3014
Regards, Roman
All are native
ones — only VNC on fast hardware in local network and
Debian 11:
1. KRDC(14.0.13) > KRFB(14.1.0) = dead-cycling KRFB without a
possibility even connect more
2. KRDC(14.1.0) > KRFB(14.0.13) = very slow KRDC screen with no
possibility of closing
And all this works only with 14.0.13.
If you talk that works, I'll see what is happening with krfb in my case.
I
didn't do a mixed test (R14.1.0 and R14.0.13), just R14.1.0 to
R14.1.0. KRDC (vnc) to KRFB did show some slowness in updating, like
500ms or so and it seemed weird to me since this was over a local wifi
network. I don't know if R14.0.13 was quicker, you have definitely
more experience on this than I have.
It is definitely good to look into those issues you highlighted and I
think it would also be good to make sure mixed configuration
connection (R14.0.13 to R14.1.0 or viceversa) still work.
The switch to standalone libtdevnc was done many years ago in master.
I am not sure of the details but in any case if it does not behave as
well as R14.0.x we have to look into this, since regressions are not
good.