https://bugs.kde.org/show_bug.cgi?id=516861
--- Comment #7 from [email protected] --- Additional observation: The same first-attempt failure described in previous comments also occurs when using updatectl update directly from the CLI, not just via Discover. Pattern observed: - First run: aborts silently or exits early (consistent with the 30% / metadata-only behaviour seen in Discover) - Second run immediately afterwards: completes successfully This suggests the issue is in the backend (kde-linux-sysupdated) or the update state initialisation, rather than in Discover itself. Discover may simply be a more visible surface for the same underlying race condition. Environment: KDE Linux Alpha, KVM VM, updatectl v2 endpoint. -- You are receiving this mail because: You are watching all bug changes.
