Hello, Mike McGuire, le sam. 05 janv. 2019 03:25:42 +0000, a ecrit: > This started happening to me recently, not sure what change could be to blame > but I found a lengthy thread on the ubuntu bug tracker that seems to confirm > things. Copying the relevant post: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/comments/66 > > --- > > In my case, I traced the issue to the keyboard-configuration package postinst > script, which ends up calling 'setupcon --force --save' which in turn calls > 'kbd_mode -u'
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). > It looks like the checks to avoid this behavior while a graphic environment > is active don't work in the context of the installer. Err, since --force is passed, the checks are not used, so it's no wonder. But it shouldn't be happening in a non-debian-installer case. FTR: we do need --force because the Debian installer lives within a bterm, and thus setupcon can not know that it's actually running within a Linux console, just with bterm in between. Samuel