Thank you @ahasenack! ** Description changed:
This is *not* an issue in any one atomic version of fwupd, but rather an issue with the archive state at this moment caused by a combination of factors. Creating this bug to track these details. [Impact] - I have marked this as "Critical" since, for impacted users, fwupd.service is completely nonfunctional and fails to start due to a fwupd/libfwupd mismatch: + I have marked this as "Critical" on Noble since, for impacted users, + fwupd.service is completely nonfunctional and fails to start due to a + fwupd/libfwupd mismatch. I haven't set a priority for other releases + since it is unclear whether their phasing ever reached a point such that + their archive states are similarly impacted (and I'm not yet aware of + reports to that effect for those releases) + sudo systemctl status fwupd × fwupd.service - Firmware update daemon - Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static) - Active: failed (Result: exit-code) since Mon 2026-07-06 20:02:49 UTC; 2min 18s ago - Docs: https://fwupd.org/ - Process: 1938738 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) - Main PID: 1938738 (code=exited, status=1/FAILURE) - CPU: 29ms + Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static) + Active: failed (Result: exit-code) since Mon 2026-07-06 20:02:49 UTC; 2min 18s ago + Docs: https://fwupd.org/ + Process: 1938738 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) + Main PID: 1938738 (code=exited, status=1/FAILURE) + CPU: 29ms Jul 06 20:02:49 localhost systemd[1]: Starting fwupd.service - Firmware update daemon... Jul 06 20:02:49 localhost fwupd[1938738]: Failed to load daemon: failed to load engine: libfwupd version 1.9.34 does not match daemon 1.9.33 Jul 06 20:02:49 localhost systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Here is an example apt policy output from one impacted user's system: sudo apt policy fwupd libfwupd2 fwupd: - Installed: 1.9.33-0ubuntu1~24.04.1ubuntu1 - Candidate: 2.0.20-1ubuntu2~24.04.1 - Version table: - 2.0.20-1ubuntu2~24.04.1 500 (phased 0%) - 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages - *** 1.9.33-0ubuntu1~24.04.1ubuntu1 100 - 100 /var/lib/dpkg/status - 1.9.16-1 500 - 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages + Installed: 1.9.33-0ubuntu1~24.04.1ubuntu1 + Candidate: 2.0.20-1ubuntu2~24.04.1 + Version table: + 2.0.20-1ubuntu2~24.04.1 500 (phased 0%) + 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages + *** 1.9.33-0ubuntu1~24.04.1ubuntu1 100 + 100 /var/lib/dpkg/status + 1.9.16-1 500 + 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages libfwupd2: - Installed: 1.9.34-0ubuntu1~24.04.1 - Candidate: 1.9.34-0ubuntu1~24.04.1 - Version table: - *** 1.9.34-0ubuntu1~24.04.1 500 - 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages - 100 /var/lib/dpkg/status - 1.9.16-1 500 - 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages + Installed: 1.9.34-0ubuntu1~24.04.1 + Candidate: 1.9.34-0ubuntu1~24.04.1 + Version table: + *** 1.9.34-0ubuntu1~24.04.1 500 + 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages + 100 /var/lib/dpkg/status + 1.9.16-1 500 + 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages Incident details: 1. libfwupd2 became libfwupd3 in fwupd 2. 2. fwupd 2.0.20-1ubuntu2~24.04.1 was released to noble-updates[0], and the prior version was thus unpublished/superseded on 2026-06-08 ("Superseded on 2026-06-08 by fwupd - 2.0.20-1ubuntu2~24.04.1")[1] 3. 2026-06-11, phasing was set to 0% for fwupd[2] on noble-updates due to a couple identified regressions (detailed below). Thus, users who updated before this phasing was stopped should not be impacted by this issue, but many users who were behind on fwupd/libfwupd2 updates are impacted. 4. Users of fwupd < 1.9.34-0ubuntu1~24.04.1 trying to apt update/apt upgrade at some point between then and now were/are(?) still getting libfwupd2 1.9.34-0ubuntu1~24.04.1, which it seems is still published in noble-updates and is allowable by apt deps for fwupd <= 1.9.34-0ubuntu1~24.04.1, which only had a >= dep on libfwupd2. But, these users don't have any candidate version for fwupd since the only version currently published is phased at 0%. All of this will be resolved once that fwupd patch currently in proposed migrates, or if phasing on 2.0.20-1ubuntu2~24.04.1 is set to 100%, since new fwupd after that version has a strict dependency on libfwupd3's version number. [0] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/28 [1] https://launchpad.net/ubuntu/+source/fwupd/+publishinghistory [2] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/33 ** Description changed: This is *not* an issue in any one atomic version of fwupd, but rather an issue with the archive state at this moment caused by a combination of factors. Creating this bug to track these details. [Impact] I have marked this as "Critical" on Noble since, for impacted users, fwupd.service is completely nonfunctional and fails to start due to a fwupd/libfwupd mismatch. I haven't set a priority for other releases since it is unclear whether their phasing ever reached a point such that their archive states are similarly impacted (and I'm not yet aware of - reports to that effect for those releases) + reports to that effect for those releases). However, it is possible that + they are impacted as well. sudo systemctl status fwupd × fwupd.service - Firmware update daemon Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static) Active: failed (Result: exit-code) since Mon 2026-07-06 20:02:49 UTC; 2min 18s ago Docs: https://fwupd.org/ Process: 1938738 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) Main PID: 1938738 (code=exited, status=1/FAILURE) CPU: 29ms Jul 06 20:02:49 localhost systemd[1]: Starting fwupd.service - Firmware update daemon... Jul 06 20:02:49 localhost fwupd[1938738]: Failed to load daemon: failed to load engine: libfwupd version 1.9.34 does not match daemon 1.9.33 Jul 06 20:02:49 localhost systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Here is an example apt policy output from one impacted user's system: sudo apt policy fwupd libfwupd2 fwupd: Installed: 1.9.33-0ubuntu1~24.04.1ubuntu1 Candidate: 2.0.20-1ubuntu2~24.04.1 Version table: 2.0.20-1ubuntu2~24.04.1 500 (phased 0%) 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages *** 1.9.33-0ubuntu1~24.04.1ubuntu1 100 100 /var/lib/dpkg/status 1.9.16-1 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages libfwupd2: Installed: 1.9.34-0ubuntu1~24.04.1 Candidate: 1.9.34-0ubuntu1~24.04.1 Version table: *** 1.9.34-0ubuntu1~24.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages 100 /var/lib/dpkg/status 1.9.16-1 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages Incident details: 1. libfwupd2 became libfwupd3 in fwupd 2. 2. fwupd 2.0.20-1ubuntu2~24.04.1 was released to noble-updates[0], and the prior version was thus unpublished/superseded on 2026-06-08 ("Superseded on 2026-06-08 by fwupd - 2.0.20-1ubuntu2~24.04.1")[1] 3. 2026-06-11, phasing was set to 0% for fwupd[2] on noble-updates due to a couple identified regressions (detailed below). Thus, users who updated before this phasing was stopped should not be impacted by this issue, but many users who were behind on fwupd/libfwupd2 updates are impacted. 4. Users of fwupd < 1.9.34-0ubuntu1~24.04.1 trying to apt update/apt upgrade at some point between then and now were/are(?) still getting libfwupd2 1.9.34-0ubuntu1~24.04.1, which it seems is still published in noble-updates and is allowable by apt deps for fwupd <= 1.9.34-0ubuntu1~24.04.1, which only had a >= dep on libfwupd2. But, these users don't have any candidate version for fwupd since the only version currently published is phased at 0%. All of this will be resolved once that fwupd patch currently in proposed migrates, or if phasing on 2.0.20-1ubuntu2~24.04.1 is set to 100%, since new fwupd after that version has a strict dependency on libfwupd3's version number. [0] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/28 [1] https://launchpad.net/ubuntu/+source/fwupd/+publishinghistory [2] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/33 ** Description changed: This is *not* an issue in any one atomic version of fwupd, but rather an issue with the archive state at this moment caused by a combination of factors. Creating this bug to track these details. [Impact] I have marked this as "Critical" on Noble since, for impacted users, fwupd.service is completely nonfunctional and fails to start due to a fwupd/libfwupd mismatch. I haven't set a priority for other releases since it is unclear whether their phasing ever reached a point such that their archive states are similarly impacted (and I'm not yet aware of reports to that effect for those releases). However, it is possible that they are impacted as well. sudo systemctl status fwupd × fwupd.service - Firmware update daemon Loaded: loaded (/usr/lib/systemd/system/fwupd.service; static) Active: failed (Result: exit-code) since Mon 2026-07-06 20:02:49 UTC; 2min 18s ago Docs: https://fwupd.org/ Process: 1938738 ExecStart=/usr/libexec/fwupd/fwupd (code=exited, status=1/FAILURE) Main PID: 1938738 (code=exited, status=1/FAILURE) CPU: 29ms Jul 06 20:02:49 localhost systemd[1]: Starting fwupd.service - Firmware update daemon... Jul 06 20:02:49 localhost fwupd[1938738]: Failed to load daemon: failed to load engine: libfwupd version 1.9.34 does not match daemon 1.9.33 Jul 06 20:02:49 localhost systemd[1]: fwupd.service: Main process exited, code=exited, status=1/FAILURE Here is an example apt policy output from one impacted user's system: sudo apt policy fwupd libfwupd2 fwupd: Installed: 1.9.33-0ubuntu1~24.04.1ubuntu1 Candidate: 2.0.20-1ubuntu2~24.04.1 Version table: 2.0.20-1ubuntu2~24.04.1 500 (phased 0%) 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages *** 1.9.33-0ubuntu1~24.04.1ubuntu1 100 100 /var/lib/dpkg/status 1.9.16-1 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages libfwupd2: Installed: 1.9.34-0ubuntu1~24.04.1 Candidate: 1.9.34-0ubuntu1~24.04.1 Version table: *** 1.9.34-0ubuntu1~24.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports noble-updates/main arm64 Packages 100 /var/lib/dpkg/status 1.9.16-1 500 500 http://ports.ubuntu.com/ubuntu-ports noble/main arm64 Packages Incident details: 1. libfwupd2 became libfwupd3 in fwupd 2. 2. fwupd 2.0.20-1ubuntu2~24.04.1 was released to noble-updates[0], and the prior version was thus unpublished/superseded on 2026-06-08 ("Superseded on 2026-06-08 by fwupd - 2.0.20-1ubuntu2~24.04.1")[1] 3. 2026-06-11, phasing was set to 0% for fwupd[2] on noble-updates due to a couple identified regressions (detailed below). Thus, users who updated before this phasing was stopped should not be impacted by this issue, but many users who were behind on fwupd/libfwupd2 updates are impacted. 4. Users of fwupd < 1.9.34-0ubuntu1~24.04.1 trying to apt update/apt upgrade at some point between then and now were/are(?) still getting libfwupd2 1.9.34-0ubuntu1~24.04.1, which it seems is still published in noble-updates and is allowable by apt deps for fwupd <= 1.9.34-0ubuntu1~24.04.1, which only had a >= dep on libfwupd2. But, these users don't have any candidate version for fwupd since the only version currently published is phased at 0%. + [Fix] + All of this will be resolved once that fwupd patch currently in proposed migrates, or if phasing on 2.0.20-1ubuntu2~24.04.1 is set to 100%, since new fwupd after that version has a strict dependency on libfwupd3's version number. [0] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/28 [1] https://launchpad.net/ubuntu/+source/fwupd/+publishinghistory [2] https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2142578/comments/33 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2160164 Title: (archive state issue) Halted phased update to latest fwupd has introduced mismatched versions on some outdated systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2160164/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
