configs-scripts VS fwupd

You can't combine them, and if you try, you're almost certainly going to have a bad time. But on a BTRFS file system, you can deduplicate all the data between them. I run that script on my own setup, and the space savings from so doing are significant.

Prefix deduplication has massive space savings potential. I made a script that you can run periodically that handles running duperemove on installed Proton versions and the compatdata folder for BTRFS filesystems: vacuum-steamplay

I also dislike the spacious padding that GTK tends to use. I have tweaks that I use for GTK3 gtk.css that make the UI more compact. We can almost certainly still do that here, we just need to sit down with the Adwaita demo and the GTK inspector and just start poking and tweaking.

The only way to change the UI density is with xdg-config/gtk-{3,4}.0/gtk.css. You can use @import to split the changes across multiple files. Here is what I use to slim down GTK3. You also need this tweak for the headerbar height to not be decided by an invisible "sizing box".

UEFI firmware can not be updated in legacy BIOS modeSee https://github.com/fwupd/fwupd/wiki/PluginFlag:legacy-bios for more information.Use fwupdmgr --help for help

A similar bug, but featuring a different file and checksum, from today.

The more user-friendly distros have support for updating the UEFI secure boot dbx (forbidden binaries) database via fwupd, but due to the circumstances around this update, they currently don't/don't do it correctly. MS isn't doing it automatically themselves yet either so we're not any worse off. There's an open issue around handling this. I suspect it'll take a couple of months before this to-be-written support finds its way into distros. It's complex, annoying and the result of it going wrong is a system that can't boot Windows and can't boot from preexisting Windows recovery media. Distros will want to be very careful with it. I suspect they'll roll it out in stages with single-boot systems getting patched first and possibly interactive user confirmation.

Use fwupd

These updates are coming from fwupd and LVFS. The frontend is Gnome Software. Lenovo is pushing their firmware updates to LVFS, so you're updating with vendor code. Its a lot like getting device drivers and what-not through Windows Update.

More here u/CornFlakes1991 please report the issue

-> # fwupdmgr update WARNING: UEFI ESP partition not detected or configured See https://github.com/fwupd/fwupd/wiki/PluginFlag:esp-not-found for more information. Devices with no available firmware updates: • USB3.0 Hub • Samsung SSD 860 EVO 250GB • USB2.0 Hub • Unifying Receiver Devices with the latest available firmware version: • SKHynix • UEFI dbx

Related issue: https://github.com/fwupd/fwupd/issues/5477

Would be good to put some pressure on them to use this.