GNU GRUB - Bugs: bug #63975, "no server is specified"...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63975: "no server is specified" error message when loading a font
Submitter: | Andrea <viavisolutions> | ||
Submitted: | Wed 29 Mar 2023 11:13:21 AM UTC | ||
Category: | User Interface | Severity: | Major |
Priority: | 5 - Normal | Item Group: | None |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | |
Open/Closed: | Open | Release: | other |
Release: | Reproducibility: | Every Time | |
Planned Release: | None |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
No changes have been made to this item
I'm using grub 2.06 on ubuntu 22.04 to create a simple rescue disk like so:
The resulting hybrid image can be booted in 4 different ways:
1. bios boot protocol, as a cdrom
2. bios boot protocol, as a hdd (say, a usb stick)
3. uefi boot protocol, as a cdrom
4. uefi boot protocol, as a hdd (say, a usb stick)
However, when booted in UEFI mode, loadfont will fail with:
I'm not sure why grub would try to load something from the network; a couple of observations:
- If you drop to a command line and execute all_functional_tests, you will see additional failures related to the unicode font.
- The grub environment (as reported by "set") contains some network-related entries that are not present when booting the same image in bios mode.
- If you load the font with the full path, grub won't complain (but, according to the documentation, that shouldn't be needed).