From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222161] platform/x86: lg-laptop: Double input of super key
Date: Wed, 18 Nov 2026 20:04:02 +0000 [thread overview]
Message-ID: <bug-222161-215701-PLp5i9BHCq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-222161-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=222161
jvallep@gmail.com (jvallep@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvallep@gmail.com
--- Comment #19 from jvallep@gmail.com (jvallep@gmail.com) ---
I can confirm this issue on an LG Gram 16Z90TL-G.AU88B running Fedora 45.
Test results:
Kernel 7.2.15-300.fc45: the integrated keyboard Super key works correctly.
Kernel 7.3.3-300.fc45: the Super key does not work.
Kernel 7.3.4-300.fc45: the issue is still present with the original lg_laptop
module.
I applied Armin Wolf's modified patch, adding the two KE_IGNORE entries for WMI
events 0x30020000 and 0x30020001, mapped to KEY_LEFTMETA.
The patched lg_laptop module compiled successfully against
kernel-devel-7.3.4-300.fc45 and fixed the issue.
I installed the patched module under
/lib/modules/7.3.4-300.fc45.x86_64/updates/ and confirmed that the Super key
works correctly, including after reboot.
Hardware: LG Electronics 16Z90TL-G.AU88B.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-11-18 20:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:50 [Bug 222161] New: platform/x86: lg-laptop: Double input of super key bugzilla-daemon
2026-10-20 19:24 ` [Bug 222161] " bugzilla-daemon
2026-10-20 21:07 ` bugzilla-daemon
2026-10-20 21:12 ` bugzilla-daemon
2026-10-20 22:31 ` bugzilla-daemon
2026-10-20 23:49 ` bugzilla-daemon
2026-10-20 23:51 ` bugzilla-daemon
2026-10-20 23:54 ` bugzilla-daemon
2026-10-21 8:11 ` bugzilla-daemon
2026-10-25 13:09 ` bugzilla-daemon
2026-10-26 6:59 ` bugzilla-daemon
2026-11-01 17:10 ` bugzilla-daemon
2026-11-01 20:33 ` bugzilla-daemon
2026-11-01 22:09 ` bugzilla-daemon
2026-11-02 10:21 ` bugzilla-daemon
2026-11-03 14:56 ` bugzilla-daemon
2026-11-03 14:58 ` bugzilla-daemon
2026-11-03 15:45 ` bugzilla-daemon
2026-11-03 18:08 ` bugzilla-daemon
2026-11-10 15:25 ` bugzilla-daemon
2026-11-18 20:04 ` bugzilla-daemon [this message]
2026-11-19 20:22 ` 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-222161-215701-PLp5i9BHCq@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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