Mario Limonciello

> I can check, when a new release arrives in Arch. I can't compile and swap such a low-level system component (not enough knowledge). You can add those changes to...

Just to confirm when you tested you tested with daemon launched from the systemd unit, not from the venv, right?

The venv in this case won't let you debug it unfortunately. I would add those to the systemd unit of the packaged version to debug it.

@Sean-StarLabs should the flashrom plugin check for this and inhibit updates or avoid probing in this case perhaps?

> Probing is fine (it's onyl write ops that wont work), but I think the ideal would to check and throw some form of warning/info as to why it's inhibited....

I think for now as a workaround you can add the flashrom plugin into `DisabledPlugins`. See [documentation](https://fwupd.github.io/libfwupdplugin/fwupd.conf.html#daemon-parameters) for guidance on how to do this.

Yeah dependencies.xml in contrib/ci needs updates for aarch64 deps.

### Thanks for your commit The fwupd project has had a style change starting with fwupd 1.6.x. The style is summarized in https://github.com/fwupd/fwupd/blob/main/CONTRIBUTING.md and it appears your current pull request...

Hmm I wonder if this would be better done just merging "snapd support" directly into the uefi-dbx plugin. Otherwise it's a lot of callbacks for something isn't very common to...

> I had a variant like this early on. It wasn't too pretty 😄. For reference, it's in a branch: https://github.com/fwupd/fwupd/compare/main...bboozzoo:fwupd:bboozzoo/snapd-dbx-observer please have a look. TBH I don't think it...