Bug#1061731: fwupd: Failed to load daemon: failed to load engine: Failed to load config: Key file does not have group “redfish”

[Richard B <rb-misc@posteo.net>]

    Hello.
    
    I can confirm that upgrading fwupd and libfwupd2 on Trixie to
    1.9.14-1 and installing the package maintainer's version of
    /etc/fwupd/fwupd.conf allowed the fwupd status to start:
    
> sudo apt upgrade
>       Reading package lists... Done
>       Building dependency tree... Done
>       Reading state information... Done
>       Calculating upgrade... Done
>       The following packages will be upgraded:
>         fwupd libfwupd2
>       2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>       Need to get 0 B/3,833 kB of archives.
>       After this operation, 54.3 kB of additional disk space will be
>       used.
>       Do you want to continue? [Y/n] y
>       Retrieving bug reports... Done
>       Parsing Found/Fixed information... Done
>       serious bugs of fwupd (1.9.11-1 → 1.9.14-1) <Outstanding>
>        b1 - #1061731 - fwupd: Failed to load daemon: failed to load
>       engine: Failed to load config: Key file does not have group
>       “redfish”
>       Summary:
>        fwupd(1 bug)
>       Are you sure you want to install/upgrade the above packages?
>       [Y/n/?/...] y
>       Reading changelogs... Done
>       ...
>       Configuration file '/etc/fwupd/fwupd.conf'
>        ==> Modified (by you or by a script) since installation.
>        ==> Package distributor has shipped an updated version.
>          What would you like to do about it ?  Your options are:
>           Y or I  : install the package maintainer's version
>           N or O  : keep your currently-installed version
>             D     : show the differences between the versions
>             Z     : start a shell to examine the situation
>        The default action is to keep your current version.
>       *** fwupd.conf (Y/I/N/O/D/Z) [default=N] ? y
>       Installing new version of config file /etc/fwupd/fwupd.conf ...
>       fwupd-offline-update.service is a disabled or a static unit not
>       running, not starting it.
>       fwupd-refresh.service is a disabled or a static unit not running,
>       not starting it.
>       fwupd.service is a disabled or a static unit not running, not
>       starting it.
>       Processing triggers for libc-bin (2.37-15) ...
>       Processing triggers for man-db (2.12.0-3) ...
>       Processing triggers for dbus (1.14.10-4) ...
>       Processing triggers for hicolor-icon-theme (0.17-2) ...
>       
>       systemctl status fwupd
>       ○ fwupd.service - Firmware update daemon
>            Loaded: loaded (/usr/lib/systemd/system/fwupd.service;
>       static)
>            Active: inactive (dead)
>              Docs: https://fwupd.org/
>       
>       sudo systemctl start fwupd
>       
>       systemctl status fwupd
>       ● fwupd.service - Firmware update daemon
>            Loaded: loaded (/usr/lib/systemd/system/fwupd.service;
>       static)
>            Active: active (running) since Thu 2024-03-07 16:37:27 CST;
>       3s ago
>              Docs: https://fwupd.org/
>          Main PID: 22184 (fwupd)
>             Tasks: 7 (limit: 18110)
>            Memory: 23.7M (peak: 108.7M)
>               CPU: 988ms
>            CGroup: /system.slice/fwupd.service
>                    └─22184 /usr/libexec/fwupd/fwupd
>       
>     
    I kept fwupd at 1.9.11-1 since this bug was reported, but the new
    version seems to be in the clear.
    
    Best.
    
    Richard