cragw

The update has been successfully verified on a machine-supported OS, and the same patch has been cross-checked on another system running Linux. It is unlikely that this is a fwupd...

I cannot reproduce this issue on Ubuntu. Can you enable verbose mode and attach the journal log? ``` $ fwupdmgr modify-config fwupd VerboseDomains "*" $ fwupdmgr update ```

Can you try this instead? ``` $ sudo systemctl stop fwupd $ sudo /usr/libexec/fwupd/fwpud -vv 2>&1 | tee /tmp/fwupd.txt // in a new terminal $ fwupdmgr update ```

fwupd on Ubuntu 16.04 has already reached its end-of-life, there may be little or no updates available.

hi @brjsp , can you provide full device list please? ``` $ fwupdmgr get-devices --show-all-devices ```

> [TPM firmware](https://dl.dell.com/FOLDER11323524M/1/DELLTPM_STHE4_1.769_64_v3.exe) dated 2024-05-27. The .exe file can be run within Windows PE. > AFAIK no TPM updates for Linux. > [Thunderbolt firmware](https://dl.dell.com/FOLDER10502992M/2/Intel-Thunderbolt-Controller-Driver_TBB12_WIN_1.41.1379.0_A18_01.EXE) dated 2025-03-07. The file does not...

This issue is similar to #8368 that will impact WD19/WD22 docks across fwupd 2.0.4, 2.0.5 and 2.0.6. The next stable release 2.0.7 should have #8481 included to address this bug.

An improvement 28d686212 was added a few days ago that addresses some conditions like this. Can you try a build with the mentioned fix?

@superm1 do you know how to debug the issue related to a missing device for the history to upload?

> Can you check if these happen in venv too? for issue 1, no reports require uploading - snap fwupd only. for issue 2, incorrect version format - both snap...