When trying to run fwupdmgr, it hangs. journalctl: Nov 12 12:07:55 lap dbus-daemon[433]: [system] Activating via systemd: service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.104' (uid=0 pid=38477 comm="fwupdmgr refresh> Nov 12 12:07:55 lap systemd[1]: Starting Firmware update daemon... Nov 12 12:07:55 lap fwupd[38487]: Failed to load daemon: syscall filtering is configured but not working Nov 12 12:07:55 lap systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Nov 12 12:07:55 lap systemd[1]: fwupd.service: Failed with result 'exit-code'. Nov 12 12:07:55 lap systemd[1]: Failed to start Firmware update daemon. Nov 12 12:08:20 lap dbus-daemon[433]: [system] Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) This is on a systemd gentoo. fwupd was emerged with [ebuild R ] sys-apps/fwupd-2.0.1::gentoo USE="amdgpu archive bash-completion cbor gnutls lzma nvme policykit spi systemd uefi -amt -bluetooth (-elogind) -fastboot -flashrom -gtk-doc -introspection -logitech -minimal -modemmanager -sqlite -synaptics -test -tpm" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11 -python3_13" 4855 KiB The same problem also existed in 1.9.x fwupd, but was definitely fixed in 1.9.20, see my comment 1 in bug 931500 and upstream bug https://github.com/fwupd/fwupd/issues/7144 However, the meson.build commit applied to fix 7144 is present in the current gentoo 2.0.1 build, so this is most likely "same error message, but different reason".
Downgraded to 1.9.24, this one works fine.
See also https://github.com/fwupd/fwupd/issues/8078
Unfortunately, I haven't been able to reproduce this on any of my devices. Did you restart the fwupd service before running fwupdmgr? Does fwupdtool work?
Given that error message comes from the daemon, that was a dumb question. Could you please attach `emerge --info`?
Created attachment 908818 [details] emerge --info
Created attachment 908819 [details] Kernel .config Kernel .config is from 6.11.8, fwupd error was with 6.11.6 or 7, but I didn't change the config since then.
(In reply to John M. Harris, Jr. from comment #3) > Unfortunately, I haven't been able to reproduce this on any of my devices. > > Did you restart the fwupd service before running fwupdmgr? Does fwupdtool > work? I will re-emerge 2.0.1 und test fwupdtool tomorrow.
Did some testing with 2.0.1: 1.) The fwupd daemon is auto-started by systemd on demand, not when booting: As soon as I invoke fwupdmgr on the command line, the error message mentioned above appears in the syslog. Nothing about fwupd in the syslog before that. 2.) fwupdtool works without problems, at least for the commands refresh and get-updates. 3.) fwupdmgr refresh and get-updates also work without problems after I manually start /usr/libexec/fwupd/fwupd in another terminal as root before invoking fwupdmgr. And /usr/libexec/fwupd/fwupd outputs only expected warnings to its terminal, nothing related to syscall filtering. This could indicate that something is wrong with Gentoo's fwupd.service?
Created attachment 908890 [details] fwupd.service as installed by emerge on my Gentoo system
