Bug#818065: console-setup is not read correctly at boottime and must be started manually

Hallöchen!

I confirm this bug (at least, that the correct font is not set) on
Trixie on one of my two workstations.  It is difficult to say
whether the root cause is the same as for the issuer, as 10 years
are a long time.  On the other hand, the whole procedure doesn’t
seem to have changed:

- console-setup.service is started at boot time

- console-setup.service runs /lib/console-setup/console-setup.sh

- /lib/console-setup/console-setup.sh runs setupcon to recreate the
  /etc/console-setup/cache* files if:

  - run not at boot time OR
  - cache* files don’t exist or are outdated

- Finally: /lib/udev/rules.d/90-console-setup.rules runs
  /etc/console-setup/cached* at boot time (the exact trigger is
  unknown to me)

In my case, it is a race: udev runs cached_setup_font.sh too early in
the boot process.  Adding “sleep 2” at the top of
cached_setup_font.sh solves the problem.  So, at boot time happens
probably:

1. udev calls /etc/console-setup/cached*
2. The console is reset to default fonts
3. console-setup.service is started

On my workstation without this issue, (2) probably happens first.

My workaround is to patch /lib/console-setup/console-setup.sh so
that (3) *always* calls setupcon.

Bye,
Torsten.

-- 
Torsten Bronger