The DISPLAY checks were not yet in place in 16.04 console-setup so the bug probably happens a lot more frequently on it... would be nice if they could be backported since it still has long period of support left and this is extremely annoying. I'm starting to think there is some other cause too because it seems to be much too common, why would console-setup's packaging scripts be ran all the time since the package itself updates hardly ever. Or does some trigger force that?
Note to everyone who suffers from it that this can be temporarily fixed by running "sudo kbd_mode -s", which should be much less disruptive way of solving it for a time than rebooting.
The DISPLAY checks were not yet in place in 16.04 console-setup so the bug probably happens a lot more frequently on it... would be nice if they could be backported since it still has long period of support left and this is extremely annoying. I'm starting to think there is some other cause too because it seems to be much too common, why would console-setup's packaging scripts be ran all the time since the package itself updates hardly ever. Or does some trigger force that?
Note to everyone who suffers from it that this can be temporarily fixed by running "sudo kbd_mode -s", which should be much less disruptive way of solving it for a time than rebooting.