[Bug 1730514] Re: possible bug in folder name

[Mario Limonciello]

Well so what happened is there is an EFI variable that wasn't cleared
when you installed Ubuntu and used fwupd.  There is supposed to be a
systemd unit that would have run to clear it.  For some reason it didn't
run on your system and that's the root cause of this problem.

Share the following and we can try to figure out where the problem is:
1) Can you confirm that you don't have a /var/cache/fwupdate/done?  I suspect you shouldn't have one.
2) What is the output of the unit status?
# systemctl status fwupdate-cleanup
3) How did you install Ubuntu?  (Live CD, Alternate installer, netinst etc).


** Summary changed:

- possible bug in folder name
+ Existing install path used for UEFI firmware updates

** Package changed: fwupd (Ubuntu) => fwupdate (Ubuntu)

** Changed in: fwupdate (Ubuntu)
       Status: New => Incomplete

** Changed in: fwupdate (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fwupdate in Ubuntu.
https://bugs.launchpad.net/bugs/1730514

Title:
  Existing install path used for UEFI firmware updates

Status in fwupdate package in Ubuntu:
  Incomplete

Bug description:
  Dell XPS 13 9360 here with latest ubuntu (KDE). Clean install as sole
  operating system. I had a scheduled firmware update that didn't
  proceed on reboot. I run sudo fwupdmgr update --verbose and got (among
  other stuff):

  libfwup.c:1176 get_fd_and_media_path(): open of
  /boot/efi/EFI/fedora/fw/fwupdate-GfuBQT.cap failed: No such file or
  directory

  This is one of the common problems listed in
  https://github.com/hughsie/fwupd/wiki/Common-Problems In this case it
  might be a problem in the ubuntu packaging. The correct folder should
  have been /boot/efi/EFI/ubuntu/fw/ I mean ubuntu here, above it was
  fedora!

  The workaround was creating /boot/efi/EFI/fedora/fw/ as per the wiki.
  It's said there that in the future version the folder will be
  automatically created. Despite that, I don't see any reason to have a
  fedora folder in my file system ;)

  In my way to the workaround I found that archlinux has had a similar
  problem. I copy here the link in case it helps:
  https://bugs.archlinux.org/index.php?do=details&task_id=55815

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1730514/+subscriptions