Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"
I would suggest a new issue linking to that one instead so it's not lost.
> -----Original Message-----
> From: Michel Le Bihan <michel@lebihan.pl>
> Sent: Monday, July 27, 2020 1:01 PM
> To: Limonciello, Mario; 963475@bugs.debian.org
> Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not
> parse device path: Invalid argument"
>
>
> [EXTERNAL EMAIL]
>
> I added a comment under the existing closed issue:
> https://github.com/rhboot/efibootmgr/issues/133#issuecomment-664549236
>
> Le lundi 27 juillet 2020 à 17:54 +0000, Limonciello, Mario a écrit :
> > In that case, would you mind reporting a bug to upstream efibootmgr?
> > It seems
> > to me that your Boot0000 entry can't be properly parsed. You may
> > need to also
> > attach it to your bug report.
> >
> > > -----Original Message-----
> > > From: Michel Le Bihan <michel@lebihan.pl>
> > > Sent: Monday, July 27, 2020 12:16 PM
> > > To: Limonciello, Mario; 963475@bugs.debian.org
> > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > "Could not
> > > parse device path: Invalid argument"
> > >
> > >
> > > [EXTERNAL EMAIL]
> > >
> > > It was efibootmgr and efivar master.
> > >
> > > Le lundi 27 juillet 2020 à 16:46 +0000, Limonciello, Mario a écrit
> > > :
> > > > Was that just efibootmgr master?
> > > > If possible, can you move up to *both* efivar master and
> > > > efibootmgr
> > > > master and try again?
> > > >
> > > > > -----Original Message-----
> > > > > From: Michel Le Bihan <michel@lebihan.pl>
> > > > > Sent: Monday, July 27, 2020 11:25 AM
> > > > > To: Limonciello, Mario; 963475@bugs.debian.org
> > > > > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > > > "Could not
> > > > > parse device path: Invalid argument"
> > > > >
> > > > >
> > > > > [EXTERNAL EMAIL]
> > > > >
> > > > > Hello,
> > > > >
> > > > > I applied the fix and built the package. It didn't help. I also
> > > > > built
> > > > > latest master and I still have this issue.
> > > > >
> > > > > BTW, the computer is an OptiPlex 7040. Full hwinfo --bios:
> > > > > https://lebihan.pl/files/hwinfo-bios.txt
> > > > >
> > > > > Error trace:
> > > > > ```
> > > > > root@s217-lab00:~# /dev/shm/efibootmgr/src/efibootmgr -v
> > > > > BootCurrent: 0003
> > > > > Timeout: 2 seconds
> > > > > BootOrder: 0003,0004,0001,0005,000A,0007,0008,0009,0002
> > > > > Boot0000* Windows Boot ManagerCould not parse device path:
> > > > > Invalid
> > > > > argument
> > > > > error trace:
> > > > > /build/efivar-yvRv8P/efivar-37/src/include/efivar/efivar-
> > > > > dp.h:1208
> > > > > efidp_is_valid(): invalid device path node type: Invalid
> > > > > argument
> > > > > ```
> > > > >
> > > > > Michel Le Bihan
> > > > >
> > > > > Le lundi 27 juillet 2020 à 15:28 +0000, Limonciello, Mario a
> > > > > écrit
> > > > > :
> > > > > > > -----Original Message-----
> > > > > > > From: Michel Le Bihan <michel@lebihan.pl>
> > > > > > > Sent: Sunday, July 26, 2020 2:58 PM
> > > > > > > To: 963475@bugs.debian.org
> > > > > > > Subject: Bug#963475: libefivar1: "efibootmgr -v" fails with
> > > > > > > "Could
> > > > > > > not
> > > > > > > parse device path: Invalid argument"
> > > > > > >
> > > > > > >
> > > > > > > [EXTERNAL EMAIL]
> > > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > What's preventing the upstream fix from being applied to
> > > > > > > this
> > > > > > > package?
> > > > > > >
> > > > > > > Michel Le Bihan
> > > > > >
> > > > > > I personally can't reproduce the failure on my system's
> > > > > > firmware.
> > > > > > Can you apply the fix locally and confirm it actually helps?
Reply to: