From: TegarOk <TegarOk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] efibootmgr weird output
Date: Sat, 06 Aug 2022 00:41:02 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38492@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]
New issue by TegarOk on void-packages repository
https://github.com/void-linux/void-packages/issues/38492
Description:
### Is this a new report?
Yes
### System Info
Void 5.10.109_1 x86_64 AuthenticAMD notuptodate rrmFFFFF
### Package(s) Affected
efibootmgr-18_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
When execute efibootmgr -v on terminal, the output should be something like this:
`Boot0002* Void Linux 5.18 HD(XXXXXX)r.o.o.t.=XXXXXXX .q.u.i.e.t. .s.p.l.a.s.h. .r.w. .r.a.d.e.o.n...s.i._.s.u.p.p.o.r.t.=.0. .a.m.d.g.p.u...s.i._.s.u.p.p.o.r.t.=.1. .a.m.d.g.p.u...d.p.m.=.1. .a.m.d.g.p.u...g.p.u._.r.e.c.o.v.e.r.y.=.2. .a.p.p.a.r.m.o.r.=.1. .n.e.t...i.f.n.a.m.e.s.=.0. .i.o.m.m.u.=.p.t. .a.m.d._.i.o.m.m.u.=.1. .a.c.p.i._.e.n.f.o.r.c.e._.r.e.s.o.u.r.c.e.s.=.l.a.x. .i.n.i.t.r.d.=.\.i.n.i.t.r.a.m.f.s.-.5...1.8...1.1._.1...i.m.g.`
### Actual behaviour
But on the latest version. efibootmgr didnt report something like that, instead like this:
`Boot0002* Void Linux 5.18 VenHw(99e275e7-75a0-4b37-a2e6-c5385e6c00cb)72006f006f0074003d005a00460053003d005a004600530052002f0056006f00690064002000710075006900650074002000730070006c00610073006800200072007700200072006100640065006f006e002e00730069005f0073007500700070006f00720074003d003000200061006d0064006700700075002e00730069005f0073007500700070006f00720074003d003100200061006d0064006700700075002e00640070006d003d003100200061006d0064006700700075002e006700700075005f007200650063006f0076006500720079003d0032002000610070007000610072006d006f0072003d00310020006e00650074002e00690066006e0061006d00650073003d003000200069006f006d006d0075003d0070007400200061006d0064005f0069006f006d006d0075003d003100200061006300700069005f0065006e0066006f007200630065005f007200650073006f00750072006300650073003d006c0061007800200069006e0069007400720064003d005c0069006e0069007400720061006d00660073002d0035002e00310038002e00310031005f0031002e0069006d006700`
### Steps to reproduce
1. Open terminal
2. launch "efibootmgr -v"
3. Weird Output
4. Done
next reply other threads:[~2022-08-05 22:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 22:41 TegarOk [this message]
2022-08-06 1:33 ` sgn
2022-08-06 1:35 ` sgn
2022-08-06 1:36 ` sgn
2022-08-06 1:41 ` TegarOk
2022-08-06 1:42 ` TegarOk
2022-08-06 1:43 ` sgn
2022-08-06 1:44 ` sgn
2022-08-06 1:45 ` sgn
2022-08-06 1:46 ` sgn
2022-08-06 1:47 ` [ISSUE] [CLOSED] " TegarOk
2022-08-06 1:47 ` TegarOk
2022-08-06 1:47 ` sgn
2022-08-06 1:52 ` TegarOk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38492@inbox.vuxu.org \
--to=tegarok@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).