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

2024-03-07 Thread Richard B

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) 
 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

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

2024-01-31 Thread Michel Casabona

Hi,

It seems that the bug is fixed upstream

https://github.com/fwupd/fwupd/pull/6735



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

2024-01-31 Thread Laurent Bigonville
On Mon, 29 Jan 2024 10:47:50 +0100 Laurent Bigonville  
wrote:

>
> Hello,
>
> It seems that fwupd is not starting anymore on my machine.
>
> In the logs I can see:
>
> jan 29 10:40:28 eriador systemd[1]: Starting fwupd.service - Firmware
> update daemon...
> jan 29 10:40:28 eriador fwupd[13042]: Failed to load daemon: failed to
> load engine: Failed to load config: Key file does not have group 
“redfish”

> jan 29 10:40:28 eriador systemd[1]: fwupd.service: Main process exited,
> code=exited, status=1/FAILURE
> jan 29 10:40:28 eriador systemd[1]: fwupd.service: Failed with result
> 'exit-code'.
> jan 29 10:40:28 eriador systemd[1]: Failed to start fwupd.service -
> Firmware update daemon.
>

I've no idea what happened, but the configuration file was changed (I 
didn't do these changes):


$ sudo diff -u fwupd/fwupd.conf /etc/fwupd/fwupd.conf
--- fwupd/fwupd.conf    2024-01-24 10:15:36.0 +0100
+++ /etc/fwupd/fwupd.conf    2023-07-13 11:36:11.244229063 +0200
@@ -1,5 +1,20 @@
-# use `man 5 fwupd.conf` for documentation
 [fwupd]
 DisabledPlugins=test;test_ble
 OnlyTrusted=true
 AllowEmulation=false
+DisabledPlugins=test;test_ble
+IgnorePower=false
+OnlyTrusted=true
+AllowEmulation=false
+
+[msr]
+MinimumSmeKernelVersion=5.18.0
+
+[redfish]
+
+[thunderbolt]
+MinimumKernelVersion=4.13.0
+DelayedActivation=false
+RetimerOfflineMode=false
+
+[uefi_capsule]



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

2024-01-30 Thread Sébastien Dinot
Hi guys,

I fixed the issue on my system by commenting out the title of the two
empty sections in /etc/fwupd/fwupd.conf:

#[redfish]
...
#[uefi_capsule]

Then, of course, you need to start the daemon:

$ sudo systemctl start fwupd

Sébastien

-- 
Sébastien Dinot, sebastien.di...@free.fr
http://www.palabritudes.net/
Ne goutez pas au logiciel libre, vous ne pourriez plus vous en passer !



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

2024-01-30 Thread Paul Mabileau
Hi,

I faced this issue as well. It seems to me that the problem comes from the 
fact that the updated global configuration or parsing thereof under `/etc/
fwupd/fwupd.conf` is invalid because some sections are empty, potentially 
making them just as absent from the parsing's perspective.

Another workaround, potentially more lightweight, is therefore to either add 
at least one benign configuration key and value in the `redfish` and 
`uefi_capsule` sections taken from the man page or the `*.conf.old` files of 
the 
same name, or to simply remove them entirely.

Cheers,
Paul.



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

2024-01-29 Thread Laurent Bigonville

Package: fwupd
Version: 1.9.12-1
Severity: serious

Hello,

It seems that fwupd is not starting anymore on my machine.

In the logs I can see:

jan 29 10:40:28 eriador systemd[1]: Starting fwupd.service - Firmware 
update daemon...
jan 29 10:40:28 eriador fwupd[13042]: Failed to load daemon: failed to 
load engine: Failed to load config: Key file does not have group “redfish”
jan 29 10:40:28 eriador systemd[1]: fwupd.service: Main process exited, 
code=exited, status=1/FAILURE
jan 29 10:40:28 eriador systemd[1]: fwupd.service: Failed with result 
'exit-code'.
jan 29 10:40:28 eriador systemd[1]: Failed to start fwupd.service - 
Firmware update daemon.


Kind regards,

Laurent Bigonville