Description of problem: Under Wayland session not working user defined switching Keyboard layout In my case not work "Ctrl + Shift" combination. Work only default "Super + Space".
Sorry I cannot reproduce using an up-to-date F21. Ctrl + Shift are both modifiers, that won't work alone, you need one regular key to activate the shortcut. In my case, I tried with Ctrl + Shift + Space and that worked un GNOME Wayland session. Could you clarify what exactly uoi are trying to achieve and how to reproduce the issue?
Try explain: Layout indicator work as expected and trigger when I pressed 'Ctrl + Shift' combination, but not all application know that layout is changed. For example I am type this message in Google Chrome at 'en' layout. If I pressed 'Ctrl + Shift' now I am would expected that my layout is 'ru', but I am stay on 'en' layout (Google Chrome still type English letters) although indicator show me that my current layout is 'ru'. With 'Super + Space' combination I don't experience this problem. P.S. Another observation if I switch combination using 'Ctrl + Shift' and then switch to another application and then immediately go back to find out what the layout switched.
Created attachment 990361 [details] Input Source Options
Same issue have gnome-terminal
OK, I understand, it's the "modifiers-alone switch to next source" option. I am able to reproduce, but I reckon it's a tad more complicated: - The modifier-only switch does change the input source as seen in the notification - The modifier-only switch works as expected using the Wayland backend (e.g. try with "GDK_BACKEND=wayland gedit", it works) - The modifier-only backend does not change the input source when using the x11 backend (try the same with "GDK_BACKEND=x11 gedit", it won't work) - But setting focus back and forth does set the correct input source So I doubt the issue is with "wayland" itself, could be either in gnome-shell or in Xwayland instead.
Problem still not fixed in Fedora 22
I have 100% reproducible conditions and I can give you TeamViewer session or screencast?
Problem reproduces 100% on Fedora 22 with gnome-shell-3.16.0-1.fc22.
This bug isn't even fedora-specific. Confirm having the same issue on Gentoo.
https://bugs.debian.org/766575 Debian users report the same.
Fedora 23 still unfixed. propose include this issue in alpha blockers
> - But setting focus back and forth does set the correct input source It points to Xwayland http://cgit.freedesktop.org/xorg/xserver/tree/hw/xwayland/xwayland-input.c#n410 modifier event carries the group index (layout) and it may happen that it is not updated as it should https://bugzilla.gnome.org/show_bug.cgi?id=752165 http://lists.x.org/archives/xorg-devel/2015-July/047066.html However, if that occurs only with user-defined shortcuts, there may be another bug in gnome-shell or mutter
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.