Bug 509814

Summary: Notifier Service and underlying OSTree backend continously retries updates.
Product: [Applications] Discover Reporter: kb01
Component: rpm-ostree BackendAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: normal CC: aleixpol, mariamfahmy66, travier
Priority: NOR    
Version First Reported In: 6.4.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description kb01 2025-09-23 05:17:39 UTC
SUMMARY
Hi all,
I’m experiencing an issue where Plasma Discover keeps spamming me with update notifications, even though the underlying rpm-ostree update fails due to dependency conflicts. These dependency conflicts are not the bug I'm reporting. It's the continuous retry spam.

STEPS TO REPRODUCE
1. Enable Automatic Updates for Discover in Fedora Kinoite
2. Introduce a dependency conflict
3.  Wait for Discover to try to update with the dependency conflict

OBSERVED RESULT
Sep 19 18:13:02 fedora plasma-discover[7002]: org.kde.plasma.libdiscover.backend.rpm-ostree: rpm-ostree "(error): Could not depsolve transaction; 1 problem detected: ...
Sep 19 18:52:48 fedora rpm-ostree[7073]: Txn Upgrade on /org/projectatomic/rpmostree1/fedora failed: Could not depsolve transaction; 1 problem detected: ... 

This happens continuously—every half minute Discover tries to start a transaction, fails, and triggers a notification again. I’m aware that the update itself is failing due to mesa-vdpau-drivers-freeworld dependency issues, but the problem here is the notification spam, not the failed update.

EXPECTED RESULT
The expected behaviour would be for Discover to only try every few to several hours later, rather than continously (I’ve gotten 330 notifications in the background just while writing this).

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
This happens immediately on the update failing, it seems to immediately retry the update instead of timing out leading to a ridiculous amount of notification spam very quickly.