From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218093] Keyboard will not register any input after using certain FN-Combos
Date: Fri, 03 Nov 2023 14:00:56 +0000 [thread overview]
Message-ID: <bug-218093-208809-nIL9IRvYix@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218093-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218093
Bagas Sanjaya (bagasdotme@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bagasdotme@gmail.com
--- Comment #1 from Bagas Sanjaya (bagasdotme@gmail.com) ---
(In reply to Totallyreal Name from comment #0)
> MSI B550 A-Pro Motherboard
> Sharkoon SGK3 Keyboard
>
> I pretty much tried all Kernels. The Issue is always the same:
>
> When pressing a FN-Combo for the Keyboard-LEDs in my Case FN+=. The keyboard
> might not be able to send any more input. "Normal" Combos like using the FN
> key to increase or decrease the Volume like FN+F2/F3 will not cause this
> issue.
> When checking with tools like evtest i noticed that sometimes no release
> command of the keyboard is received and it spams the Terminal while no more
> other input is recognized. Connecting the Keyboard to a USB3 Port (instead
> of the USB "Keyboard Port") the keyboard stays responsive though you'll
> still see the "terminal spam" caused by no release event.
>
Where is the output? And what device do you have this issue with?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2023-11-03 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 18:07 [Bug 218093] New: Keyboard will not register any input after using certain FN-Combos bugzilla-daemon
2023-11-03 14:00 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-218093-208809-nIL9IRvYix@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.