Missing App Store (Discover/Bazaar) Fix - Update Propagation Time (bazzite-dx-nvidia-open:stable)

Bazzite
1

Hello Universal Blue Community,

I’m writing to inquire about the expected propagation time for a recent Bazzite update, specifically concerning the fix for the “Missing App Store (Discover/Bazaar)” issue.

I was one of the users affected by this bug and was advised that an update would resolve it. My current system details are:

  • Image: bazzite-dx-nvidia-open:stable
  • Current Version: 42.20250708.1

Based on what I’ve seen in the changelogs and community discussions, I believe the fixed version should be 42.20250709.1 (or a later stable equivalent if 0709.1 was a testing-only build that then rolled into a subsequent stable release). The changelog for testing-42.20250709 explicitly mentions “fix: don’t show discover search results (#2866)”, which aligns with the issue I’m experiencing.

It’s now been three days since I was told to expect the update, and my system still reports “no updates found” when checking via the GUI or running ujust update in the terminal.

While I understand that immutable OS updates involve image propagation and not just package updates, I’m trying to get a clearer understanding of the official expected timing.

My questions are:

  1. What is the typical official propagation window for a critical bug fix like the missing App Store, once a stable image (e.g., 42.20250709.1 or its successor) has been built and confirmed? Is there an expected range (e.g., hours, 1-2 days, longer)?
  2. Are there any known delays or specific reasons why this particular update (42.20250709.1) might be taking longer than usual to reach the stable channel for bazzite-dx-nvidia-open images?
  3. Are there any specific logs or commands beyond ujust update and rpm-ostree status that I can check to determine if my system is correctly reaching the update mirrors or if there’s a specific reason it’s not detecting the new image?

I’ve already confirmed I’m on the stable branch and have previously run the curl -sL https://fix.universal-blue.org/ | sudo bash script (relevant for installations before July 2nd, 2024), so I believe my system is correctly configured to receive updates generally.

Any official insight into the update rollout process and current status would be greatly appreciated.

Thank you for your time and for all the work on Bazzite!

2

I’ll let someone from bazzite know on what image version you’re supposed to be on.

I can answer the propagation time. Normally it kicks off in about 15 minutes after a Bazzite release, and a GDX build kicks off 15 minutes after that.

This is automated but we are still tweaking it and sometimes it doesn’t run. It’s just a matter of tweaking the renovate config we use across the project, which has led to much faster and automated builds in general but we still have places where it’s not set up perfectly yet.

This is one of the reasons the -dx images are still in Beta, we’ll have it sorted before we announce it as generally available.

EDIT: Sounds like the bazzite team has decided to do the builds manually. I’ll let them fill you in.

1 Like
3

Thank you for the quick and insightful response! That clarifies a lot.

It’s good to know that normally, propagation is almost immediate (15 minutes for Bazzite, then another 15 for GDX builds). This certainly helps set expectations for future updates.

I appreciate the transparency regarding the ongoing tweaks to the automated process and the -dx images being in Beta.

The EDIT: mentioning that “the bazzite team has decided to do the builds manually” for this particular instance is key. Could someone from the Bazzite team please provide an update on the expected timeline for the manual build of 42.20250709.1 (or the correct fixed version) to become available for bazzite-dx-nvidia-open:stable users? Understanding the manual process’s current status would be very helpful.

Thank you again for the ongoing support!