Hi again. In short I kind of just copied that post blindly and only now looked into things further.
> Mmm, do you mean that this postinst script ends up calling setupcon > --force --save in a living Ubuntu system, not the installer of Ubuntu? > The script checks for the presence of the /lib/debian-installer.d > directory, does that directory really exist in an installed Ubuntu > system? If so, that's the problem, that directory shouldn't exist on an > installed system. >> To reproduce: >> sudo apt install --reinstall keyboard-configuration > That doesn't trigger the issue on an installed Debian system (which > doesn't have /lib/debian-installer.d). I did just try this myself and you're right, this didn't trigger it. Which got me to think more of what could have and I did recently build wine in an ubuntu chroot which is a plausible cause, I think?