This bug was fixed in the package fwupd - 1.7.9-1~20.04.1
---------------
fwupd (1.7.9-1~20.04.1) focal; urgency=medium
* New upstream release, and drop all patches since they are merged.
* Properly fall back to use DMI instead of /sys/class/dmi interface.
(LP: #1982103)
* Build depends on mondemmanager 1.8 and libxmlb 0.3.6 to support
EM120/160. (LP: #1980334)
* Don't stderr-fail the autopkgtest on modprobe error as they are
optional. (LP: #1966364)
* Run fwupd-refresh under a dedicated fwupd-refresh user. This is
fixed in 1.1.7, so it's automatically included. (LP: #1969976)
-- Yuan-Chen Cheng <yc.ch...@canonical.com> Sun, 03 Jul 2022 03:18:51
+0000
** Changed in: fwupd (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: fwupd (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1969976
Title:
DynamicUser=1 doesn't get along with services that need dbus-daemon
Status in Fwupd:
Fix Released
Status in OEM Priority Project:
Fix Committed
Status in systemd:
New
Status in fwupd package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Won't Fix
Status in fwupd source package in Focal:
Fix Released
Status in systemd source package in Focal:
Won't Fix
Status in fwupd source package in Impish:
Won't Fix
Status in systemd source package in Impish:
Won't Fix
Status in fwupd source package in Jammy:
Fix Released
Status in systemd source package in Jammy:
Won't Fix
Bug description:
Updating to systemd 245.4-4ubuntu3.16 has caused a regression in
Ubuntu 20.04, that fwupd-refresh.service always fails to run.
This has been root caused down to the changes in
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538
Unfortunately this is an upstream issue introduced by stable systemd.
https://github.com/systemd/systemd/issues/22737
The problem also occurs in Ubuntu 22.04 with a newer systemd release.
As discussed in
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/comments/61
it's a tradeoff of issues. So within Ubuntu something probably needs to be
done about fwupd-refresh.service.
One proposal is to remove DynamicUser=yes from the systemd unit, but
this will mean fwupdgmr refresh runs as root. It's relatively
sandboxed by other security mechanisms, but still not ideal. Could we
repurpose any other service account? Or alternatively we can make a
new fwupd service account that this systemd unit uses.
To manage notifications about this bug go to:
https://bugs.launchpad.net/fwupd/+bug/1969976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
