[Bug 1675805] Re: Friendly recovery uses invalid font

[Dimitri John Ledkov]

On 28 March 2017 at 09:57, Alkis Georgopoulos
<1675805 at bugs.launchpad.net> wrote:
> I'm afraid the ordering there won't be guaranteed, that udevadm --settle
> will indeed be called after udevadm --trigger. Will it?
>

That would be crazy.... don't you think?!

https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStartPre=

Syntax is the same as for ExecStart=, except that multiple command
lines are allowed and the commands are executed one after the other,
serially.

-- 
Regards,

Dimitri.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/1675805

Title:
  Friendly recovery uses invalid font

Status in friendly-recovery package in Ubuntu:
  New

Bug description:
  There are a lot of similar bug reports for this, but they all seem stalled.
  Here's a specific issue with a proposed one-line patch that works.

  When I boot my Ubuntu 16.04.2 and select recovery mode, the menu text
  is unreadable, showing boxes instead of characters, like console-setup
  hasn't ran, while it did.

  Then I edit /lib/recovery-mode/recovery-menu and insert the following line at the top:
  udevadm trigger && udevadm settle -t 10

  After I reboot, the problem is gone.

  I'll attach two screenshots, "before.png" and "after.png", showing the
  issue.

  Some info for my localization setup; but it shouldn't matter, it should be the same in any locale.
  $ cat /etc/default/locale 
  LANG="el_GR.UTF-8"
  $ cat /etc/default/console-setup 
  ACTIVE_CONSOLES="/dev/tty[1-6]"
  CHARMAP="UTF-8"
  CODESET="guess"
  FONTFACE="Fixed"
  FONTSIZE="8x16"
  VIDEOMODE=

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1675805/+subscriptions