Basically gnome-shell is overriding ubiquity's changes when ubuntu-drivers installs silently oem drivers on VMware products env ( or Virtualbox with default/recommended VMSVGA controller), namely open-vm-tools package.
udevadm trigger is executed and as a result Xorg and gnome-shell re-read their config including keyboard layouts. gnome-shell overrides changes made by Xorg which uses /etc/default/keyboard ( written/updated by ubiaquity) settings.
It doesn't seem possible to stop gnome-shell updating xkb layouts.
A possible solution would be to make sure the gnome-session behind ubiquity also uses the same keyboard layout ( which makes sense during a direct ubuntu install).
Something like that :
gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'fr')]"
Looked at it further.
Basically gnome-shell is overriding ubiquity's changes when ubuntu-drivers installs silently oem drivers on VMware products env ( or Virtualbox with default/recommended VMSVGA controller), namely open-vm-tools package.
udevadm trigger is executed and as a result Xorg and gnome-shell re-read their config including keyboard layouts. gnome-shell overrides changes made by Xorg which uses /etc/default/ keyboard ( written/updated by ubiaquity) settings.
It doesn't seem possible to stop gnome-shell updating xkb layouts.
A possible solution would be to make sure the gnome-session behind ubiquity also uses the same keyboard layout ( which makes sense during a direct ubuntu install).
Something like that :
gsettings set org.gnome. desktop. input-sources sources "[('xkb', 'fr')]"