Arch Linux

mcloaked

Member

From: Yorkshire, UK

Registered: 2012-02-02

Posts: 1,240

[SOLVED] fwupd version 1.9.17-1 is brioken

After updating fwupd today to 1.9.17-1 it fails to work.  Running the command:

$ fwupdmgr get-devices
Failed to connect to daemon: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.fwupd': startup job failed

Clearly fails.  And also the systemd unit fails to start:

$ sudo systemctl status fwupd | cat
× fwupd.service - Firmware update daemon
Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static)
Active: failed (Result: exit-code) since Mon 2024-04-22 21:58:50 BST; 2min 31s ago
Docs: https://fwupd.org/
Process: 12646 ExecStart=/usr/lib/fwupd/fwupd (code=exited, status=1/FAILURE)
Main PID: 12646 (code=exited, status=1/FAILURE)
CPU: 34ms

Apr 22 21:58:50 ryzen1 systemd[1]: Starting Firmware update daemon...
Apr 22 21:58:50 ryzen1 fwupd[12646]: Failed to load daemon: syscall filtering is configured but not working
Apr 22 21:58:50 ryzen1 systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE
Apr 22 21:58:50 ryzen1 systemd[1]: fwupd.service: Failed with result 'exit-code'.
Apr 22 21:58:50 ryztheen1 systemd[1]: Failed to start Firmware update daemon.

Downgrading solves the problem:

# pacman -U fwupd-1.9.16-1-x86_64.pkg.tar.zst
loading packages...
warning: downgrading package fwupd (1.9.17-1 => 1.9.16-1)
resolving dependencies...
looking for conflicting packages...

Now if I restart the systemd fwupd unit, it starts up fine, and then the fwupdmgr get=updates works fine again.  So version 1.9.17-1 is broken.

Edit: The bug is reported at https://gitlab.archlinux.org/archlinux/ … -/issues/1

Last edited by mcloaked (2024-04-23 06:44:47)

---

Mike C

Scimmia

Fellow

Registered: 2012-09-01

Posts: 11,612

Re: [SOLVED] fwupd version 1.9.17-1 is brioken

Right. https://github.com/fwupd/fwupd/issues/7144

mcloaked

Member

From: Yorkshire, UK

Registered: 2012-02-02

Posts: 1,240

Re: [SOLVED] fwupd version 1.9.17-1 is brioken

Thanks - and yes it is fixed in 1.9.17-2

---

Mike C