Ubuntu 22.04.4 - From today it's appear this error "Failed to update metadata for lvfs: checksum failure: failed to verify data, expected 740a74633fc78e329ea701b0c12f8761c24b7988" #6888
Comments
|
What does |
|
Same issue on my "6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux": |
Please see attached file: |
omg it's so long result.... i try to post here: |
|
Or i create a copy/paste here @hughsie |
|
I'm not sure what's happened, but in the meantime I've kicked off a rebuild just in case. |
i'm need to do somethigs on my side ? If yes ask..... consider I'm not very knowledgeable about Linux. |
|
wait a few minutes, then |
oh ok... I noticed this error today. while I was trying to solve another problem with the snap store (ndr persistent notification about software upgrade appears at every reboot). |
|
@hughsie |
|
This is what I get: |
|
I have the same error: for Ubuntu 20.04: |
|
If you follow my same debugging, do you get checksums that match? |
|
Same problem here, suddenly from today.
Yes |
@hughsie I can follow up to this step: |
|
|
I also see the same issue. wget is working for xml, but fwupdmgr is failing |
|
Can you attach the output of |
|
The error is away for me. |
|
Now it started to work in my case |
|
@hughsie apparently for me it's fixed.... |
|
From other setup: |
|
Two of four Ubuntu 22.04 servers started to complain today: I'm not sure where this checksum (0a5a850327f8e8b196b2d79e79ce347cb86037f1) comes from since: |
|
Btw, firmware-07078-stable.xml.gz is 1.1MB long. I'm not sure if the limit was updated but in 5173 it was set to 800k. |
Ohh that's it! Super old versions of fwupd had a hardcoded 1MB limit. Ubuntu should backport 0729ab5 as a priority. I'll see if I can fix something LVFS-side. |
Thank you, @hughsie . Do you need someone to report this to Launchpad for Ubuntu, so that Ubuntu can update its repositories? If so, I'll be happy to file the report. Alternatively, is compiling from source the only alternative method of getting an updated fwupdmgr until then? (I'm really not good with compiling!) |
Yes, please. In general I need Canonical to care a lot more about doing updates to the fwupd package.
There's also a snap version too, but be sure to uninstall the deb version if you install the nap one instead. |
|
I've pushed (and deployed) https://gitlab.com/fwupd/lvfs-website/-/commit/8908020c1dddaa7ff1e960966c1821d45c820073 and regenerated the legacy metadata -- now: which I think is going to work. The next step is to start picking and choosing what updates are presented to such old fwupd versions. Perhaps we can filter out non-security issues or something. The underlying problem is that Canonical isn't keeping fwupd up to date -- 1.7.9 was released on 25th July 2022. |
I'll post back here with the report once I've reported this on Launchpad.
I uninstalled the apt version and installed the snap version. It works, thank you! (I had to close and reopen the terminal because of caching.) So, I think that snap is a better solution than relying on Canonical. |
|
@KaiChuan-Hsieh can you help here? |
|
I have reported this on Launchpad as a bug in Ubuntu. If you have this problem, please vote for it: Go to the bug report; log in; and select the green writing on the left near the top. You can optionally subscribe to the bug's updates (in the right-hand column). Thank you |
I'll raise it to internal team to evaluate the feasibility. Thanks, |
Describe the bug
When i open the Ubuntu Snap Store and try to check update it's appear this error.
Apparently the check for update it's completed correctly.
Reading some thread on forum for resolve this issue need to do this from Terminal...i do this:
diabolik@NUC-Ubuntu:~$ sudo fwupdmgr refresh --force Updating lvfs Downloading… [***************************************] Downloading… [***************************************] Downloading… [***************************************] Failed to update metadata for lvfs: checksum failure: failed to verify data, expected 740a74633fc78e329ea701b0c12f8761c24b7988fwupd version information
diabolik@NUC-Ubuntu:~$ fwupdmgr --version runtime org.freedesktop.fwupd 1.7.9 runtime com.dell.libsmbios 2.4 compile org.freedesktop.gusb 0.3.10 compile com.hughsie.libjcat 0.1.9 runtime org.kernel 6.5.0-21-generic compile org.freedesktop.fwupd 1.7.9 runtime org.freedesktop.gusb 0.3.10Please provide the output of the fwupd devices recognized in your system.
`diabolik@NUC-Ubuntu:~$ fwupdmgr get-devices --show-all-devices
NUC7PJYHN
│
├─GeminiLake [UHD Graphics 605]:
│ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
│ Current version: 06
│ Vendor: Intel Corporation (PCI:0x8086)
│ GUID: 428afab4-0694-59d7-ab82-09be6ecefa9d
│ 7e675f13-a2d7-52fa-b886-05280bb915a6
│ 52e5049a-b195-5849-9498-e73ee3113abd
│ 6f398ef1-6999-553b-822a-e5798e7d3809
│ Device Flags: • Internal device
│ • Cryptographic hash verification is available
│
├─HS-SSD-E100 512G:
│ Device ID: c46944fe84f2b057692258cc87a812cc86364881
│ Summary: ATA drive
│ Current version: 030fAA20
│ Update Error: No vendor ID set
│ GUID: 0dc6e288-2ed0-5ef3-8c9f-f2eded1c7c1b
│ 9022c257-5da3-5c5a-a070-e717ec4b185d
│ 372f0676-1fad-5401-b708-00c85066c469
│ Device Flags: • Internal device
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│ • Updatable
│
├─Pentium Silver J5040 CPU @ 2.00GHz:
│ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ Current version: 0x00000022
│ Vendor: Intel
│ GUID: b9a2dd81-159e-5537-a7db-e7101d164d3f
│ 30249f37-d140-5d3e-9319-186b1bd5cac3
│ 54817722-b948-55a7-8324-3d4736e90181
│ f02ec022-4f79-53c2-a68f-08ea48563cb4
│ Device Flags: • Internal device
│
├─System Firmware:
│ │ Device ID: a45df35ac0e948ee180fe216a5f703f32dda163f
│ │ Summary: UEFI ESRT device
│ │ Current version: 70
│ │ Minimum Version: 70
│ │ Vendor: Intel(R) Client Systems (DMI:Intel Corp.)
│ │ Update State: Success
│ │ GUID: 856758ee-a971-40c7-8ee4-26d67b4f6704
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI revocation database
│ Current version: 77
│ Minimum Version: 77
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUID: c6682ade-b5ec-57c4-b687-676351208742
│ f8ba2887-9411-5c36-9cee-88995bb39731
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│ • Only version upgrades are allowed
│ • Signed Payload
│
└─TPM:
Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
Summary: TPM 2.0 Device
Current version: 403.0.0.0
Vendor: Intel (TPM:INTC)
GUID: ff71992e-52f7-5eea-94ef-883e56e034c6
34801700-3a50-5b05-820c-fe14580e4c2d
8e1cbc5d-5a11-5149-bfea-b6065d5296ba
03f304f4-223e-54f4-b2c1-c3cf3b5817c6
52d7b679-db28-5bf7-bd87-41d77aeec600
Device Flags: • Internal device
`
Additional questions
The text was updated successfully, but these errors were encountered: