Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Not enough time to work on this in 7.4 devel phase. Moving to 7.5

Moving to 7.6

Moving to 7.7

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.

(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

Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.