Comment 46 for bug 1762952

@Adam: Sad to hear that the proposed fix caused yet another regression, and sorry for the inconvenience it caused.

On 2018-07-25 03:31, Adam Conrad wrote:
> That said, I think the "run it sometimes, but not always" fix was
> probably naive at best. The only two options that seem to make
> sense for fixing this properly are:
>
> 1) Make GNOME stop writing things to that file that console-setup
> doesn't understand, or
> 2) Make console-setup understand the things GNOME writes to that
> file.

Basically it's the other way around; console-setup adds XKBOPTIONS to /etc/default/keyboard, sometimes behind the scenes, but GNOME does not include GUIs for controlling XKBOPTIONS system wide (only per user). At the same time, when you use the GNOME GUI to change the keyboard configuration system wide, it brutally drops any XKBOPTIONS in /etc/default/keyboard.

I'm going to bring it up with the desktop team, and try to figure out a better approach to handle this dissonance. Then let's make sure in advance that whatever we comes up with does not interfere with the installer.