You are not logged in.
After every fresh boot, my first keystroke on the search bar of application launcher is always duplicated. This always happens for exactly the first keystroke and never again until the system shuts down.
Anyone else having this minor annoyance?
Offline
Can't say I have. is there more data to this? Is this a wireless keyboard and it might just be a buffer from a power save wakeup? Is it JUST in the search bar or does that just happen to be the first thing you usually invoke? Does waiting a bit longer work? Do you not see the dupe event in
sudo libinput debug-eventsOffline
Is this a wireless keyboard and it might just be a buffer from a power save wakeup?
No, it is not a wireless keyboard, I also tested the keyboard on a laptop that I happen to have with Manjaro + KDE installed and I couldn't replicate this behavior.
I also did multiple tests to answer your other questions.
Is it JUST in the search bar or does that just happen to be the first thing you usually invoke?
It seems to be just that search bar. If the search bar of the application launcher is invoked before any other KDE search bars are used, then the behavior is consistent and the duplicated keystroke on the first key will always appear. However, if I invoke other search bars first (ex. Krunner's search bar or System Setting's search bar) and then I invoke the application launcher's search bar, the behavior is inconsistent. On the Krunner test (startup then Krunner and then application launcher), no duplicated keystroke appeared in any of the search bars. On the System Setting's test (startup then System Settings and then application launcher), no duplicated keystroke appeared in the System Setting's search bar, but it did appear on the application launcher's search bar. Those tests were also performed in my laptop with that specific keyboard and no duplicated keystroke appeared anywhere.
Does waiting a bit longer work?
No, even if I wait a couple of minutes, if the application launcher's search bar is the first KDE search bar to be invoked after the system startup, then the behavior is consistent.
Also, the duplicated event does not appear in libinput. After a system startup I opened a console and left libinput running, then I opened the application launcher's search bar, then I pressed a button and it did appear twice. This was the output of libinput:
-event1 DEVICE_ADDED Power Button seat0 default group1 cap:k
-event0 DEVICE_ADDED Power Button seat0 default group2 cap:k
-event2 DEVICE_ADDED 2.4G Mouse seat0 default group3 cap:k
-event5 DEVICE_ADDED 2.4G Mouse seat0 default group3 cap:p left scroll-nat scroll-button
-event6 DEVICE_ADDED 2.4G Mouse Consumer Control seat0 default group3 cap:kp scroll-nat
-event8 DEVICE_ADDED 2.4G Mouse System Control seat0 default group3 cap:k
-event3 DEVICE_ADDED SEMICO USB Keyboard seat0 default group4 cap:k
-event9 DEVICE_ADDED SEMICO USB Keyboard System Control seat0 default group4 cap:k
-event7 DEVICE_ADDED SEMICO USB Keyboard Consumer Control seat0 default group4 cap:kp scroll-nat
-event11 DEVICE_ADDED Eee PC WMI hotkeys seat0 default group5 cap:k
-event3 KEYBOARD_KEY +0.000s KEY_LEFTMETA (125) pressed
event3 KEYBOARD_KEY +0.048s KEY_LEFTMETA (125) released
event3 KEYBOARD_KEY +3.000s *** (-1) pressed
event3 KEYBOARD_KEY +3.024s *** (-1) releasedOffline