I have three keyboard layouts listed. Firefox and other x11 applications behave as they should using the correct layout which is set in gnome-shell (top right "system tray") and gnome-control-center. Gtk3/wayland applications use the secondary or tertiary layout. Affected applications: All Gtk+ 3.x applications with wayland backend Not affected: Firefox (Gtk+ 3.20 but with x11 backend), several Gtk+ 2.x applications, Qt4 applications; gnome-shell itself Version-Release number of selected component (if applicable): libinput-1.4.0-1.fc24 How reproducible: always for me on one machine, had no chance to test somewhere else yet. Steps to Reproduce: 1. have at least two (in my case: three) keyboard layouts configured in gnome-shell (top right "system tray") or gnome-control-center. 2. update to libinput 1.4.0 3. use desktop as you would normally Actual results: In Gtk+ applications with wayland backend, keyboard layout is set to secondary or tertiary layout. All other applications behave correctly Expected results: All applications should respect the configured keyboard layout Additional info: $ localectl System Locale: LANG=de_DE.UTF-8 VC Keymap: de-neo X11 Layout: de,de X11 Variant: neo,nodeadkeys X11 Options: grp:sclk_toggle
I don't know why this issue was present at first time, but I can't reproduce it any more after another reboot and upgrade. You might want to close this report as I can't reproduce it and have no clue how to hunt it down.
ok, thanks. I'll close it, please reopen when you can reproduce it. basically: libinput does not do layouts at all (handled at a higher level) and we didn't have any keyboard code change in the 1.4 release. so I don't think whatever it was was caused by libinput.