Bug 403702

Summary:	Triggering "radio switch" with Fn+Home causes Meta-Key not to trigger Application Launcher
Product:	[Plasma] kwin	Reporter:	Matt <matteo>
Component:	input	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	CONFIRMED ---
Severity:	minor	CC:	matteo, nate
Priority:	NOR	Flags:	mgraesslin: X11+
Version First Reported In:	5.14.5
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Matt 2019-01-28 18:03:07 UTC

SUMMARY
On my Dell XPS 9370, the radio kill button is paired with the home button, right next to my F12 key. 90% of the time, when I use that key (Fn+Home), it kills my Meta key until I relog.

STEPS TO REPRODUCE
1. Hold Fn key
2. Tap Home key

OBSERVED RESULT
Meta key fails to trigger application launcher. Alt+F1 still works, and other Meta assignments work too.


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Comment 1 Matt 2019-01-28 20:26:22 UTC

(In reply to Matt from comment #0)
> SUMMARY
> On my Dell XPS 9370, the radio kill button is paired with the home button,
> right next to my F12 key. 90% of the time, when I use that key (Fn+Home), it
> kills my Meta key until I relog.
> 
> STEPS TO REPRODUCE
> 1. Hold Fn key
> 2. Tap Home key
> 
> OBSERVED RESULT
> Meta key fails to trigger application launcher. Alt+F1 still works, and
> other Meta assignments work too.
> 
> 
> EXPECTED RESULT
> Application launcher opens
> 
> SOFTWARE/OS VERSIONS
> Linux/KDE Plasma: Arch Linux 4.20.0-arch1-1-ARCH
> (available in About System)
> KDE Plasma Version: 5.14.5
> KDE Frameworks Version: 5.53.0
> Qt Version: 5.12.0
> 
> ADDITIONAL INFORMATION

Comment 2 Martin Flöser 2019-01-29 05:13:00 UTC

X11 or Wayland

Comment 3 Matt 2019-01-30 02:37:08 UTC

(In reply to Martin Flöser from comment #2)
> X11 or Wayland

X11

Comment 4 Martin Flöser 2019-01-30 05:25:11 UTC

Please provide the output of xev containing meta press and radio button switch.

Comment 5 Matt 2019-01-30 22:42:44 UTC

META KEYPRESS WHEN META KEY IS WORKING:

KeyPress event, serial 40, synthetic NO, window 0x4200001,
    root 0x168, subw 0x0, time 3689931, (166,-19), root:(1199,10),
    state 0x0, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x4200001,
    root 0x168, subw 0x0, time 3690089, (166,-19), root:(1199,10),
    state 0x40, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False



RADIO KEYPRESS

KeyPress event, serial 40, synthetic NO, window 0x200001,
    root 0x168, subw 0x0, time 3850405, (164,-12), root:(1197,17),
    state 0x0, keycode 255 (keysym 0x1008ffb5, XF86RFKill), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 40, synthetic NO, window 0x200001,
    root 0x168, subw 0x0, time 3850405, (164,-12), root:(1197,17),
    state 0x0, keycode 255 (keysym 0x1008ffb5, XF86RFKill), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

META KEYPRESS AFTER RADIO SWITCH

KeyPress event, serial 40, synthetic NO, window 0x4200001, 
   root 0x168, subw 0x0, time 77107, (167,-21), root:(1200,8), 
   state 0x0, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES, 
   XLookupString gives 0 bytes:  
   XmbLookupString gives 0 bytes:  
   XFilterEvent returns: False 

KeyRelease event, serial 40, synthetic NO, window 0x4200001, 
   root 0x168, subw 0x0, time 78026, (167,-21), root:(1200,8), 
   state 0x40, keycode 133 (keysym 0xffe7, Meta_L), same_screen YES, 
   XLookupString gives 0 bytes:  
   XFilterEvent returns: False

NOTE: As I was running xev, there was one instance where the Meta Key did not fail as described. However, after a restart, it returned to the previously stated semi-functionality

Comment 6 Matt 2019-01-30 22:46:45 UTC

Again, noticing some interesting aspects to this that were I had failed to notice earlier. Locking the session and re-entering, or simply closing the lid and re-opening it  will return the meta key to its intended function.

Comment 7 Vlad Zahorodnii 2023-05-11 08:15:57 UTC

Can reproduce it. It also happens on Wayland for some reason.

Comment 8 Matt 2023-05-11 11:28:58 UTC

Yes, this bug has been persistent. I made the switch to Wayland somewhere around plasma 20, and noticed it then too. Will check today and update the ticket if it’s on latest version.