Re: Complete breakage of KRFB and KRDC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michele Calgaro via tde-users wrote:

> 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

If I may add some notes from my experience
I'm not using KRFB, but frequently KRDC. KRDC works fine to the tightvnc
linux machine, but can not cope with modern windows RDP. I was looking into
the code, because xfreerdp is working just fine with new windows but had to
give up as it was too complicated to adjust and it was also too time
consuming :(
So now for windows 10 I have scripts that run xfreerdp 

____________________________________________________
tde-users mailing list -- users@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@xxxxxxxxxxxxxxxxxx



[Index of Archives]     [Trinity Devel]     [KDE]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux