https://bugs.kde.org/show_bug.cgi?id=521682
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #73 from [email protected] --- I have a deterministic reproducer for the fwupd-related variant of this bug on Fedora 44 / Plasma Discover 6.7.4. Environment: * Fedora 44 * Plasma / Discover 6.7.4 * fwupd 2.1.7 * Discover has these backends: fwupd, flatpak, packagekit, kns * No Snap backend is present The issue can be reproduced without actually installing any updates: 1. Start Discover normally and leave the same instance running. 2. Run: sudo systemctl stop fwupd.service 3. In the already-running Discover instance, refresh/check for updates. Discover then reports: The name is not activatable and the journal contains: plasma-discover: Fwupd Error 10 The name is not activatable I originally encountered this naturally after installing system updates. The timing in the journal was: 11:27:43 fwupd.service: Deactivated successfully. 11:27:56 PackageKit: update-packages transaction ... finished with success 11:27:56 plasma-discover: Fwupd Error 10 The name is not activatable 11:27:56 plasma-discover: Fwupd Error 10 The name is not activatable fwupd itself was not upgraded during that transaction. Importantly, fwupd D-Bus activation itself works correctly: sudo systemctl stop fwupd.service fwupdmgr get-devices `fwupdmgr get-devices` successfully starts fwupd again, and `fwupd.service` immediately becomes active. Starting a fresh Discover instance with only the fwupd backend also works: plasma-discover --backends fwupd-backend So the failure appears specifically when fwupd disappears after a Discover instance has already initialized its fwupd backend. This seems consistent with the StandardBackendUpdater invalidation/state issue described in comment 61: a backend becomes invalid while Discover remains alive, and Discover does not correctly recover/reinitialize its updater state. A temporary workaround is increasing fwupd's IdleTimeout so that fwupd does not disappear during a Discover session, but Discover should ideally tolerate the D-Bus service disappearing and becoming activatable again. The `systemctl stop fwupd` sequence may also provide a simple deterministic way to reproduce this condition for an automated regression test. -- You are receiving this mail because: You are watching all bug changes.
