[Bug 1943833] Re: fwupd failed to update metadata for lvfs

Mario Limonciello 1943833 at bugs.launchpad.net
Tue Jan 18 15:18:27 UTC 2022


Yeah; perhaps there is actually multiple bugs here.

One of them is definitely in the engine, using libjcat 0.1.3 or later (at compile time) will change daemon behavior:
https://github.com/fwupd/fwupd/blob/d7b682430efb8f0718306579f64ed4bda423b4a0/src/fu-engine.c#L3963
It needs this commit to be able to verify the timestamp properly: https://github.com/hughsie/libjcat/commit/6fa790b2f458557cbf0c5caf573a9d377ce4bd44

So the engine has been built against 0.1.3 in the most recent release in
Ubuntu focal: https://launchpadlibrarian.net/549854359/buildlog_ubuntu-
focal-amd64.fwupd_1.5.11-0ubuntu1~20.04.2_BUILDING.txt.gz

libjcat 0.1.4 fixes some ABI problems introduced by 0.1.3.  I however
don't find a reason to believe compiling against it (vs runtime) will
fix this issue.

I looked at KDE discover source code (at least the latest version).
https://github.com/KDE/discover/blob/master/libdiscover/backends/FwupdBackend/FwupdBackend.cpp#L294

Looking at that I don't see any reason to think it's a problem in their
code.  They use the libfwupd client library for the update process, so
any problems should be contained into that library and it's interaction
with the daemon's engine.

That is both fwupdmgr and KDE discover use the exact same libfwupd for
the refreshing of metadata.

I think we should approach debugging this a different way.  YC can you
take the files from ~/.cache that fail and see if they fail in jcat-tool
as well?  If so, it should be easier to walk through why they're failing
with a debugger.

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

Title:
  fwupd failed to update metadata for lvfs

Status in OEM Priority Project:
  Incomplete
Status in fwupd package in Ubuntu:
  Invalid
Status in libjcat package in Ubuntu:
  Fix Released
Status in plasma-discover package in Ubuntu:
  New
Status in libjcat source package in Focal:
  Triaged
Status in libjcat source package in Hirsute:
  Triaged
Status in libjcat source package in Impish:
  Triaged
Status in fwupd source package in Jammy:
  Invalid
Status in libjcat source package in Jammy:
  Fix Released
Status in plasma-discover source package in Jammy:
  New

Bug description:
  When running `fwupdmgr refresh` from the command line or when
  performing an update from the Software application the following error
  will be thrown:

  Failed to update metadata for lvfs: checksum failure: failed to verify
  data, expected 98261db7124c8026fb88f77768787efc2f8355c3

  The cause is an outdated libjcat, as explained in the upstream bug
  report:
  https://github.com/fwupd/fwupd/issues/3652#issuecomment-912677175

  0.1.3 is included in Ubuntu but at least 0.1.4 of libjcat is required
  to function properly.

  Firmware can not be updated any longer as a result unless forcing the
  update manually by performing `fwupdmgr refresh --force`.

  This means the libjcat dependency of this package needs to be set to
  0.1.4 minimum and the libjcat package itself needs to be updated.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: fwupd 1.5.11-0ubuntu1~21.04.1
  ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Thu Sep 16 16:19:33 2021
  InstallationDate: Installed on 2019-09-12 (735 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: fwupd
  UpgradeStatus: Upgraded to hirsute on 2021-05-26 (112 days ago)
  modified.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: [modified]
  modified.conffile..etc.fwupd.remotes.d.lvfs.conf: [modified]
  mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 2021-03-25T16:21:42.746540
  mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2021-06-07T11:13:00.873724

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943833/+subscriptions




More information about the foundations-bugs mailing list