I have long ago set Right Win as the compose key in systemsettings Hardware/Input Devices/Keyboard/Advanced/Position of Compose key. This stopped working since 5.10.0. The Right Win key now activates App Dashboard. I have verified that: * the compose key setting is still being remembered (it was not reset by the upgrade) * Right Win is not specifically set as the shortcut for App Dashboard Please fix this.
Renaming and CC'ing relevant people.
(In reply to Eike Hein from comment #1) > Renaming and CC'ing relevant people. Thank you! My product and component choice for this bug report was a wild guess, could you check that too?
Same issue here (5.10.1 under Wayland). I had an issue with a random shortcut stealing the Compose key. I managed to find it in shortcut management and remove it (even though it did not have the Compose key listed) and, at the time, Compose worked again. Now, after a reboot, some other shortcut has stolen Compose. I'm not entirely sure what it is - it seems to maximize/minimize a particular window (window shortcut?). This is independent of which key I choose for the Compose key. I use Caps Lock. If I move it to Menu then the Menu key triggers the shortcut instead.
Please see https://www.reddit.com/r/kde/comments/55udc1/how_do_i_stop_the_meta_key_from_opening_the/ for a workaround.
That workaround doesn't work for me; not sure if this is because my problem is different from the reporter's or not. My issue isn't KWin stealing the Meta key, it's something stealing the Compose key (regardless of where it is mapped). I map it to Caps Lock, not Meta. The action triggered is not the launcher, it's something else (looks like a random hotkey action to me, but I'm not sure; right now it's triggering some kind of window show/hide that only happens after I've opened enough windows). The workaround correctly disables the Meta/Win key triggering the launcher, but does nothing to fix the Compose key being stolen by something else.
@Hector: your problem is completely unrelated to the problem reported here.
*** Bug 369861 has been marked as a duplicate of this bug. ***
I also have the Compose key set to Right Win and for me it just does nothing at all in KDE applications, but works fine in Firefox. When trying to enter u-umlaut in KDE applications as <Right Win> + <"> <u>, KMail or KWrite just write "u (or "u" in KWrite, because of automatic quotes). I get ü for the same key sequence in Firefox.
(In reply to Dennis Schridde from comment #8) > I also have the Compose key set to Right Win and for me it just does nothing > at all in KDE applications, but works fine in Firefox. When trying to enter > u-umlaut in KDE applications as <Right Win> + <"> <u>, KMail or KWrite just > write "u (or "u" in KWrite, because of automatic quotes). I get ü for the > same key sequence in Firefox. Operating System: Gentoo Linux KDE Plasma Version: 5.22.1 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Kernel Version: 5.12.14 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics Memory: 13,5 GiB of RAM Graphics Processor: AMD Radeon™ Vega 11 Graphics
(In reply to Dennis Schridde from comment #8) > I also have the Compose key set to Right Win and for me it just does nothing > at all in KDE applications, but works fine in Firefox. When trying to enter > u-umlaut in KDE applications as <Right Win> + <"> <u>, KMail or KWrite just > write "u (or "u" in KWrite, because of automatic quotes). I get ü for the > same key sequence in Firefox. Mapping Compose to "Menu" or "Right Alt" has no effect: The behaviour is the same.
(In reply to Dennis Schridde from comment #8) > I also have the Compose key set to Right Win and for me it just does nothing > at all in KDE applications, but works fine in Firefox. When trying to enter > u-umlaut in KDE applications as <Right Win> + <"> <u>, KMail or KWrite just > write "u (or "u" in KWrite, because of automatic quotes). I get ü for the > same key sequence in Firefox. For me the issue is gone since yesterday. I recently updated a lot of packages, including those bringing patches of my distribution to Qt and Plasma, but cannot pinpoint the fix to any specific update, due to the amount of changes. From a very brief look at the changes Gentoo applied, this one comes closest to having something to do with text input: https://bugreports.qt.io/browse/QTBUG-94215
It would not surprise me that this turned out to be a Qt bug, as there should not be anything in Plasma that would affect this.