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.
The second option is certainly the more appealing of the two, but it's clearly not going to happen before the point release in two days.
Re-opening this bug as we had to revert the fix, because it was causing an installer regression:
https:/ /bugs.launchpad .net/ubuntu/ +source/ ubiquity/ +bug/1783326
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.
The second option is certainly the more appealing of the two, but it's clearly not going to happen before the point release in two days.