Bug 943319

Summary:	sys-apps/fwupd-2.0.1: Error "Failed to load daemon: syscall filtering is configured but not working" is back
Product:	Gentoo Linux	Reporter:	Klaus Kusche <klaus.kusche>
Component:	Current packages	Assignee:	John M. Harris, Jr. <johnmh>
Status:	UNCONFIRMED ---
Severity:	normal	CC:	klaus.kusche, proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=931500
Whiteboard:
Package list:		Runtime testing required:	---

Description Klaus Kusche 2024-11-12 11:24:06 UTC

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".

Comment 1 Klaus Kusche 2024-11-12 11:28:08 UTC

Downgraded to 1.9.24, this one works fine.