Bug 2230222 - keyboard ignores first character
Summary: keyboard ignores first character
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libinput
Version: 38
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 03:01 UTC by Martin Ellison
Modified: 2024-05-28 13:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-05-28 13:47:14 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Ellison 2023-08-09 03:01:47 UTC
after a delay, keyboard ignores the first character that was typed


Reproducible: 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

previously raised as bug 2021371 under F35 and closed under end of life. Problem persists.
No idea which component is causing this.

Maybe something is going to sleep?

Comment 1 Peter Hutterer 2023-08-10 00:17:43 UTC
Please run `sudo libinput record` (in libinput-utils.rpm) and then try to reproduce the issue. That tool will print *kernel* events as received by userspace so it'll help you narrow down if the issue is in the kernel or in userspace somewhere. If you type and the event does not show up, then it's happening in the kernel.

Comment 2 Aoife Moloney 2024-05-28 13:47:14 UTC
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 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.


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