Bug 433021 - Keyboard autorepeat rate too fast, missing keys
Keyboard autorepeat rate too fast, missing keys
Product: Fedora
Classification: Fedora
Component: gtk-vnc (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Daniel Berrange
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-15 13:39 EST by Gregorio Gervasio
Modified: 2008-11-26 12:37 EST (History)
2 users (show)

See Also:
Fixed In Version: F8
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-26 12:37:21 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gregorio Gervasio 2008-02-15 13:39:16 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:
All the time

Steps to Reproduce:
1. Connect to a VNC session:

vinagre localhost:1

2. Type in a terminal window.  Hold down the "A" key for about three seconds.

Actual results:

The key autorepeat rate becomes too fast to be usable (~100 chars/sec).  At this
point, it seems to get into a bad state.  Random keys get dropped.  For example,
typing "Ctrl-G" in xev shows that the "G" key never registers.  Removing focus
on vinagre and reentering seems to get out of the bad state, until the next
autorepeat is triggered.

Expected results:

Reasonable autorepeat rate, no missing keys.

Additional info:

This problem only showed up in this version.  gtk-vnc-0.3.2-1.fc8 does not
exhibit this problem.
Comment 1 Daniel Berrange 2008-04-03 10:47:49 EDT
This should be fixed in gtk-vnc-0.3.4-1.fc8 recently pushed to f8 updates-testing
Comment 2 Bug Zapper 2008-11-26 04:49:45 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 3 Jon Stanley 2008-11-26 12:37:21 EST
As this bug is in MODIFIED, Fedora believes that a fix has been committed that resolves the problem listed in this bug report.

If this is not the case, please re-open this report, noting the version of the package that you reproduced the bug against.

Thanks for the report!

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