https://bugs.kde.org/show_bug.cgi?id=453661
--- Comment #17 from Oded Arbel <o...@geek.co.il> --- (In reply to jiri.stefka from comment #16) > What I think is happening is that the shortcuts on X11 were based on > physical keys and on Wayland they're based on the symbols that depend on the > layout. > > It could make sense, now that I think of it, that `SUPER + 1` would not work > if that would be the case as the `+` symbol is somewhere else on US layout > than in CZ. Other do not exist on the US layout and it *may* fall back to > the physical key on some of those? Because most of the ones that are not > present on US layout work at least sometimes... According to what Andrey said (who I think is a developer that is in charge of at least some of that), that is more or less the case: on X11 it has the (incorrect) behavior of always parsing global shortcuts in the context of the "first" layout and as long as that is a US layout (which is rarely not the case), everything works. But its not the correct solution. On Wayland, there is no such assumption and Qt - that is responsible for understanding "what key was pressed" basically tries to translate keysyms that are not what you can expect from a US keyboard to the character that "a correct physical QWERTY key" would have generated. As far as I can tell, if the non-US keyboard layout emits keysyms that look like something a US keyboard can emit, then Qt (QXKBCommon) does no translation and you get an incorrect key value. > If I can do anything to help please tell me. I do not have enough knowledge > to figure out what data to collect myself. The Qt bug tracking system does not have any voting mechanism, but if you can go into the QTBUG I linked and register for watching it, that I believe will add to the visibility and put some more weight towards a Qt contributor fixing the problem. -- You are receiving this mail because: You are watching all bug changes.
