[Touch-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1909347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap
I have Ubuntu MATE on a VM and could reproduce your first issue there, i.e. it's present only when Neo 2 is not first in the list of keyboard layouts. Consequently this is probably an xkeyboard-config issue and not specific to gnome-control-center. And the issue is reasonably upstream in nature. I found this open upstream issue regarding Neo 2: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard- config/-/issues/14 Can't tell if it's related to your observations. If not I would recommend you to file a new issue upstream. If you do, please post a link to it here for tracking purposes. ** Bug watch added: gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues #14 https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/14 ** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config (Ubuntu) ** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided => Low ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1909347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap
** Also affects: gnome-control-center Importance: Undecided Status: New ** No longer affects: xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in gnome-control-center: New Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1909347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp