Bug 383056 - super key opens launcher menu, even when remapped to ctrl
Summary: super key opens launcher menu, even when remapped to ctrl
Status: RESOLVED DUPLICATE of bug 381447
Alias: None
Product: kwin
Classification: Plasma
Component: input (show other bugs)
Version: 5.10.4
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-02 17:08 UTC by Ural
Modified: 2017-08-15 14:28 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ural 2017-08-02 17:08:05 UTC
Hello. 
I use gentoo and often update plasma to latest version. While I was on Plasma 5.8-5.9, I didn't had this bug.

I have remapped super (win) key to ctrl key in systemsettings. After long-time usage of macos, it is more comfortable to me to click super key which is closer. 

After some update, if I press super key and don't press another, it opens a launcher menu. I don't want this and didn't found where to disable it. I want my super key to be the same as ctrl key and nothing more.

How to disable opening launcher menu?

P.S. it is not duplicate of https://bugs.kde.org/show_bug.cgi?id=367730 
The problem appeared again after some plasma update
Comment 1 Dmitry 2017-08-15 09:34:04 UTC
I have the same problem. It's extremely annoying to stop using key bindings you get used to, just because developers don't pay attention to users, when adding new feature, that is non-configurable and undisableable.
I don't want to use <Win> key to open launcher, it is already Alt+F1 for that and everybody get used to it.

Plasma version: 5.10.4
OS: Gentoo Linux.
Comment 2 Kai Uwe Broulik 2017-08-15 10:11:23 UTC
There was a duplicate bug report about how modifier-only shortcuts don't respect custom key mappings but I can't find it right now.
Comment 3 Martin Flöser 2017-08-15 14:28:12 UTC
@Kai-Uwe: browse bugs -> kwin -> component input

That's how I just found it.

*** This bug has been marked as a duplicate of bug 381447 ***