https://bugs.kde.org/show_bug.cgi?id=523258
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from [email protected] --- Confirming the same issue on Fedora 44 Kinoite, custom bootc image based on quay.io/fedora/fedora-kinoite:44-nvidia. Henri's explanation matches what I found. The refresh itself succeeds, Discover just surfaces the second, rate limited download attempt as a user facing error even though the first attempt already completed. I can confirm the "it actually succeeds" part. Running fwupdmgr refresh --force by hand immediately after seeing the error dialog succeeds cleanly and downloads new metadata, and fwupdmgr get-updates then correctly enumerates all devices with accurate status. Nothing about the fwupd side is actually broken. I also see the identical error string in Discover's own background check log, immediately followed by normal continued processing rather than any real failure: > Fwupd Error 21 Failed to download metadata for lvfs: attempted previous > download of https://cdn.fwupd.org/downloads/firmware.xml.zst.jcat from just > 753ms ago That timing (753ms, and in an earlier occurrence I tested of 237ms) is well inside the 1500ms FWUPD_CLIENT_DOWNLOAD_URI_DELTA window linked, which supports his theory that Discover is requesting the same .jcat twice in quick succession rather than fwupd actually failing to reach the server. $ kinfo Operating System: Fedora Linux 44 KDE Plasma Version: 6.7.4 KDE Frameworks Version: 6.29.0 Qt Version: 6.11.1 Kernel Version: 7.1.12-200.fc44.x86_64 (64-bit) Graphics Platform: Wayland $ rpm -q fwupd plasma-discover fwupd-2.1.7-1.fc44 plasma-discover-6.7.4-1.fc44 Easy to reproduce on demand here by simply closing and reopening Discover a few times in a row, since each launch's background update check triggers its own metadata refresh attempt. -- You are receiving this mail because: You are watching all bug changes.
