I think Ublue is only set to automatically check for updates once per day. If there were only a few updates available, it's possible your system just didn't check yet that day.

See if your /etc/rpm-ostreed.conf has automatic updates set to "stage." I think that should be the default.

See update section in this FAQ, which tells you what config disables automatic updates.

One of the main features of silverblue is auto updates in the background. You don't need a cronjob or a graphical tool to achieve this, it's build into the distribution.

Have a look here: https://miabbott.github.io/2018/06/13/rpm-ostree-automatic-updates.html

You just have to change one entry in /etc/rpm-ostreed.conf and reload the systemd service.

Looks expected:

https://github.com/ublue-os/main/issues/191

Ublue uses OCI images, I don’t think Silverblue does. Last time I used Ublue even rpm-ostree couldn’t do “check” but it looks like upstream has fixed that at least.

Unfortunately I have no idea why your updates have stopped working.

As for having to run the upgrade command, have you considered using cronie to run the command on a schedule for you?

Here's a decent guide for it if you wanted to look into it as a bandaid fix.

More than like likely yes, although you shouldn't have to and this is not expected behavior. Same thing happened to me with Kinoite. Twice. I still got flatpak upgrades through Discover but no longer system upgrades, or the system upgrades would appear but error out. I just decided to not rebase anymore after the third reinstall and use toolbox for everything that didn't have a flatpak available.

I thiink, sudo systemctl enable NAME OF SERVICE

they have an automatic updater service, anyone knos the name?

Edit: other people already mentioned the rpm-ostree native way, which is better.

Btw, do you know how then to disable the update check / module in Discover? I find it weird to have it check always, and also to search for big GUI apps there is kinda not the purpose, although sometimes necessary