linux-firmware issue

[Bret Busby]

On 14/9/25 01:42, Little Girl wrote:
> Hey there,
> 
> After the issue of the linux-firmware update timing out and failing
> for many of us the other day, I was finally able to install the
> linux-firmware update last Sunday.
> 
> Updates have worked smoothly since then until two nights ago. Now,
> whenever I check for updates with the Discover GUI (I'm using
> Kubuntu), I get this temporary pop-up as a caution or warning at the
> bottom of the window, regardless of whether there are any updates or
> not, with XXX representing the hash that it displays.
> 
> Failed to update metadata for lvfs: checksum failure: failed to
> verify data, expected XXX
> 
> Note that this doesn't prevent me from being able to grab any
> available updates.
> 
> Tge sudo apt update command and the sudo apt full-upgrade command are
> run regularly on this machine and don't solve the issue.
> 
> The apt policy linux-firmware command shows that I've got the
> available candidate installed.
> 
> The fwupdmgr refresh command and the fwupdmgr --force refresh command
> produce the same cautionary output when run with or without sudo.
> 
> The fwupdmgr update command produces this result, with XXX
> representing the device ID when run with or without sudo:
> 
> Devices with no available firmware updates:
>   • XXX
> No updatable devices
> 
> Someone in IRC suggested looking at the
> /etc/fwupd/remotes.d/lvfs.conf file and doing either or both of these
> things:
> 
> Remove this line if you have it:
> keyring=gpg
> 
> Replace gz with zst in this line, if you have it:
> MetadataURI=https://cdn.fwupd.org/downloads/firmware.xml.gz
> 
> I didn't have the keyring line and I changed the Metadata line.
> Despite that change, the output remains the same, even after a reboot.
> 
> Someone else on IRC suggested that the cause for the pop-up is
> intermittent IME, that some "old  commands" may not work any more,
> and that this is a question for the #kubuntu-devel IRC channel. I
> tried asking about it in that channel that yesterday and today and
> got no response after several hours.
> 
> I'm hoping that someone in here can tell me whether this is at my end
> or the server's end and whether it requires either my or the server
> folks' attention or can be safely ignored.
> 

Hello.

I am wondering whether, rather than the problem being with the 
linux-firmware upgrade, the problem may lie with your update manager.

I am running Linux Mint Mate 21.3, which is based on Ubuntu 22.04, and, 
uses the Ubuntu 22.04 repositories, and, I have not encountered the 
problem that you describe.

I have, as part of Linux Mint Mate, the Linux Mint Update Manager, and, 
it seems to be working okay, without any problems shown.

The name for the Update manager package that I have, is mintUpdate v 6.0.9 .

So, I wonder whether the problem that you have been encountering, lies 
with the update manager, rather than with the linux-firmware upgrade.

I expect that, if the problem lies with the linux-firmware upgrade, that 
all users would likely be experiencing it, but, as I am apparently using 
a different update manager to you, and, am not experiencing the problem, 
I wonder whether that is where the problem lies.

Another possibility, relates to the version number of your OS.

In your message above, you did not include which version of Kubuntu, you 
are running.

As I said, the Ubuntu repositories that my OS uses, are for Ubuntu 22.04 .

So, the question arises, as to which version of Kubuntu, you are using.

..
Bret Busby
Armadale
West Australia
(UTC+0800)
..............