Kinoite Showing OS/App Upgrades in Discover

TL;dr on Kinoite, it looks like system images aren’t updating automatically. Do I use Discover to install updates or ignore Discover entirely?

The docs mention that updates will be automatically download and applied/installed in the background. But, as of today, I see the same 11 updates in Discover as I did five days ago. The only difference is the OS image (instead of updating to 20260929, it’s 20261003).

The 11 upgrades are a mix; there’s one OS image, a bunch of libraries/Mesa related things, Firefox, Fedora Platform, and some Fedora KDE thing.

I thought the PC will automatically download/install and prompt me with “hey reboot now to upgrade.” Instead, it just seems to accumulate things in Discover until I download/install. I use that PC once a week for about two hours, with high-speed internet and it running pretty much the entire time.

If I run rpm-ostree status, I see a base install entry (44.1 I think) and a versioned one (20260919 I think). That one, I installed manually through Discover.

I am almost certain, the automatic update on Discover is once a week but you can configure it from the apps settings to daily if you prefer that.

Does that mean I have to upgrade through Discover once a week? Or that if I keep refreshing it, eventually I’ll see the upgrades disappear because they’re being auto-installed in the background?

I’m not entirely sure how it works on Discover as I primarilly use Gnome Software/Silverblue but if it’s setup the same then you don’t really need to do anything. It’ll just do it in the background.

However, I’m sure by default Discover is setup to automatically update weekly.

You may need to check System Settings → Software Update and modify if needed.

Yep, already checked. It was set to automatic and weekly.

@boniboyblue I’ll wait a few more days/weeks and see, it sounds like it should auto update. Thank you for clarifying!

Keep in mind there’s an issue where flatpak apps are not auto-updated, only the system :

Thanks, didn’t know about this. Should I reply to it and add “me too” or something? Last update was four months ago …

No need to notify everyone by sending a message. The issue is already known and has been reproduced. It will be fixed when someone will have time.

However you can add your mail to the CC list to be notified when progress is made on this issue.

Interestingly, my machine (Discover 6.7.5) eventually installed the Flatpak upgrades by itself! But not the OS image. I think it’s because I left it on for several hours unattended.

Forgot to mention: I think I got OS upgrades finally configured properly. I used AI to diagnose and fix, so I’m not 100% clear on the details. This app (prototype of mine) helped tremendously: Coder77 / auto-upgrade-status · GitLab

My main takeaway is Auto-upgrade is not enabled by default, and this is by design. AI poked through some of the KDE Plasma code and other code to figure it out.

To fix this:

  • Edit /etc/rpm-ostreed.conf. There should be a [Daemon] section with AutomaticUpdatePolicy=none. Change it to stage, which means “download and set up, and install after reboot.” You can alternatively specify apply, which automatically reboots after installating and setting everything up.
  • Restart the rpm-ostreed service: sudo systemctl restart rpm-ostreed.service so that it picks up your new config.
  • Enable the timer that checks for and/or runs auto updates: sudo systemctl enable --now rpm-ostreed-automatic.timer

To check that everything’s correct, verify that this returns “stage” which is the value we specified earlier: gdbus introspect --system --dest org.projectatomic.rpmostree1 --object-path /org/projectatomic/rpmostree1/Sysroot --only-properties | grep -i Automatic or busctl get-property org.projectatomic.rpmostree1 /org/projectatomic/rpmostree1/Sysroot org.projectatomic.rpmostree1.Sysroot AutomaticUpdatePolicy

And … theoretically, you should get OS updates installed automatically, and hopefully a notification to reboot and update. I’m still waiting on this, so …

I see from the KDE bug ticket that this one has a fix scheduled for Plasma 6.8.