I’m wondering if anyone has gotten the Auto Update feature for Kinoite F42 working? I installed the F42 beta in a fresh VM, and wanted to see how this feature was going to work.
I can see the following has been set in the new config file:
However, I haven’t witnessed the system actually applying the updates automatically. Is there a timer? Does the “Update Frequency” in Software Update settings affect how often it attempts to update?
On my actual machine (F41), I am also currently utilizing the rpm-ostree automatic service. I also have a script that runs at login to automatically update my flatpaks.
In the details of the change for F42, it states that it “will enable background updates by default in new installations and existing installations”.
Since it seems that it will somehow affect my existing F41 install when I upgrade to F42, I was testing this in a VM to understand the behavior. I didn’t want my existing setup to conflict/interfere, or be redundant, with the new system upon upgrading. I’m assuming when upgrading to F42 I should revert to commenting out “AutomaticUpdatePolicy” in /etc/rpm-ostreed.conf, not run my flatpak update script, and let Discover handle it all.
However, so far I cannot tell that this auto update via Discover feature is working at all.
Yes, good point. I assumed that this is in regards to just notifications to reboot, as described: “After a week without a reboot, they will be offered to reboot to apply system updates.”
But I’ve changed this value to “60”, just to test, and it still appears to not affect anything in regards to triggering an update.
I just changed it to test. Like I said, I don’t think that setting is actually indicating the interval for trying an update. I think it’s just the interval for the system to show the user a “Reboot Now” notification.
As I understand it, any automatic update that includes packages that would require a reboot will notify the user immediately. Updates that do not require the reboot will wait for the scheduled notification timed from the last reboot.
Updates that require a reboot include things like kernel, drivers, libraries, etc.
Right, but this change is specific to Kinoite, which is an atomic system, so all updates (except flatpaks) require a reboot to take effect.
The page states, "The user will only be notified to reboot their system once the updates have been applied and once a given amount of time has passed before the last time an update was applied. "
It should be configured to update everything automatically if a week pasted since the last update.
You might have to restart the Plasma Discover Notifier that triggers the auto update if you set a short time for the check for it to take effect:
/usr/libexec/DiscoverNotifier --replace
Make sure that you also don’t have another config set in ~/.config/PlasmaDiscoverUpdates.
It’s been a while since I last tested that and a lot of things changed in Discover so it might not work exactly as expected and testing is welcomed indeed.
It appears that auto update in Discover might be bugged and not working at all. Currently it appears that auto updates should begin after 1 minute of idle time. However, I can confirm in my VM that even after >1min of idle, it does not begin the upgrade process.
This commit seems to have replaced the command in notifier/UnattendedUpdates.cpp from plasma-discover-update --offline to plasma-discover --headless-update.
The latter command option doesn’t exist: discover: Unknown option 'headless-update'
I think this is what may be what is breaking it? I’ve added this to the KDE bug report as well.
Edit: Seems this change was merged only 1 week ago and is targeted for Plasma 6.4.
