Bug 1402405

Summary: Improve key repeat under high latency network
Product: Red Hat Enterprise Linux 8 Reporter: David Blechter <dblechte>
Component: spice-gtkAssignee: Default Assignee for SPICE Bugs <rh-spice-bugs>
Status: CLOSED WONTFIX QA Contact: SPICE QE bug list <spice-qe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 8.0CC: cww, dblechte, fziglio, knoel, lpeer, marcandre.lureau, mkalinin, mtessun, rbalakri, srevivo, tpelka, victortoso
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1138211 Environment:
Last Closed: 2020-03-18 17:54:37 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Spice RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1138211    

Comment 1 Victor Toso 2017-03-27 13:12:58 UTC
Not enough time to work on this in 7.4 devel phase. Moving to 7.5

Comment 2 Victor Toso 2017-11-15 14:22:20 UTC
Moving to 7.6

Comment 3 Victor Toso 2018-07-10 14:43:24 UTC
Moving to 7.7

Comment 6 Victor Toso 2019-03-05 12:48:46 UTC
I don't understand why this is marked as RFE instead of a simple bug. We have code in place to deal with key repeat which is triggered over default 100 ms value. An user with high latency can try different values by using SPICE_KEYPRESS_DELAY environment variable at first, as workaround/helper and a proper solution relies on the client knowing the average latency of the connection to adjust this delay on the flow.

Comment 7 David Blechter 2019-03-05 13:15:32 UTC
(In reply to Victor Toso from comment #6)
> I don't understand why this is marked as RFE instead of a simple bug.

You are right, removed RFE

> We have code in place to deal with key repeat which is triggered over default
> 100 ms value. An user with high latency can try different values by using
> SPICE_KEYPRESS_DELAY environment variable at first, as workaround/helper and
> a proper solution relies on the client knowing the average latency of the
> connection to adjust this delay on the flow.

setting devel Cond NACK, as spice development primarily focus is on HW 3D acceleration and Wayland support

Comment 13 RHEL Program Management 2020-03-18 17:54:37 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.