Hi Robie,
I think we are talking about Jammy as comment#11.
and yes, as I mentioned in "Where problems could occur":
>also each DM still need to deal with multi-rfkill events because upstream
>changes[2].
From what I learned from HP, there are some old platforms have both
Intel-HID and HPQ6001 components but I don't have the one in my side.
I have
1. HPQ6001 HP laptop
2. Intel-HID HP laptop
I shared what I can imaged when problems will occur, some check points and
workaround in the bug description.
Hope it can cover what you concerning.
** Description changed:
[Impact]
The airplane hokey doesn't work on HP new generation machines.
[Test Plan]
Press airplane hokey.
Before the patch, nothing happens.
After the patch, the rfkill works as expected.
+
+ In some old HP platforms (contains Intel-HID and HPQ6001 in same
+ machine), the user will aware the airplane mode toggled very quickly
+ e.g. turn-on and turn-off immediately (or works good without problem,
+ depends on how DM handles multiple rfkill events).
+
+ In this case, you could check:
+ 1. sudo evtest
+ # You probably could see
+ # ...
+ # /dev/input/event8: Intel HID events
+ # ...
+ # /dev/input/event11: Wireless hotkeys
+ # or "HP Wireless hotkeys" depends on your kernel version
+
+ 2. try to listen these events when pressing airplane key, you will
+ probably see these two events will send the keycode out.
+
+ 3. check the components own this event
+ $ sudo udevadm info -a /dev/input/event11
+ # ...
+ # ATTRS{phys}=="hpq6001/input0"
+
+ $ sudo udevadm info -a /dev/input/event8
+ # ...
+ # DRIVERS=="intel-hid"
+
+ 4. check your hwdb is affect.
+ $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
+ # If you didn't see anything then it means your intel-hid is unmask.
+
+ 5. You could report a bug to your DM for dealing with two rfkill events (same
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as
workaround (but it will be overwritten in next upgrade) by adding:
+ ```
+ evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
+ ```
+ to /lib/udev/hwdb.d/60-keyboard.hwdb
+
+ then
+ $ systemd-hwdb update
+ $ udevadm trigger
[Where problems could occur]
In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will
not work but HP confirmed the new HP generation won't contain the HPQ6001 and
also each DM still need to deal with multi-rfkill events because upstream
changes[2].
---
In the last year, HP mentions HP machines need to use hp-wireless
(HPQ6001) as the rfkill source[1].
However, HP confirms the HPQ6001 has been retired in the platforms since
2022.
In the platforms after 2022, there are two sources of rkfill events
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
Therefore, the upstream already accept the patch[2] to unmask intel-hid and
mention this big change in the NEWS.
This change makes the pre-2022 HP platforms meet the regression since they
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing
function key.
Thus, there is a patch[3] to make sure the GNOME could deal with this case
smoothly.
However, the systemd change will still cause other DEs meet the regression
(xfce, KDE, lxde, etc..).
Backport systemd change to make HP 2022 platforms work is not the best choice
on stable version (focal in this case).
We still need a solution to make airplane key works on 2022 HP platforms
(intel-hid and atkbd only).
The potential solution from my mind that is to maintain a whitelist to unmask
intel-hid in ubuntu-patch in focal, something like:
```
evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
KEYBOARD_KEY_8=wlan # Use hp-wireless instead
```
after "KEYBOARD_KEY_8=unkown".
[1] https://bugs.launchpad.net/bugs/1883846
[2] https://github.com/systemd/systemd/pull/20219
[3]
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955997
Title:
The airplane hotkey has no function on a HP platform
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
