2

I'm using gnome-tweaks-tool to set an alternative hotkey for changing keyboard layout (Ctrl+Shift). It works - layout changes, but keyboard indicator on top toolbar doesn't change after pressing hotkey. If I use standart combination Super+Space layout and indicator on toolbar work good.

Can I fix this issue?

2 Answers2

8

After discussing the issue on the Ubuntu Launchpad it seems that it related to the Wayland session. Under Xorg, everything works fine.

To switch from Wayland to Xorg (from https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop):

sudo vim /etc/gdm3/custom.conf

Uncomment the line:

#WaylandEnable=false

Restart GDM3 display manager:

sudo systemctl restart gdm3
Zzaponka
  • 181
4

run this in terminal:

gsettings set org.gnome.desktop.wm.keybindings switch-input-source-backward "['<Control>Shift_L']"

got this answer from here - below the marked as right answer.

Sagi314
  • 71
  • I think that this solution doesn't resolve the issue itself: the keyboard indicator doesn't change, when you change the keyboard layout. I'm looking for the way to deal with this issue too: it was broken after upgrade from Ubuntu 21.10 to 22.04 LTS. – Zzaponka May 08 '22 at 14:50
  • I was looking for a solution because I had this issue too (on fresh 22.04 installation). I Tried some things but that's the answer that solved the problem in my case. maybe it will help others too. @Zzaponka – Sagi314 May 08 '22 at 19:03
  • I mean that in my opinion the solution you are referring to is about the way to assign different keys combination to switch between input layouts, but the current one is about issue with keyboard layout indicator itself that doesn't reflect the current layout. – Zzaponka May 09 '22 at 19:13
  • Yes, I know, my issue was the same. I changed the key binding using Gnome-Tweaks and it indeed changed, but the indicator stayed the same. This line made it change the indicator too. – Sagi314 May 09 '22 at 20:28
  • This actually solved my problem. Indicator started working. – kkazakov Jul 09 '22 at 12:10
  • I had the same problem and was reluctant to switch to X11, this solution fixed it. I think this should be the accepted answer – Yar Aug 11 '23 at 08:33