Jacopo Clark

I found the problem: This bug happens with `sdcc=4.5.0` but not with `sdcc=4.4.0`. I leave this issue here for reference. You may close it.

Same problem for me as well. (Temporarily) downgrading to `fwupd=1.9.25` did work, although of course I am hoping for a better solution. Coincidentally, I am also having this problem on...

> Someone is going to need to follow the steps in https://github.com/fwupd/fwupd/blob/main/data/meson.build#L151 -- it seems Arch specific for some reason. Even though starting the systemd service fails with the exact...

I just rebuild `fwupd` with `dynamic_options += ['SystemCallErrorNumber=SIGSYS']` and then started the `fwupd` daemon from the main branch and **it did not fail** and subsequently running `fwupdmgr get-updates` etc worked...

The working test (with those error messages) was with the fwupd daemon from the venv. The systemd service (installed through the package manager) did not work until I downgraded it.