[jira] [Commented] (GUACAMOLE-1285) Poor rendering over VNC

["Nick Couchman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282980#comment-17282980 ] 

Nick Couchman commented on GUACAMOLE-1285:
------------------------------------------

[~gareth.somerville1]:
A couple of comments about this:
- JIRA is not intended to be a generic support forum, so I suggest that you start by posting this question to the mailing list: http://guacamole.apache.org/support/
- As you've confirmed that this only happens in Chrome and not in Firefox, and as turning off browser hardware acceleration resolves the issue, this sounds more like an issue with the browser and not with Guacamole, in which case you'd need to report this to the Chrome developers.

> Poor rendering over VNC
> -----------------------
>
>                 Key: GUACAMOLE-1285
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1285
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.0.0, 1.3.0
>         Environment: OS: Linux, Windows; Browsers: Chrome, Opera
>            Reporter: Gareth Somerville
>            Priority: Major
>              Labels: performance
>         Attachments: image (5).png, image (6).png, image (7).png, image (8).png
>
>
> We currently use Guacamole to display a VNC connection from a remote Chromium browser running at 1920x1800 full screen.
> We began getting complaints from users in mid-late September about the display appearing 'blurry', and upon investigation found that this appeared to be that some UI elements are rendering incorrectly as shown below - this is most noticeable with text and causes difficulties reading, particularly at smaller font sizes.
> !image (5).png!  !image (6).png! 
> After looking for solutions, we have found that some (but not all) users have seen this go away when displaying the Guacamole display at full screen on a screen greater than or equal to 1920x1800. A more reliable, but more invasive fix is to disable hardware acceleration in the browser. This seems to solve the problem for any user that raises the issue. Below is a comparison with the above after disabling hardware acceleration.
>  !image (7).png!  !image (8).png! 
> We haven't had any reports of this issue in browsers using other rendering engines (i.e. Firefox), so this implies that an update to that engine is what caused the issue. I haven't been able to narrow this down for sure, but it could be version 86 of Chrome where this was introduced. Due to the nature of the issue, it could also be related to drivers, but we have seen reports on both Windows and Linux, so I'm inclined to think it is the rendering engine.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)