Bug 5610 - Sometimes we don't get a framebuffer update after panning
Summary: Sometimes we don't get a framebuffer update after panning
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.8.0
Assignee: Samuel Mannehed
URL:
Keywords: hean01_tester, prosaic, upstream
Depends on: 5611
Blocks: 6132
  Show dependency tree / graph
 
Reported: 2015-08-20 11:07 CEST by Samuel Mannehed
Modified: 2017-03-27 14:19 CEST (History)
2 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Samuel Mannehed cendio 2015-08-20 11:07:22 CEST 
When panning we require new data from the server to draw the new parts of the screen. This seems to be working very inconsistently. The result is that you have blank parts of the screen until you do something else which will trigger the update.

It is a lot easier to reproduce on touch devices, where you don't have a mouse cursor.
Comment 1 Samuel Mannehed cendio 2015-08-20 11:43:17 CEST 
Upstream bug: https://github.com/kanaka/noVNC/issues/517
Comment 2 Samuel Mannehed cendio 2017-01-10 16:52:42 CET 
Fixed in upstream by double buffering: https://github.com/novnc/noVNC/pull/699

We would no longer need frame buffer updates after panning.
Comment 4 Samuel Mannehed cendio 2017-02-03 16:02:40 CET 
Fixed now.
Comment 5 Henrik Andersson cendio 2017-02-06 14:58:08 CET 
Works as expected
Note You need to log in before you can comment on or make changes to this bug.