Description of problem: Image you: - use a US English international 105 keys keyboard - have different keyboard layouts with different button layouts (f.e. German and US English DVORAK) set You define a keyboard shortcut in one layout. The shortcut works in that layout. You switch to the other keyboard layout. You press the other buttons to get the same character. The shortcut does not work. The buttons of the first keyboard layout have to be pressed to make the shortcut work. Version-Release number of selected component (if applicable): I do not know which component is responsible for this behaviour. I tested with and can reproduce the problem with Fedora 22 & 24: SDDM and GDM with Xfce, GNOME, GNOME@Wayland. Other distributions on different hardware are affected too: Lubuntu 14.04: LightDM with LXDE (In Windows 7 and Mac OS X 10.10.5 this behaviour is not present.) Maybe this behaviour was present in X11 and carried over to Wayland? libwayland-server-1.10.0-1.fc24.x86_64 How reproducible: 100% Steps to Reproduce: 1. set multiple keyboard layouts in your session, like German and US English (DVORAK). German is the default keyboard layout. The L key is on different buttons on the keyboard for the defined layouts. In German layout to get an L you have to press L key. In US English (DVORAK) layout to get an L you have to press P key. 2. switch to German layout and define a keyboard shortcut, for example to open a terminal with Ctrl+L 3. press Ctrl+L. A terminal is opened. 4. switch to US English (DVORAK) keyboard layout and press Ctrl+P (to get the L) Actual results: nothing happens Expected results: a terminal should be started because I pressed the right key combination Additional info: If you press Ctrl+L a terminal is opened.
This bug is also present in fedora 25 with GNOME@Wayland. I use belgian and french-bépo layouts. After switching from belgian to bépo, I cannot use Super+L to lock the screen.
Although I have this issue with Gnome applications, Firefox and TeXmacs don't seem to be affected by this bug.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
still reproducable on Fedora 26 with libwayland-server-1.13.0-1.fc26.x86_64
I have this bug too. fr (AZERTY) to fr-bépo (BÉPO) or be (AZERTY) to fr-bépo (BÉPO). Applications with XWayland are not impacted (as mentioned before).
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.