[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"



Package: libefivar1
Version: 37-2.1
Severity: important

Hello!

One week ago I had no issues in running:

  $ efibootmgr -v

but today, I get:

  $ efibootmgr -v
  BootCurrent: 0001
  Timeout: 1 seconds
  BootOrder: 0001,0000
  Boot0000* debianCould not parse device path: Invalid argument

Please note that (luckily!) the system is able to boot and reboot,
and that the non-verbose output is:

  $ efibootmgr
  BootCurrent: 0001
  Timeout: 1 seconds
  BootOrder: 0001,0000
  Boot0000* debian
  Boot0001* debian2

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?

Thanks for your time.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libefivar1 depends on:
ii  libc6  2.30-8

libefivar1 recommends no packages.

libefivar1 suggests no packages.

-- no debconf information


Reply to: