Fedora Account System
Red Hat Associate
Red Hat Customer
On a HP Spectre x360 13-4163nf laptop, I got spurious KEY_WLAN events from the keyboard device, which makes gnome-settings-daemon behaves erratically. I'm reporting this as a libinput bug, but it is may be a kernel issue. Here is the output of sudo libinput-debug-events at resume from suspend: -event2 DEVICE_ADDED Power Button seat0 default group1 cap:k -event5 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event1 DEVICE_ADDED Power Button seat0 default group3 cap:k -event6 DEVICE_ADDED Logitech M325 seat0 default group4 cap:p left scroll-nat scroll-button -event11 DEVICE_ADDED HP Wide Vision FHD Camera seat0 default group5 cap:k -event7 DEVICE_ADDED ELAN Touchscreen Pen seat0 default group6 cap:T size 293.24/165.93mm -event8 DEVICE_ADDED ELAN Touchscreen seat0 default group6 cap:t size 302.40/168.00mm calib -event10 DEVICE_ADDED Intel Virtual Button driver seat0 default group7 cap:k -event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group8 cap:k -event4 DEVICE_ADDED SynPS/2 Synaptics TouchPad seat0 default group9 cap:pg size 140.53/61.82mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on -event9 DEVICE_ADDED HP Wireless hotkeys seat0 default group10 cap:k -event17 DEVICE_ADDED HP WMI hotkeys seat0 default group11 cap:k -event10 KEYBOARD_KEY +9.35s KEY_UNKNOWN (240) pressed event10 KEYBOARD_KEY +9.35s KEY_UNKNOWN (240) released -event3 KEYBOARD_KEY +9.37s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.38s KEY_WLAN (238) released event3 KEYBOARD_KEY +9.39s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.40s KEY_WLAN (238) released event3 KEYBOARD_KEY +9.41s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.42s KEY_WLAN (238) released event3 KEYBOARD_KEY +9.45s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.46s KEY_WLAN (238) released event3 KEYBOARD_KEY +9.47s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.48s KEY_WLAN (238) released event3 KEYBOARD_KEY +9.49s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +9.50s KEY_WLAN (238) released -event10 KEYBOARD_KEY +10.94s KEY_UNKNOWN (240) pressed event10 KEYBOARD_KEY +10.94s KEY_UNKNOWN (240) released -event3 KEYBOARD_KEY +10.97s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +10.97s KEY_WLAN (238) released event3 KEYBOARD_KEY +10.99s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +10.99s KEY_WLAN (238) released event3 KEYBOARD_KEY +11.01s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +11.01s KEY_WLAN (238) released event3 KEYBOARD_KEY +12.49s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +12.50s KEY_WLAN (238) released event3 KEYBOARD_KEY +12.52s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +12.52s KEY_WLAN (238) released event3 KEYBOARD_KEY +12.54s KEY_WLAN (238) pressed event3 KEYBOARD_KEY +12.54s KEY_WLAN (238) released While when I press the airplane key (it is a regular keyboard key and also f12 when fn is pressed), I got: -event9 KEYBOARD_KEY +21.32s KEY_RFKILL (247) pressed event9 KEYBOARD_KEY +21.32s KEY_RFKILL (247) released
Punting to the kernel. libinput doesn't look at the keys, it merely receves them and forwards them and we don't emulate key events anywhere. So if you get a KEY_WLAN, it's coming from the kernel (you can also verify this with evemu-record if you want to)
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
Still there with kernel 4.9.3-200.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.10.9-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
The bug is still there in the latest kernel 4.10.13-200.fc25.x86_64.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Still there on fedora 29. As a workaround, is there a way to disable a key with libinput ?
Re-closing since F29 reached EOL several years ago. If this is still an issue, please update the version. If you cannot update the version, needinfo me.