Bug 2021371 - keyboard ignores first character
Summary: keyboard ignores first character
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 35
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-09 02:19 UTC by Martin Ellison
Modified: 2023-08-09 02:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-13 15:49:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martin Ellison 2021-11-09 02:19:17 UTC
Description of problem: after a delay, keyboard ignores the first character that was typed


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


How reproducible: frequent (always?)


Steps to Reproduce:
1. wait a few minutes
2. try to type using the keyboard

Actual results: first character is missing


Expected results: input appears as typed


Additional info: only started with F35
Not sure which component is causing this, please reassign
Using xfce4

Comment 1 Kevin Fenzi 2021-11-09 22:20:32 UTC
Does this happen in every terminal / application? 

Does it happen on just vtys? ie, control-alt-f2 and login to the console, does it happen there?

How is your keyboard connected?

Comment 2 Martin Ellison 2021-11-11 07:42:08 UTC
It seems not to be application-specific. For example, Visual Studio Code, gedit, xfce4-terminal/bash.

control-alt-f2 (or the like) do not get me to a VT100. I think this is a separate issue.

My keyboard is connected by a USB cable.

I am using the kmod-nvidea screen drivers.

Comment 3 Ben Cotton 2022-11-29 17:16:35 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
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 EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Ben Cotton 2022-12-13 15:49:05 UTC
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 Martin Ellison 2023-08-09 02:51:24 UTC
I still have this problem under F38...


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