From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 435221FF178 for ; Mon, 29 Dec 2025 14:38:49 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 29B871B071; Mon, 29 Dec 2025 14:39:54 +0100 (CET) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Date: Mon, 29 Dec 2025 14:39:19 +0100 Message-ID: <20251229133920.40752-2-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20251229133920.40752-1-m.sandoval@proxmox.com> References: <20251229133920.40752-1-m.sandoval@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1767015534402 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.092 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH docs 2/2] firmware-updates: add group header to fwupd.conf X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" After creating a new config file, either as daemon.conf or fwupd.conf with the same contents as the example prior to this commit, the following error will be seen when starting fwupd.service: Failed to load daemon: failed to load engine: Failed to load config: failed to load /etc/fwupd/fwupd.conf: Key file does not start with a group Since there are potentially multiple groups, adding this at the end of the file might result in the key added to the wrong group. The file is also not present by default, so creating it without the header will also lead to issues. On the other hand, adding the group multiple times is not an issue. Please see `man 5 fwupd.conf` for more details. Signed-off-by: Maximiliano Sandoval --- firmware-updates.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/firmware-updates.adoc b/firmware-updates.adoc index 9ca4b6e..b9ca47e 100644 --- a/firmware-updates.adoc +++ b/firmware-updates.adoc @@ -57,6 +57,7 @@ mount point of the EFI partition in `/etc/fwupd/fwupd.conf`, for example: .File `/etc/fwupd/fwupd.conf` ---- +[fwupd] # Override the location used for the EFI system partition (ESP) path. EspLocation=/boot/efi ---- -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel