A minor problem with software updates

[Dwaff]

Today I’ve run into this, when checking for software updates:

• How to find out what is causing this?
• Where is a document describing what Software does behind the scenes when I hit the refresh button on the “updates” pane?

I can’t copy-paste text from this little baloon. Very annoying. Now I have to manually type “Failed to update metadata for lvfs: checksum failure” so that it can be searched for…

[Quarnero]

@Dwaff, please read about same problem within this thread:

@Quarnero

sudo fwupdmgr refresh

[Dwaff]

Thanks for the hint.

Just switching from ethernet to wifi “fixed” the problem. I still do not know what is going on, though. Remembernig a thousands of cookbook recipes for problems like this one is not a way to go for me.

[Quarnero]

Didn’t have time to investigate (or know how to do this) but somehow think that fwupd package is something available for the first time within PureOS Byzantium repo. IMO, very good direction and great progress that required (and still do) some expert handling and control from Purism Team side, or at least deserves some attention from users of PureOS. Thank you @jeremiah! Just preparation to get there was a lot of work, wasn’t it?

Few selected explanations here (beside another 53):

PluginFlag:legacy bios · fwupd/fwupd Wiki

LVFS Triaged Issue: AC power required · fwupd/fwupd Wiki

fwupd flatpak · fwupd/fwupd Wiki

And under same link address is written: “When compiled with firmware support, it will check for updates periodically and automatically download firmware in the background. After the firmware has been downloaded a popup will be displayed in GNOME Software to perform the update.”

sudo apt list fwupd
Listing… Done
fwupd/stable,now 1.5.7-4 amd64 [installed]

Short overview, all started here:

@henry-nicolas

Would this LVFS support be used for coreboot upgrades ? This seems like a good use case although I don’t know LVFS well enough to understand whether that’s possible or not…

fwupd was promised to happen and from now on available within current PureOS distro:

@jeremiah

I’ll be a bit more specific about upstream’s requirements; they want flashrom to be usable from a tool called fwupd (firmware update). flashrom is only one of the packages that Purism contributes too, we modify things like coreboot and heads as well, so there’s lots of development going on and refactoring to using things like libflashrom has been a lower prio. Hopefully I’ll put it on the front burner once a couple issues that I need to resolve are complete.

All while kindly and repeatedly insisted within LVFS main thread:

@rugk

It would make updating firmware so much more convenient

[Dwaff]

Having looked at the background (thanks for the initial hint, again), I have a vague idea of what is going on. Still I need to investigate why I got the checksum error when connected over the built in ethernet, and why it went away, when I unplugged the ethernet cable and enabled wifi via the kill switch. My hunch is that the firmware packages are only checked for actively used devices.