Discussed during the 2016-10-31 blocker review meeting: [1]

The decision to classify this bug as an AcceptedFreezeException was made as this is an installer issue and therefore cannot be fixed with an update.

[1] https://meetbot.fedoraproject.org/fedora-blocker-review/2016-10-31/f25-blocker-review.2016-10-31-16.01.txt

I've assigned a custom key combination in GNOME wayland and it works fine.

F25 GNOME,
Using Gnome.org in lieu of Wayland, the keyboard switching works for me, but, it does not result in a change to the Gnome keyboard layout INDICATOR (top panel right side).
My choice for layout change was simultaneous control key operation.

Same OR SIMILAR results as Dwaxeiption.

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

"I've assigned a custom key combination in GNOME wayland and it works fine."

This is about using the switcher combo that anaconda configures. If you select some locales, anaconda will automatically select two keyboard layouts, and try to configure a specific key combination (usually alt+shift) to switch between them. There is also an option in the anaconda KEYBOARD screen to configure one of several different switcher key combinations.

None of this actually works under Wayland; any combo anaconda thinks it's configured as a layout switcher combo does not in fact switch the layouts. But anaconda's UI still tells you it's configured a switcher combo and that you can use it to switch layouts.

Still the same issue with F28 Beta.

I switched the keyboardlayout using the gnome-settings dialog.

anaconda stil showed the us layout.

after clicking on it it changed to null

a second click crashed anaconda.

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.

*** Bug 1628859 has been marked as a duplicate of this bug. ***

per the dupe, this is still valid as of F29.

Just wanted to share. I have got to test Fedora Silverblue 29 RC1.5 image and found almost all "alt+<key>" combinations working for me. They can switch the keyboard. But some are not working like "Caps Lock" "Right Alt" "Shift+Caps Lock". I have not checked all the combinations.

This bug is basically about Workstation live images. Installer images like the Silverblue installer image are not affected *during the install* because the installer environment uses X, not Wayland. Post-install, though, Workstation will not respect any switcher combo configured by anaconda for X.

Adam, Thanks for that information.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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.

The same occurs on F31 Workstation Live.

Description of the problem:

Live is running under mutter which is "taking control" of keyboard switching. So our current solution with libxklavier won't work. We have to rewrite (implement new) keyboard control which is using DBus gnome shell service. This is a bit unfortunate and not that trivial task to do. Currently we are trying to find a better way to do this.

*** Bug 1817229 has been marked as a duplicate of this bug. ***

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Assigned to mail list is nonsense, returning to new.