micke
(Micke)
July 14, 2026, 7:11pm
1
I’m seeing the same issue on three Fedora CoreOS 44 (latest stable (44.20260621.3.1)) servers.
fwupd-refresh.timer runs every hour, but fwupd-refresh.service fails consistently.
I’ve ruled out a few obvious things:
Fwupd-DEBUG: emitting ::status-changed() [waiting-for-auth]
fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
If I then run:
sudo fwupdmgr refresh
it succeeds, updates the metadata files, and afterwards fwupd-refresh.service starts successfully again.
This makes me suspect a polkit/authorization issue rather than a systemd sandboxing problem.
I also found what looks like a related upstream discussion:
main ← superm1/refresh-remote
öppnad 04:12AM - 13 Jun 26 UTC
Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139344
Type of pul… l request:
- [ ] New plugin (Please include [new plugin checklist](https://github.com/fwupd/fwupd/wiki/New-plugin-checklist))
- [x] Code fix
- [ ] Feature
- [ ] Documentation
Has anyone else seen this on FCOS 44, or is there already a Fedora bug tracking it?
l-c-g
(Lars)
July 14, 2026, 7:24pm
2
I see it also failing:
Jul 11 19:15:48 fwupdmgr[558698]: Updating lvfs
Jul 11 19:15:48 systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE
Jul 11 19:15:48 systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'.
Jul 11 19:15:48 systemd[1]: Failed to start fwupd-refresh.service - Refresh fwupd metadata and update motd.
Since this is on a vserver, where I cannot update the firmware anyway, I decided to just wait and see if it is fixed in the next update
tlbueno
(Tiago Bueno)
July 15, 2026, 6:05pm
4
rapneset
(Rolv Apneseth)
July 15, 2026, 6:16pm
5
Yes, apologies, this issue made it through next. We have fwupd pinned in testing-devel now but that hasn’t made it to next / testing yet. A fix was also merged upstream so hopefully we don’t need to keep that pin for long either.
It’s safe to ignore the failure anyway, or even disable that timer, since currently fwupd does not work on CoreOS anyway.
micke
(Micke)
July 15, 2026, 6:25pm
6
Thanks for quick response. I’ll be disabling the timer on my machines.