search

FreeRDP / FreeRDP-WebConnect

A gateway for seamless access to your RDP-Sessions in any HTML5-compliant browser
515 stars 1.6k forks source link

Drawing issues, graphical corruptions? #130

Open ncalvert opened 8 years ago

ncalvert commented 8 years ago

I am using this fork https://github.com/c64cosmin/FreeRDP-WebConnect.git

... which is the only version i can get to successfully build. I am seeing artifacts\graphical corruptions on all browsers to a Windows 2008 R2 machine.To define it a little better, parts of the images are not drawing, i see lines, undrawn boxes. It is worse in a console. Text appears as soon as i type it, in fact it is very responsive, however parts of the console are not drawn. Moving the mouse causes the box to be drawn a little better (sorry, this is a horrible explanation!) This is not something that changes. If i let a session sit for an hour the 'corruptions' will remain the same. Can i double check before I wider the scope of my testing - is this to be expected or is something wrong?

Ubuntu 14.04 64bit about 4GB RAM, lots of CPU, this is a VM

Thanks very much for your hard work on this.

ncalvert commented 8 years ago

Interestingly this doesn't happen on Windows 2012 R2 - just spun up another VM. Very odd.

c64cosmin commented 8 years ago

@calvert-tagadab First of all you should be using the master on https://github.com/FreeRDP/FreeRDP-WebConnect We also have a installer if you are using WebConnect on Windows https://www.cloudbase.it/downloads/FreeRDPWebConnect.msi - this is the installer for webconnect https://www.cloudbase.it/downloads/FreeRDPWebConnect_Beta.msi - this is the newest build we have(might be unstable)

Could you tell me what branch from my fork have you built? Also, what hypervisor are you using?

ncalvert commented 8 years ago

I built the master of git@github.com:c64cosmin/FreeRDP-WebConnect.git.

I don't want to muddy the water here with too many disparate issues, but for clarity i am not using Windows to run FreeRDP-WebConnect. I am running and building it on Linux. I am connecting to Windows clients. The issues I am seeing (graphical issues mentioned above) are only with Windows 2008 R2, i tried Windows 2012 R2 and the performance was incredible . i will continue to do more testing to see if i can narrow down the problem.

Perhaps a larger issue - and the reason i am using your fork - is the the master (https://github.com/FreeRDP/FreeRDP-WebConnect) has never, ever built for me on any distribution of Linux from Ubuntu 12 through to Centos 7, I always get 'error: ‘wsgate::WsGateService’ has not been declared' errors. As far as i cant tell I am following the build intructions to the letter. Your c64cosmin fork builds fine, Building this fork was suggested here in a different issue (Compilation issues on a variety of O/S #93).

Right now I still cant build the master on a fresh install of Ubuntu 14, Centos 6 or Centos 7. I can only build your fork. But as a i say, sorry if i'm confusing things with multiple issues. It would seem sensible to try and somehow fix the compilation issues and build the master of https://github.com/FreeRDP/FreeRDP-WebConnect and see if my issue with RDP to Windows 2008 R2 persists.

Cheers.

GhostEye85 commented 8 years ago

I am also having the graphical issues mentioned here on a windows 2008 R2 server. I have FreeRDP-WebConnect installed on the windows 2008 R2 machine, and connecting to that same server. I have tried both the stable and beta release msi files listed here. Both produce the same results.

The wsgate.exe service is using 13% cpu (about 1 core) constantly while connected. I saw in another post that the beta build was to fix the cpu issues, but it did not resolve it in my case.

I tested the same setup using a 2012 R2 server and although the cpu usage was still high (using the beta msi) the graphical issues were not present. As calvert concluded, the issue seems to be only present when connecting to Windows 2008 R2 servers. Unfortunately due to legacy software support, I need to be able to connect to 2008 R2.

I'm curious if you think this is something that is fixable or if it is just an inherent problem with connecting to 2008 R2. Any advice is appreciated. Thanks!

c64cosmin commented 8 years ago

@dkramer85 The issues that you have is fixable (both the CPU and drawing), though the solution will be delayed for a while.