GNOME Bugzilla – Bug 763736
Disable input source from the current locale if user already configure one
Last modified: 2021-07-05 14:16:01 UTC
gnome-shell switches layouts with meta_backend_lock_layout_group(). The combined keymap is different from the single one. E.g. Behavior of Eisu_toggle is different between jp,jp and jp. If org.gnome.desktop.input-sources.sources is assigned, I think the keymap from the current locale is not needed. Also I'd avoid the conversion from 'default' to 'us' in IBusEngineDesc.layout.
This was originally reported in Fedora. https://bugzilla.redhat.com/show_bug.cgi?id=1249335 Recently a RHEL bug is relative with this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1311858
Created attachment 324080 [details] [review] Patch for keyboardManager.js This disables the combined layouts if users have input-sources.sources. However in my test, gdm login screen still have 'us'. Who updates org.gnome.desktop.input-sources.sources of gdm?
(In reply to Takao Fujiwara from comment #0) > gnome-shell switches layouts with meta_backend_lock_layout_group(). > The combined keymap is different from the single one. > E.g. Behavior of Eisu_toggle is different between jp,jp and jp. How is it different? > If org.gnome.desktop.input-sources.sources is assigned, I think the keymap > from the current locale is not needed. The keymap for the current locale is needed as explained in https://git.gnome.org/browse/gnome-shell/tree/js/misc/keyboardManager.js#n104
(In reply to Rui Matos from comment #3) > (In reply to Takao Fujiwara from comment #0) > > gnome-shell switches layouts with meta_backend_lock_layout_group(). > > The combined keymap is different from the single one. > > E.g. Behavior of Eisu_toggle is different between jp,jp and jp. > > How is it different? Eisu_toggle on 'jp,jp' toggles upper and lower characters but one on 'jp' does not. 'jp' toggles upper and lower with only Shift + Eisu_toggle. MS-IME on Windows toggles ASCII and Hiragana with Eisu_toggle but it does not change the cases. This bug confuses users who connect from MS-Windows to GNOME remotely especially Hiragana on ibus-kkc or ibus-anthy is enabled. > > > If org.gnome.desktop.input-sources.sources is assigned, I think the keymap > > from the current locale is not needed. > > The keymap for the current locale is needed as explained in > https://git.gnome.org/browse/gnome-shell/tree/js/misc/keyboardManager.js#n104 I'm not sure if I understand the comment. Alt+Ф is not required on jp keyboard by default and mnemonics keys works on jp keyboard.
(In reply to Takao Fujiwara from comment #4) > > How is it different? > > Eisu_toggle on 'jp,jp' toggles upper and lower characters but one on 'jp' > does not. > 'jp' toggles upper and lower with only Shift + Eisu_toggle. Ok, we need to find out why there's this difference in behavior. Because there really shouldn't be a difference here.
But 'jp,us' also causes a trouble because the Eisu_toggle toggles upper and lower likes CapsLock. Currently the layout of kkc is fallen back to 'us' as my patch fixed it.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.