[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2021-02-27 Thread Bug Watch Updater
** Changed in: efivar (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844320 Title: efibootmgr -v UiAppCould not parse device path To manage

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2020-08-24 Thread Bug Watch Updater
** Changed in: efivar (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844320 Title: efibootmgr -v UiAppCould not parse device path To manage

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2020-08-24 Thread dann frazier
** Bug watch added: Debian Bug tracker #963475 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475 ** Also affects: efivar (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963475 Importance: Unknown Status: Unknown -- You received this bug notification because

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-25 Thread Ryan Harper
Thanks! I can confirm this fixes the issue we found: root@ubuntu:/# apt-cache policy efivar efivar: Installed: 37-2ubuntu2 Candidate: 37-2ubuntu2 Version table: *** 37-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package efivar - 37-2ubuntu2 --- efivar (37-2ubuntu2) eoan; urgency=medium * Backport more fixes from upstream that fix efibootmgr -v. (LP: #1844320) -- Michael Hudson-Doyle Wed, 25 Sep 2019 10:50:57 +1200 ** Changed in: efivar (Ubuntu) Status:

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-24 Thread Michael Hudson-Doyle
** Package changed: efibootmgr (Ubuntu) => efivar (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844320 Title: efibootmgr -v UiAppCould not parse device path To manage notifications about

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-20 Thread Ryan Harper
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844320 Title: efibootmgr -v UiAppCould not parse device path To manage notifications about this bug go to:

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-19 Thread Dmitry-a-durnev
efibootmgr without args lists the boot entries correctly: BootCurrent: Timeout: 1 seconds BootOrder: ,0001,000E,000F,0002,0003,0004 Boot* ubuntu Boot0001* Windows Boot Manager ... , but efiboomgr -v returns: BootCurrent: Timeout: 1 seconds BootOrder:

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: efibootmgr (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844320 Title: