On 2020-08-12 13:57, Akbarkhon Variskhanov wrote:
> Restarting the GNOME Shell fixes the issue and the 'ru' layout gets
> added in /etc/default/keyboard configuration file: XKBLAYOUT=us,ru
If your system has one user only, and you add an XKB input source via Settings, /etc/default/keyboard is also updated instantly. It's per design; no need to restart anything.
> This may explain why rearranging the order of input sources
> magically fixes the bug: newly added input sources probably need to
> be put into defaults once to be recognized later.
Nope. When testing on 18.04, I added an additional user, so /etc/default/keyboard did not get updated. It behaved the same way. The input source settings for the user don't need to be synced with /etc/default/keyboard.
I saw that your upstream issue was closed. If you want to help solve the problem on 18.04, I would suggest that you look at upstream commits in gnome-shell and/or gnome-control-center which might be related. After all we know that the issue is not present in focal (GNOME 3.36).
On 2020-08-12 13:57, Akbarkhon Variskhanov wrote: keyboard configuration file: XKBLAYOUT=us,ru
> Restarting the GNOME Shell fixes the issue and the 'ru' layout gets
> added in /etc/default/
If your system has one user only, and you add an XKB input source via Settings, /etc/default/ keyboard is also updated instantly. It's per design; no need to restart anything.
> This may explain why rearranging the order of input sources
> magically fixes the bug: newly added input sources probably need to
> be put into defaults once to be recognized later.
Nope. When testing on 18.04, I added an additional user, so /etc/default/ keyboard did not get updated. It behaved the same way. The input source settings for the user don't need to be synced with /etc/default/ keyboard.
I saw that your upstream issue was closed. If you want to help solve the problem on 18.04, I would suggest that you look at upstream commits in gnome-shell and/or gnome-control- center which might be related. After all we know that the issue is not present in focal (GNOME 3.36).