Dear Maintainer,

My problem is the same as describe here:
https://github.com.cnpmjs.org/fwupd/fwupd/issues/1330
When I downgrade to the stable version I saw that same error.
But in version 1.3.3 I receive that one but I also cannot update
firmware:
fwupdmgr update
No upgrades for Thunderbolt Controller, current is 20.00: 20.00=same, 17.01=older
No upgrades for System Firmware, current is 0.1.33: 0.1.30=older, 0.1.29=older, 0.1.28=older, 0.1.26=older, 0.1.25=older, 0.1.33=same
Upgrade available for UEFI Device Firmware from 184.65.3590 to 184.70.3626
20KF001GGE must remain plugged into a power source for the duration of the update to avoid damage. Continue with update? [Y|n]: y
Downloading 184.70.3626 for UEFI Device Firmware...
Decompressing…           [***************************************]
Authenticating…          [***************************************]
Updating UEFI Device Firmware…                                   ]
Scheduling…              [***************************************]
failed to write data to efivarfs: Error writing to file descriptor: No space left on device

Nothing fwupd can do about this.  It's either efivarfs NV store is full on your box or BIOS is locking it down.

Nothing fwupd can do about this.  It's either efivarfs NV store is full on your box or BIOS is locking it down.

Dear Maintainer,

A warning displayed each time I login the system (Lenovo IdeaPad 340) says
there is an update available. After ignoring it for a few weeks, I tried
updating the firmware, specifically the UEFI dbx device (217 --> 371), using
"fwupdmgr update".  I received the same message:

        "failed to write data to efivars: Error writing to file descriptor: No
space left on device"

After looking it up (Internet search, DBTS), I found this bug stating that
nothing can be done. I understand that there is nothing else to do if there is
not more room. Regarding the other suggested possibility (about the BIOS
locking it down), is there any option to convince the BIOS to be more "open"?

Anyway, another question is about a way to remove or to avoid the warning when
login (when the update is not possible as is our case).

The last question is to calm down my curiosity because of my poor understanding
of the life of a (software) bug. This is one of my first bug reports, and I
still don't get the criteria to change the bug status. Why the bug is open yet?
I mean, it has been dealt with. What else can be done? It is my understanding
that the information will still be available even if the bug is closed.

Thank you in advance for your time. Regards, robert

Dear Maintainer,

I am writing to add that the firmware has been updated. I do not know how,
when, or why.

The message informing about a new possible upgrade did not show up recently.
When I realized that (it took more than a few boot cycles), I reviewed the
history which confirmed the upgrade.

This is not helpful. I mean things happening without any supervision.

Thanks anyway. Regards.

I also ran into this "No space left on device" error, but in a different
situation.

I knew that a particular Dell laptop I was working on had firmware
available via fwupd, so I had the bright idea to boot Debian Live and
install fwupd to update it.

But I realized some firmware images (maybe _all_ system BIOS images?)
actually work by writing things into the EFI partition, to be updated
upon reboot (like how MS Windows also does it). So my bright idea didn't
work, since I didn't yet have a drive installed with an EFI partition.
But due to the error being about "No space" I wasted some time trying to
resolve that, before realizing the real issue. After I had a proper
Debian install with EFI it worked fine.

So I think part of the issue here is that fwupd should better detect
when it's completely missing things it needs to be successful and give
an improved error and maybe point to documentation about how it works.

In my case it was "no EFI partition", but others in this bug report have
alluded to things like efivars, the BIOS locking things down, etc. So
some additional sanity checks of these things would be nice.

Thanks,

Dear Maintainer,



   * What led up to the situation? Tried to update UEFI dbx 20230501 -> 20241101
   * What exactly did you do (or not do) that was effective (or
     ineffective)? Tried updating by Discover & fwupd, then rebooting
   * What was the outcome of this action? Firmware was not updated, update keeps showing up in Discover
   * What outcome did you expect instead? The firmware to be updated or the update not to show up