Fwupd: Invalid Compressed data error

Created on 29 Nov 2020  Β·  11Comments  Β·  Source: fwupd/fwupd

Describe the bug

I am unable to update the firmware metadata on my system.

scoronado@piensalo-bien ξ‚° ~ ξ‚° fwupdmgr get-updates
Firmware metadata has not been updated for 30 days and may not be up to date.

Update now? (Requires internet connection) [y|N]: y
Updating lvfs
Downloading…             [***************************************]
Invalid compressed data
✘ scoronado@piensalo-bien ξ‚° ~ ξ‚° echo $?
1

Steps to Reproduce
Steps to reproduce the behavior.
Run fwupdmgr get-updates from the command line and accept the firmware update metadata

Expected behavior
I expected the latest metadata with a clean exit.

fwupd version information
Please provide the version of the daemon and client.

✘ scoronado@piensalo-bien ξ‚° ~ ξ‚° fwupdmgr --version
client version: 1.5.2
compile-time dependency versions
    gusb:   0.3.5

daemon version: 1.5.2

Please note how you installed it (apt, dnf, pacman, source, etc):

Installed via Arch Linux community repository using pacman

fwupd device information
Please provide the output of the fwupd devices recognized in your system.

 ✘ scoronado@piensalo-bien ξ‚° ~ ξ‚° fwupdmgr get-devices --show-all-devices
20FL000NUS
β”‚
β”œβ”€Intel Management Engine:
β”‚     Device ID:          570d24e21cec6aadc4c7019ea2d7cfc16c22191b
β”‚     Current version:    184.77.3664
β”‚     Minimum Version:    184.77.3664
β”‚     Vendor:             DMI:LENOVO
β”‚     GUIDs:              a7c68c44-60f0-431c-9242-926912892f28
β”‚                         aaa760ee-7215-5d8e-8dd3-5c7160bc7bff
β”‚     Device Flags:       β€’ Internal device
β”‚                         β€’ Updatable
β”‚                         β€’ System requires external power source
β”‚                         β€’ Needs a reboot after installation
β”‚                         β€’ Device is usable for the duration of the update
β”‚   
β”œβ”€Intel(R) Coreβ„’ i7-6600U CPU @ 2.60GHz:
β”‚     Device ID:          4bde70ba4e39b28f9eab1628f9dd6e6244c03027
β”‚     Current version:    0x000000d6
β”‚     Vendor:             Intel
β”‚     GUIDs:              b9a2dd81-159e-5537-a7db-e7101d164d3f
β”‚                         30249f37-d140-5d3e-9319-186b1bd5cac3
β”‚                         28d7f31c-1663-5b15-a900-94a71cbcd53f
β”‚                         e4bc7423-9fec-55a6-8f6c-827c40992491
β”‚     Device Flags:       β€’ Internal device
β”‚   
β”œβ”€SAMSUNG MZ7LN512HMJP-000L7:
β”‚     Device ID:          e421b2fc248391f6fe3e55ddbb3c9043be068bd0
β”‚     Summary:            ATA Drive
β”‚     Current version:    MAV02L6Q
β”‚     Vendor:             Samsung (ATA:0x144D)
β”‚     GUIDs:              b987c66f-bb70-54a1-b880-e1c41ba2c222
β”‚                         c9706c50-0f93-5b57-af6e-4e3fd77ea10e
β”‚                         9aa5c587-9906-564a-b5d6-baffbf019028
β”‚     Device Flags:       β€’ Internal device
β”‚                         β€’ Updatable
β”‚                         β€’ System requires external power source
β”‚                         β€’ Needs a reboot after installation
β”‚                         β€’ Device is usable for the duration of the update
β”‚   
β”œβ”€Skylake GT2 [HD Graphics 520]:
β”‚     Device ID:          5792b48846ce271fab11c4a545f7a3df0d36e00a
β”‚     Current version:    07
β”‚     Vendor:             Intel Corporation (PCI:0x8086)
β”‚     GUIDs:              0efd51bf-82d9-5b36-a627-5f4cb8791aae
β”‚                         9ab6f3db-aa83-5f84-8301-06ba4459738e
β”‚                         2f7ef0d3-15f0-571c-b852-de72f1c7c730
β”‚                         bdcb90a0-e7cd-5d77-995d-d79b7183aa29
β”‚     Device Flags:       β€’ Internal device
β”‚                         β€’ Cryptographic hash verification is available
β”‚   
β”œβ”€System Firmware:
β”‚ β”‚   Device ID:          3762edb590127a8d7498cf374bd920ce65fc54c2
β”‚ β”‚   Current version:    0.1.34
β”‚ β”‚   Minimum Version:    0.1.22
β”‚ β”‚   Vendor:             LENOVO (DMI:LENOVO)
β”‚ β”‚   GUIDs:              0b145790-0d11-4dee-9c2a-19ddbcbb200c
β”‚ β”‚                       230c8b18-8d9b-53ec-838b-6cfc0383493a
β”‚ β”‚                       f8a13b1e-34af-5e8d-8773-4ff345768048
β”‚ β”‚   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
β”‚ β”‚ 
β”‚ └─Intel AMT [unprovisioned]:
β”‚       Device ID:        e2623122c99d58220498aacbfcfdb1baebbae3c5
β”‚       Summary:          Hardware and firmware technology for remote out-of-band management
β”‚       Current version:  11.8.77.3664
β”‚       Bootloader Version:11.8.77.3664
β”‚       Vendor:           Intel Corporation
β”‚       GUID:             2800f812-b7b4-2d4b-aca8-46e0ff65814c
β”‚       Device Flags:     β€’ Internal device
β”‚     
└─UEFI Device Firmware:
      Device ID:          3b6d9c846a832bbcf3af788610c2baaea129f9bb
      Current version:    65544
      Minimum Version:    1
      Vendor:             DMI:LENOVO
      GUIDs:              2433c86b-6d72-4330-84ef-1972b1fe6e27
                          dbaa8618-6e64-5ffd-8688-ae3cccb5c93b
      Device Flags:       β€’ Internal device
                             β€’ Updatable
                            β€’ System requires external power source
                            β€’ Needs a reboot after installation
                            β€’ Device is usable for the duration of the update

Additional questions

  • Operating system and version: Arch Linux x86_64
  • Have you tried rebooting? Yes
  • Is this a regression? Yes
bug
Source
picture scoronado12
👀1

Most helpful comment

I have the same issue as well on Arch, , and fwupdmgr 1.5.2.
Solved it by uninstalling then install the fwupd

picture elhossary on 2 Dec 2020
👍6 🎉2

All 11 comments

I have tried renaming the directory, /var/lib/fwupd/remotes.d/lvfs to see if fwupd would download a fresh copy in its place, and it did not work.

scoronado12 picture scoronado12 on 29 Nov 2020

Can you provide the output of the remote itself in /etc/fwupd/remotes.d?

superm1 picture superm1 on 29 Nov 2020

Thanks for replying. This looks like a directory.

[root@piensalo-bien remotes.d]# ls -l
total 32
-rw-r--r-- 1 root root 247 Nov 25 16:58 dell-esrt.conf
-rw-r--r-- 1 root root 283 Nov 25 16:58 fwupd-tests.conf
-rw-r--r-- 1 root root 327 Nov 20  2019 lvfs.conf
-rw-r--r-- 1 root root 406 Nov 25 16:58 lvfs.conf.pacnew
-rw-r--r-- 1 root root 372 Nov 20  2019 lvfs-testing.conf
-rw-r--r-- 1 root root 361 Nov 25 16:58 lvfs-testing.conf.pacnew
-rw-r--r-- 1 root root 317 Nov 25 16:58 vendor.conf
-rw-r--r-- 1 root root 296 Nov 25 16:58 vendor-directory.conf

These pacnew files look suspiciously like part of a pacman operation that went wrong, should I remove them?

scoronado12 picture scoronado12 on 29 Nov 2020

I suspect the ones that are not pacnew are the problem actually.. I think you should finish the packaging operation (which probably means renaming those files)

superm1 picture superm1 on 29 Nov 2020

Looks like this was an effect of an upgrade that occurred as we had a brief power surge, not an issue with fwupd itself. It works perfectly now.

Thank you @superm1

scoronado12 picture scoronado12 on 30 Nov 2020
👍1

I have same situation (Invalid compressed data), but it is not looks like update issue.
If I disable Keyring=gpg, then I'm able to update. So It looks like something gpg related. Are there any way to trace this out?

alxchk picture alxchk on 30 Nov 2020

It's related to some changes recently to allow newer library to work with older daemon.
@alxchk are you on 1.5.2? Hand install? Packaged install? Why didn't your .conf files get updated on upgrades?

superm1 picture superm1 on 30 Nov 2020

Yes, it's 1.5.2. I'm on gentoo, and looking to the 1.5.2 ebuild I don't see anything related to updating conf files.
Are there any info what should be done?

Okay, looks like this Keyring= statement is not required anymore. Than I'll just comment it out. I expected that this completely disables sign checks.

alxchk picture alxchk on 30 Nov 2020

Correct it's not needed. See: https://github.com/fwupd/fwupd/commit/d5aab65f30bbc7490240b752dc76d7668aa38f7e#diff-49bf8eeb6b1ed2fbc12bc3420d7d449dcead3118f6f414ce46015f7f291beaf5 for details.

Why didn't the ebuild update the conffile? Shouldn't it have seen conffile changed and triggered a 3 way merge?

superm1 picture superm1 on 30 Nov 2020

I have the same issue on Fedora 33, and fwupdmgr 1.5.2.

hferreiro picture hferreiro on 2 Dec 2020
👍2

I have the same issue as well on Arch, , and fwupdmgr 1.5.2.
Solved it by uninstalling then install the fwupd

elhossary picture elhossary on 2 Dec 2020
👍6 🎉2
Was this page helpful?
0 / 5 - 0 ratings

Related issues

fornellas picture fornellas  Β·  4Comments
switchwitch picture switchwitch  Β·  10Comments
FFY00 picture FFY00  Β·  11Comments
onavsaber picture onavsaber  Β·  8Comments
dupondje picture dupondje  Β·  4Comments