public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218093] New: Keyboard will not register any input after using certain FN-Combos
Date: Tue, 31 Oct 2023 18:07:29 +0000	[thread overview]
Message-ID: <bug-218093-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=218093

            Bug ID: 218093
           Summary: Keyboard will not register any input after using
                    certain FN-Combos
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: kotversuchung@gmail.com
        Regression: No

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.

I tried blacklisting certain combos so that i wouldn't accidently hit that key
though it just doesn't help. To be honest it seems to me that Linux
recognizes/receives that it shouldn't. Because even if the Input "freezes" i'm
still able to change the LED-Behaviour of the Keyboard.. 
On Windows this issue doesn't exist. So i'm pretty certain that it is related
to Linux in some way. I also tried an Uefi-Update yet the Issue persisted.
I'm by no means a "Linux Pro" and actually have no clue what else i could try.
So i just wanted to report that here in case someone else is having this issue.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2023-10-31 18:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 18:07 bugzilla-daemon [this message]
2023-11-03 14:00 ` [Bug 218093] Keyboard will not register any input after using certain FN-Combos bugzilla-daemon

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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox