SUMMARY We should update different resources at different frequencies. Flatpaks should be updated daily, "silently", in the background with an extra low priority for network and disk io. On Kinoite, system updates should behave pretty much the same but with a different frequency. If not on metered connection, not on battery and auto updates enabled, discover should prepare everything in the background and then notify only when user action is required: restarting apps or rebooting > sometimes I feel that way about Fedora TBH. When I see the notification I feel compelled to go and apply those updates just to make the notifier go away from my system tray Exactly my feeling. I don't want to be bothered every time I open my session by something that will distract me from what I wanted to do on the computer Even notifying for reboot is not ideal. In the best case, we would change the sleep button to suggest poweroff when there are updates to apply. Or have an apply updates and shutdown button Thus no notification at all in the best case. Only notify if there is an issue we can not automatically fix or wait a bit for it to be resolved. STEPS TO REPRODUCE N/A OBSERVED RESULT N/A EXPECTED RESULT NA SOFTWARE/OS VERSIONS Linux/KDE Plasma: ADDITIONAL INFORMATION N/A
In my opinion Flatpaks should be updated as the user prefers for other updates, automatic or manual. Or some options could be added for each type of packages, system, Flatpak, Snap and AppImage in the future. I normally prefer to update them manually as I don't work to have anything broken during the work days and also I don't want to do it over mobile connections with limited traffic data.
I think we're talking about defaults; every one of these should be configurable too. See also Bug 416193, Bug 413053, and Bug 436927
With automatic updates, isn't this the way it already works? That's what the tooltip for the Automatic Updates option in System Settings > Updates, says, at least. So either this is already implemented or else that tooltip is wrong!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
This is missing one important element: different auto-update cadence for different backends. Right now, I can not set my Flatpaks to auto-update daily and my system to auto-update weekly. It's all or nothing.
Confirming so the bot calms down.
While discussing it a
Sorry for the partial comment :/. While discussing this at Akademy, we also thought about splitting the system updates from the rest. Instead of having a per-backend setting, it would be a setting for system updates (that are generally larger and often require a reboot), and another one for the rest, which are generally smaller and do not require a reboot (flatpaks, snaps, etc.). The auto updater could then ask the backend if they are a system one or not and trigger auto-updates as needed.