To reproduce:
1) gsettings set org.gnome.libgnomekbd.keyboard layouts "['it','it\tnodeadkeys','it\tus']"
2) startx # assuming this launches GNOME Shell or Unity, haven't tested other environments)
Notice that your layout ends up being "it\tus" instead of "it". If you instead set your layouts to ['it','it\tnodeadkeys','it\tmac'], you DO NOT get the bug. That is, libxklavier is matching against the 'us' part of 'it\tus' for some reason.
Originally reported in Ubuntu: https:/ /bugs.launchpad .net/bugs/ 960096 using libxklavier 5.2.1
We had a problem where after autologin, the wrong keyboard layout group would get selected instead of the default.
Seems to be caused by http:// cgit.freedeskto p.org/libxklavi er/commit/ ?id=18e75ba865e 5f23b5e0b6926cc 20ee82b0782084
To reproduce: libgnomekbd. keyboard layouts "['it', 'it\tnodeadkeys ','it\tus' ]"
1) gsettings set org.gnome.
2) startx # assuming this launches GNOME Shell or Unity, haven't tested other environments)
Notice that your layout ends up being "it\tus" instead of "it". If you instead set your layouts to ['it',' it\tnodeadkeys' ,'it\tmac' ], you DO NOT get the bug. That is, libxklavier is matching against the 'us' part of 'it\tus' for some reason.