Discover (Software Center) Missing, Rollback Failed, Can't Install Flatpaks - Bazzite User Needs Help!

Bazzite
1

Hello Bazzite Community,

I’m in a really frustrating situation with my Bazzite (KDE Plasma) installation and I desperately need some help. I’m hoping someone here can offer a solution as I’m currently stuck.

The Problem:
After performing a system update via ujust update in the terminal, my Discover (Software Center) application completely disappeared. I can’t find it in the application launcher, and I have no graphical way to install or manage applications.

What I’ve Tried So Far (and what failed):

  1. Rebooting: Did this multiple times, no change.
  2. Attempting Rollback via GRUB:
    • I can access the GRUB menu and see older Bazzite versions under “Advanced options for Bazzite.”
    • However, when I select any of these older versions, the system attempts to boot but then gives an error (unfortunately, I don’t have the exact error message at hand, but it prevents the boot process) and eventually defaults back to the latest, problematic version. So, rollback is not working for me.
  3. Reinstalling Discover via Terminal (Flatpak):
    I tried the following commands, as advised, to reinstall Discover:
    flatpak remote-add --if-not-exists flathub [https://flathub.org/repo/flathub.flatpakrepo](https://flathub.org/repo/flathub.flatpakrepo)
flatpak update --appstream
flatpak install flathub org.kde.discover
    • The first command (remote-add) showed no output, which I understand is normal if Flathub was already present.
    • The second command (update --appstream) ran, showing download progress, so it seems to have completed.
    • However, the flatpak install flathub org.kde.discover command consistently fails with the error: Nothing matches org.kde.discover in remote flathub. This is the core issue preventing me from getting Discover back.
  4. Deep Cleaning Flatpak Cache: I also tried flatpak uninstall --unused, flatpak repair --user, and flatpak repair --system followed by flatpak update --appstream again, but the flatpak install command still gives the “Nothing matches…” error.
  5. Attempting to install GNOME Software Center: I tried flatpak install flathub org.gnome.Software as a last resort, but it fails with the same “Nothing matches…” error, suggesting a broader Flatpak issue.

My Current Situation & Why I Need Help:

  • I have no graphical software manager.
  • I cannot rollback to a previous working version.
  • I cannot install any Flatpak applications via terminal due to the “Nothing matches…” error.
  • I CANNOT reinstall Bazzite from scratch. I have critical data on my hard drive that I cannot easily back up or move at this moment, and I’m not in a position to perform a full system reinstall.
  • I’m currently stuck with a broken system for application management and feel completely locked out.

My Questions:

  1. What could be causing the “Nothing matches org.kde.discover in remote flathub” error, especially after updating --appstream and running repair commands?
  2. Given that rollback isn’t working and reinstalling isn’t an option, is there any advanced rpm-ostree or Flatpak command/tweak I can try from the terminal (perhaps from a Live USB, though I’d prefer not to chroot if possible) to fix this issue and get Discover back?
  3. Are there any specific logs I should check that might shed more light on why Flatpak can’t find these packages?

Any guidance or specific commands would be greatly appreciated. Thank you in advance for your time and help!

2

Bazaar should be in there which is the new GUI application store for flatpaks.

rpm-ostree status should show if you actually have an older image still available, there should be the previous one, then you can use rpm-ostree rollback command. But if its giving an error, we would need to know what the error actually is to help.

3

As mentioned, Discover has been replaced with Bazaar.

That didn’t work because Gnome Software isn’t available as a flatpak. You’d have to rpm-ostree install it with rpm-ostree install gnome-software.

As an alternative, you could browse flathub.org directly for apps. It then provide a command you can run to install the apps. But again, Bazzite now comes with a different GUI store called Bazaar, so this isn’t necessary.

4

Hello everyone,

Thank you for your continued patience and guidance. I’m providing a concise summary of the troubleshooting steps taken so far, especially in response to your suggestions, along with the persistent issues.

1. Current Bazzite Version:

  • My system is currently running on 42.20250712 (from July 12, 2025).
  • Crucially, the older, working ‘41’ versions are no longer available on my disk (not listed in rpm-ostree status -v). This means a direct rollback to a known good state is not possible.

2. Rollback Attempts:

  • I attempted sudo rpm-ostree rollback from the terminal. The command ran, but booting into the rolled-back version (the other ‘42’ image) still fails with an error on screen (unable to capture specific error due to GRUB unreliability).
  • GRUB itself is highly unreliable, appearing only occasionally during reboots, preventing reliable rollback attempts from there.

3. Discover / Bazaar (GUI App Stores):

  • Neither Discover nor Bazaar is found in my application launcher.
  • flatpak list | grep -i discover shows only Discover Overlay, not the main org.kde.discover application.

4. Core Problem: Flatpak Installation Failure (“Nothing matches…”):

  • Despite flatpak remote-add and flatpak update --appstream appearing to run, flatpak install flathub <any_app_id> (e.g., org.kde.discover, org.flathub.Bazaar) consistently fails with: error: Nothing matches <app_id> in remote flathub.
  • This indicates a fundamental issue preventing my system from seeing/accessing Flatpak applications from Flathub.
  • I encountered “Unknown option” errors with some flatpak commands I was attempting (e.g., --force-collection-update, --user-only/--system-only for flatpak search), which added to the troubleshooting difficulty.

5. Diagnostic Data Provided (in previous posts):

  • Full rpm-ostree status -v output.
  • flatpak remotes -d output.
  • flatpak search discover output (shows no results for org.kde.discover).
  • Relevant journalctl logs (grep -iE 'error|fail|warn|bug|flatpak|ostree|dnf|rpm' and grep -i flatpak).

In summary: I am stuck on a Bazzite 42 version where Flatpak app installation is completely broken, I have no graphical software center, and I cannot rollback to a working version. The issue seems to be a deeper problem with Flatpak’s ability to communicate with Flathub.

I’m eagerly awaiting further guidance on how to fix this underlying Flatpak issue. Thank you for your continued support.

5

I’ve gathered additional flatpak output as requested, which clarifies the situation:

1. Flatpak Apps/Runtimes Are Installed and Working:

  • My flatpak list output shows numerous Flatpak applications (e.g., Firefox, Telegram, Krita, Heroic Games Launcher) and runtimes (various org.freedesktop.Platform, org.gnome.Platform, org.kde.Platform versions) are present and presumably functional. This confirms Flatpak itself is not entirely broken.

2. Core Issue: “Nothing matches…” remains for new installations:

  • The fundamental problem persists: flatpak install flathub <any_app_id> (e.g., org.kde.discover, org.flathub.Bazaar) consistently fails with error: Nothing matches <app_id> in remote flathub.
  • This indicates that while installed Flatpaks work, my system cannot find or access application metadata from the Flathub remote to install new apps.

3. Flathub Remote Configuration (looks normal):

  • flatpak remotes shows flathub system.
  • flatpak remotes -d output confirms the correct URL:
    Name    Title   URL                         Collection ID Subset Filter Priority Options … … Homepage Icon
flathub Flathub [https://dl.flathub.org/repo/](https://dl.flathub.org/repo/) -

4. No GUI App Store:

  • Neither Discover nor Bazaar is found in my app launcher, confirming org.kde.discover and org.flathub.Bazaar are not installed.

In summary: Installed Flatpak apps work, but I’m completely unable to install new Flatpaks due to the “Nothing matches…” error. This points to an issue with how my system’s Flatpak is querying or updating its understanding of the Flathub repository’s contents.

Given that my 41 deployments are unavailable and GRUB rollbacks are unreliable, solving this Flatpak metadata issue is critical. Any specific commands to re-initialize Flatpak’s appstream data or diagnose this “Nothing matches” error would be greatly appreciated.

6

You can’t rollback from fedora 42 base to fedora 41 so that is anyways out of the question.

Bazaar is not a flatpak it should be in the image as a native package.

7

In fact, I don’t understand why it doesn’t work. By continuing to run tests to fix the problem, I noticed that Flatpack works, except for the graphical apps for selecting software.
It’s not a huge problem, but I’d like to avoid doing everything from the terminal. Moreover, I’d miss out on the ability to explore new apps to try out, because without having them right in front of me, I wouldn’t have the incentive to try new ones.

8

That’s completely expected. Discover is not available as a flatpak, only as an rpm. Bazaar also isn’t available as a flatpak, though one is planned for the future.