SUMMARY I have defined the Compose key to be the right menu key, which worked well on both X11 and Wayland before Plasma 5.21. Since the update, it keeps triggering the context menu on Wayland, regardless of what is configured in the system keyboard settings. STEPS TO REPRODUCE 0. login to a wayland session 1. start `kcmshell5 kcm_keyboard` 2. go to tab `Advanced` 3. configure `Position of Compose key` to be `Menu` OBSERVED RESULT The Menu key, which is set to be the Compose key, triggers the context menu EXPECTED RESULT It should not trigger the context menu, but the Compose input SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-66-generic Graphics Platform: Wayland ADDITIONAL INFORMATION Input Module is ibus, because otherwise accented keys don't work at all on Wayland (see https://bugs.kde.org/show_bug.cgi?id=411729#c4)
Any progess on this, guys? Can someone reproduce the described behaviour? I really rely on the compose key for typing French texts, but I would like to keep using Wayland for many reasons
To be more clear: compose key does not work
... with any key configured in the settings, not only the menu key
Can you attach your .config/kxkbrc file please?
For what it's worth, compose key works fine for me. However, I need to set QT_IM_MODULE=compose to make it work in Qt apps.
Isn't it a duplicate of bug 411729?
Created attachment 136402 [details] kxkbrc
I set QT_IM_MODULE=compose, but compose key still doesn't work (accented keys do, though)
it also doesn't work in gtk apps like chromium
compose worked well for me on wayland with ibus as input module before plasma 5.21, so this bug must somehow have been caused by the update
Does anyone have an idea what could be the cause of this, or what I could do to get rid of the problem? I even created a new user to test, and there is exactly the same problem: regardless of what key I configure in the settings, it will never trigger compose input. It doesn't work in XWayland clients, either.
It seems none of the Hardware > Input Devices > Keyboard > Advanced > Configure keyboard options work. I'm seeing the same issue with the compose key, and the "Make Caps Lock and additional Ctrl" doesn't take effect either. It doesn't seem to be a dupe of bug 411729. Running QT_IM_MODULE="" kwrite doesn't help at least.
(In reply to Manuel Geißer from comment #11) > Does anyone have an idea what could be the cause of this, or what I could do > to get rid of the problem? I see suspicious "VariantList=\\0" line in your kxkbrc, could you try to remove it? Is any options in the "Hardware > Input Devices > Keyboard > Advanced > Configure keyboard" work for you? IBus is not needed to check this, so maybe disable temporary.
(In reply to Andrey from comment #13) > (In reply to Manuel Geißer from comment #11) > > Does anyone have an idea what could be the cause of this, or what I could do > > to get rid of the problem? > > I see suspicious "VariantList=\\0" line in your kxkbrc, could you try to > remove it? That fixed it. Thanks!! :)
Removing this entry temporarily fixes the issue, but apparently there is something that periodically adds it again to the configuration...
this could be worked around with a login script, though
(In reply to Manuel Geißer from comment #15) > Removing this entry temporarily fixes the issue, but apparently there is > something that periodically adds it again to the configuration... Probably that's because the configuration rewrites on every start currently, I had a fix for that. For now, could you confirm the line appears on every restart? Also, please confirm every option in "Hardware > Input Devices > Keyboard > Advanced > Configure keyboard" stops working. Also, please check adding one more layout in keyboard configuration solves it. I'll update bug description meanwhile. Also, could you please attach your journal right after Plasma starts? And the last question, isn't it happening on X11 at all? Thanks.
(In reply to Andrey from comment #17) > Probably that's because the configuration rewrites on every start currently, > I had a fix for that. > For now, could you confirm the line appears on every restart? Interestingly, it does not. I just restarted and the configuration stayed intact. However, as soon as I tweak any advanced keyboard option, the invalid `VariantList` value appears agian, and can only be removed manually. > Also, please confirm every option in "Hardware > Input Devices > Keyboard > > Advanced > Configure keyboard" stops working. Yes everything does stop working. I initially didn't notice this as the only option relevant for me personally is Compose key... > Also, please check adding one more layout in keyboard configuration solves > it. I'll update bug description meanwhile. Yes it does - very good finding. > Also, could you please attach your journal right after Plasma starts? I don't know how to do that, sorry - could you explain please or point me at some documentation? Is it still relevant, provided that the invalid entry does not reappear on every reboot? > And the last question, isn't it happening on X11 at all? No, X11 seems to be completely unaffected. > Thanks. No problem, thanks for your effort to investigate the bug! >> Removing this entry temporarily fixes the issue, but apparently there is >> something that periodically adds it again to the configuration... I was wrong. This issue is not periodical - I probably only toggled one of the advanced keyboard settings in the meantime, which caused the invalid entry to reappear.
(In reply to Manuel Geißer from comment #10) > compose worked well for me on wayland with ibus as input module before > plasma 5.21, so this bug must somehow have been caused by the update By the way, sorry for wrongly accusing 5.21 for the issue, it was of course completely unrelated - I just deleted my second keyboard profile at the same time...
You might still guessed the version right - I introduced this bug recently ;)
Lol - that was really coincidence ;)
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/403
*** Bug 435002 has been marked as a duplicate of this bug. ***
*** Bug 433265 has been marked as a duplicate of this bug. ***
*** Bug 433266 has been marked as a duplicate of this bug. ***
Git commit 1c10a6f6612f09281f4fdcfdba6ba7c250f23f72 by Andrey Butirsky. Committed on 31/03/2021 at 19:52. Pushed by butirsky into branch 'master'. fix broken keyboard configurations with single layout on Wayland KConfigGroup::writeEntry() shouldn't be used with list - otherwise, "VariantList=\\0" is saved for the list with single empty item, as a measure to distinguish it from empty list. We don't need it here as the list is read directly by external library on load. M +1 -1 kcms/keyboard/keyboard_config.cpp https://invent.kde.org/plasma/plasma-desktop/commit/1c10a6f6612f09281f4fdcfdba6ba7c250f23f72
Git commit 5e89a55e26b004fc097fd3b544823e88003db066 by Nate Graham, on behalf of Andrey Butirsky. Committed on 31/03/2021 at 20:00. Pushed by ngraham into branch 'Plasma/5.21'. fix broken keyboard configurations with single layout on Wayland KConfigGroup::writeEntry() shouldn't be used with list - otherwise, "VariantList=\\0" is saved for the list with single empty item, as a measure to distinguish it from empty list. We don't need it here as the list is read directly by external library on load. (cherry picked from commit 1c10a6f6612f09281f4fdcfdba6ba7c250f23f72) M +1 -1 kcms/keyboard/keyboard_config.cpp https://invent.kde.org/plasma/plasma-desktop/commit/5e89a55e26b004fc097fd3b544823e88003db066
*** Bug 432438 has been marked as a duplicate of this bug. ***
Thanks for fixing this issue!
Here is why the config was overridden even if you don't touch it. Happens when you boot X11 session. Fixed: https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/433
*** Bug 433301 has been marked as a duplicate of this bug. ***