Bug#819288: console-setup-linux: keyboard-setup.sh init script (actually, the cached scripts) rely on /tmp, which may not be mounted at early boot

[Felipe Sateler]

Package: console-setup-linux
Version: 1.141
Severity: normal

Hi,

The cached scripts rely on the compiled keyboard maps to be present in
/tmp (presumably by having being saved by setupcon -k). However, when
/tmp is a separate filesystem, this will never work, as the init script
is run to soon, and for memory-backed /tmp it can only work during the
same boot.

The cached stuff needs to be stored elsewhere.

-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages console-setup-linux depends on:
ii init-system-helpers 1.29
ii initscripts 2.88dsf-59.3
ii kbd 2.0.3-2
ii keyboard-configuration 1.141

console-setup-linux recommends no packages.

Versions of packages console-setup-linux suggests:
ii console-setup 1.141

Versions of packages keyboard-configuration depends on:
ii debconf 1.5.59
ii liblocale-gettext-perl 1.07-1+b1

Versions of packages console-setup depends on:
ii debconf 1.5.59
ii keyboard-configuration 1.141
ii xkb-data 2.17-1

Versions of packages console-setup suggests:
ii locales 2.22-4
ii locales-all [locales] 2.22-4
ii lsb-base 9.20160110

Versions of packages console-setup-linux is related to:
pn console-common <none>
ii console-data 2:1.12-5
pn console-tools <none>
pn gnome-control-center <none>
ii kbd 2.0.3-2
ii systemd 229-3

-- debconf information:
* keyboard-configuration/model: Generic 105-key (Intl) PC
* keyboard-configuration/store_defaults_in_debconf_db: true
* keyboard-configuration/xkb-keymap: us
* keyboard-configuration/layout:
console-setup/guess_font:
keyboard-configuration/ctrl_alt_bksp: false
console-setup/charmap47: UTF-8
console-setup/fontsize-fb47: 8x16
keyboard-configuration/unsupported_layout: true
* keyboard-configuration/modelcode: pc105
console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/optionscode:
* keyboard-configuration/compose: No compose key
* keyboard-configuration/layoutcode: us
* keyboard-configuration/toggle: No toggling
keyboard-configuration/unsupported_config_options: true
console-setup/use_system_font:
console-setup/fontsize-text47: 8x16
console-setup/fontface47: Fixed
* keyboard-configuration/variantcode:
* keyboard-configuration/other:
keyboard-configuration/unsupported_config_layout: true
console-setup/codesetcode: Lat15
keyboard-configuration/unsupported_options: true
console-setup/fontsize: 8x16
debian-installer/console-setup-udeb/title:
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/variant: English (US)
* keyboard-configuration/switch: No temporary switch
console-setup/framebuffer_only:
console-setup/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages

[Anton Zinoviev]

On Sat, Mar 26, 2016 at 12:53:45AM -0300, Felipe Sateler wrote:
>
> The cached scripts rely on the compiled keyboard maps to be present in
> /tmp (presumably by having being saved by setupcon -k).

Hm, this is totaly unexpected. Normally the cached scripts rely on
compiled keyboard maps in /etc.

The only reason I can see the cached scripts rely on maps in /tmp is
that /etc/ was read-only when `setupcon --save-only` was executed by
/etc/init.d/console-setup.sh or `dpkg-reconfigure`.

The cached scripts should never rely on files in /tmp and this is a bug
I will have to fix somehow. However, an important question we have to
investigate here is this: why in your system the cached scripts rely on
files in /tmp.

Anton Zinoviev

[Felipe Sateler]

Interesting. Indeed, re-running console-setup.sh (after boot)
generates a new cached_setup_keyboard script that uses a file in /etc.
Even more, I cannot reproduce the original problem, and cannot find in
the code how did this happen in the first place (after all, the script
should not have been written to /etc either!)

But, maybe setupcon should force remove the cached script if it
contains references to /tmp (or better yet, the script does not match
/etc/console-setup/cached_*.map.gz)

--

Saludos,
Felipe Sateler

[Anton Zinoviev]

On Sun, Mar 27, 2016 at 12:06:39PM -0300, Felipe Sateler wrote:
>
> But, maybe setupcon should force remove the cached script if it
> contains references to /tmp (or better yet, the script does not match
> /etc/console-setup/cached_*.map.gz)

Yes, something has to be done about this.

Anton Zinoviev