From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 222161] New: platform/x86: lg-laptop: Double input of super key
Date: Tue, 20 Oct 2026 17:50:04 +0000 [thread overview]
Message-ID: <bug-222161-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=222161
Bug ID: 222161
Summary: platform/x86: lg-laptop: Double input of super key
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: helian.caumeil@clever.cloud
Regression: No
Created attachment 311202
--> https://bugzilla.kernel.org/attachment.cgi?id=311202&action=edit
the fix i applied
It seems that catching native ACPI events cause the super key
events to be handled 2 times:
- by the lg-laptop module
- by the keyboard driver
It result in having the input sended 2 times
when pressing super key.
I don't know the input system to tell if its this...
I have wrote/applied the following patch on my system (attached).
I don't know if this is good enough or the correct patch to do.
In advance, sorry for if my english is not fully understandable,
this is not my mother language.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2026-10-20 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 17:50 bugzilla-daemon [this message]
2026-10-20 19:24 ` [Bug 222161] platform/x86: lg-laptop: Double input of super key 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
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@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 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.