Bazzite doesn’t notify about updates anymore

I did some digging and found two pointers, but no fix for the problem yet.

First is this post about Kinoite - they are talking about Discover of course, which we don’t have anymore. Makes me wonder if this is related to the problem. Anyway, I get the same result. Entering journalctl -f -u rpm-ostreed does not show any update checks being done.

The second was this post on the Answer Overflow, but it’s about F41 and the issue seems to have been fixed? I’m not knowledgeable enough to understand this in full.

So something is definitely off and I doubt that OP and me are the only ones having that issue, since it’s easy to miss. I’d appreciate any help on this. Missing updates for the browser for example isn’t great.

Ok, typical case of overcomplicated thinking. Bottom line is: Bazaar simply doesn’t notify about available updates, correct? Well, that’s not good.

Someone asked on Discord 3 weeks ago, and there was no response.

Bazzite doesn’t use rpm-ostreed for auto-updates, it uses custom updaters from ublue. It used to use ublue-update (which was just a wrapper around topgrade; the ujust update script still uses topgrade), but has changed to uupd which has been written specifically for Ublue OSes. Maybe the uupd timer didn’t get automatically enabled after ublue-update was removed?

You can use ujust to turn it on and off with ujust _toggle-updates or by checking the uupd.timer systemd unit manually (use systemctl status uupd.timer to check and systemctl enable --now uupd.timer to enable it if it is disabled).

So for me the updates are enabled and the uupd.timer appears enabled as well (got 4 hours and 15 mins left apparently).

I had wondered what would happen to the update notifications now that we have Bazaar, and I guess what happens is that we don’t have notifications?

Well, uupd should update the base system, brew, system and user flatpaks, and rootful and user distroboxes. Bazaar won’t give update notifications, but the flatpaks should just be updated in the background.

Not everybody does unattended updates for several reasons. Not having a notification for flatpaks anymore is a regression.

3 Likes

It’s also disconcerting if something stops working as you might not realise it was an update.

I remember seeing a user on Reddit saying he thought he broke Bazzite because Discover suddenly stopped working and wasn’t sure how, so I told him they had just switched to Bazaar and directed him here to follow updates to the distro.

Another funny one was seeing a post on YouTube yesterday talking about how Cachy introduced LatencyFlex finally! And people saying, “I’ll wait until Bazzite does it” while it’s been installed in Bazzite for a while now.

Now we get silent updates. This distro needs more communication within the OS itself, not less, alas :frowning:

It has some really cool features (like installing mesa-git without touching your system drivers), but given that Linux newbies are more likely to use this disrro, we also need to make them known within the OS in the way that newbies expect to get told. Maybe have a launcher pop up with a news feed, even if it just embeds the announcement page or the GitHub read me.

If I knew how to do it, I would 100% try and contribute to adding that feature, unfortunately it might take me some time to get there as I only just know how to add some software via their OCI template. And that’s incidentally how I find out about some new features, because I often look at their code, most people won’t do that.

1 Like

I’m also having the same issue about not receiving notifications for updates.

1 Like

I’m also have the same problem. My system crashed last night during shutdown and I remembered I hadn’t seen any notifications for updates in some time - when I restarted (after a prolonged ‘preparing system’ boot screen) and manually checked for updates, there was 1.6GB worth