search

novnc / noVNC

VNC client web application
https://novnc.com
Other
11.43k stars 2.27k forks source link

graphic glitch for noVNC #1023

Closed leslie-qiwa closed 6 years ago

leslie-qiwa commented 6 years ago

We're using noVNC in our application. Sometimes, we found some graphic glitch which doesn't have in native VNC player. Does anyone have any clue on it?

screen capture

samhed commented 6 years ago

What version of noVNC are you using?

leslie-qiwa commented 6 years ago

thanks for reply. It is from master : a4d51bd22048df40963c999903e5156f343df293

CendioOssman commented 6 years ago

Which browser and VNC server?

leslie-qiwa commented 6 years ago

Safari - Version 11.0.2 (13604.4.7.1.3) Firefox - 57.0.2 Chrome - Version 64.0.3282.167 (Official Build) (64-bit)

We are using this vncproxy

DirectXMan12 commented 6 years ago

Can you send us a recording with the issue?

leslie-qiwa commented 6 years ago

Thanks for prompt reply. I'm trying to identify if problem is at vncproxy side. Once it is done, will update you.

leslie-qiwa commented 6 years ago

Just one correction, we are using https://github.com/libvirt/libvirt-console-proxy as proxy.

For more information. Our server is ESX. Per this issue: https://github.com/novnc/noVNC/issues/44, seems like ESX VNC is not officially supported. It works in our side if using above proxy, then we saw above glitch sometimes.

leslie-qiwa commented 6 years ago

After more investigation, I found out this issues is at our implementation. So I'll just close it. Seems like VMWare ESXi uses tight_png encoding, so it would be great if https://github.com/novnc/noVNC/issues/51 can be solved.

CendioOssman commented 6 years ago

51 is already solved, so I'm not sure what you are waiting for in that case? And #44 is about extra stuff, not the basic things like working image.

leslie-qiwa commented 6 years ago

Thanks for the confirmation. Seems like function encodingName(num) at core/encodings.js need add support for pseudoEncodingTightPNG as well.

It is interesting that above graphic glitch problem can happen if I just change encodingTight to -260. But once I enable pseudoEncodingTightPNG, it will display correctly.

leslie-qiwa commented 6 years ago

1026 is created. It works in our ESX environment.