[Bug 1675805] Re: Friendly recovery uses invalid font
Launchpad Bug Tracker
1675805 at bugs.launchpad.net
Mon Apr 3 11:48:01 UTC 2017
This bug was fixed in the package friendly-recovery - 0.2.35
---------------
friendly-recovery (0.2.35) experimental; urgency=medium
* friendly-recovery.service: trigger and settle udevadm before
launching, drop broken settle down commands. Thanks to Alkis
Georgopoulos. LP: #1675805
* system-summary: improve cpu_freq reading, and make the script
resilient to failures of reading cpu_freq. LP: #1675824
-- Dimitri John Ledkov <xnox at ubuntu.com> Wed, 29 Mar 2017 17:04:51
+0100
** Changed in: friendly-recovery (Ubuntu)
Status: In Progress => Fix Released
--
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:
Fix Released
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
More information about the foundations-bugs
mailing list