Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1015472
| From | Francesco Poli <invernomuto@paranoici.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" |
| Date | 2020-06-27 15:40 +0200 |
| Message-ID | <AmjdM-3em-11@gated-at.bofh.it> (permalink) |
| References | <AkoAW-6xC-5@gated-at.bofh.it> <AkoAW-6xC-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Mon, 22 Jun 2020 08:46:14 +0200 Francesco Poli (wintermute) wrote: [...] > I searched the web and found a github [issue], that claims the > problem is in efivar, mentioning a [commit] that is supposed > to fix it. > But it seems to me that the [code] currently in Debian unstable > does not include this fix. > > [issue]: <https://github.com/rhboot/efibootmgr/issues/133> > [commit]: <https://github.com/rhboot/efivar/commit/4e04afc2df9bbc26e5ab524b53a6f4f1e61d7c9e> > [code]: <https://sources.debian.org/src/efivar/37-2.1/src/ucs2.h/> > > I hope I am not completely off-track... :-p > > Could you please investigate the issue and cherrypick the patch, > if appropriate? I tried to downgrade from libefiboot1/37-2.1 to libefiboot1/37-2 and I can confirm that the problem vanishes after the downgrade. Is there any news on your side? Please let me know, thanks for your time! -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" "Francesco Poli (wintermute)" <invernomuto@paranoici.org> - 2020-06-22 09:00 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Francesco Poli <invernomuto@paranoici.org> - 2020-06-27 15:40 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-26 22:10 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 18:30 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Kevin Locke <kevin@kevinlocke.name> - 2020-07-27 21:00 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 19:20 +0200
Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument" Michel Le Bihan <michel@lebihan.pl> - 2020-07-27 20:10 +0200
Bug#963475: Could not parse device path: Invalid argument Omer Ozarslan <omerfaruko@gmail.com> - 2020-07-28 03:20 +0200
Bug#963475: Could not parse device path: Invalid argument Michel Le Bihan <michel@lebihan.pl> - 2020-07-29 22:50 +0200
csiph-web