Bug 1402405 - Improve key repeat under high latency network
Summary: Improve key repeat under high latency network
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: spice-gtk
Version: 8.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks: 1138211
TreeView+ depends on / blocked
 
Reported: 2016-12-07 13:25 UTC by David Blechter
Modified: 2021-06-10 11:45 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1138211
Environment:
Last Closed: 2020-03-18 17:54:37 UTC
Type: Feature Request
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 261543 0 Troubleshoot None When typing in the spice session keys are stuck 2019-03-27 21:12:09 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.