Gnome Software not working in Fedora Silverblue 36 with “Your operating system is no longer supported...” message

Hi. I have seen this issue reported elsewhere but no clear solution. The window is empty and reports: “Your operating system is no longer supported…” No repos available either. Any ideas how to fix this? I suppose this issue does not affect updating from the command prompt, right? Thanks in advance

4 Likes

I have the same problem.

There is a discussion here:
https://github.com/fedora-silverblue/issue-tracker/issues/257

3 Likes

I saw the “Unsupported operating system” message in gnome-software-42. The non-existent repositories and empty software categories showed in the gnome-software-42.1 update. I think they’re separate issues.

3 Likes

I am having this same issue.

GNOME Software shows this:

hey @passthejoe - is this issue consistent? I was just able to refresh the metadata from that updates-archive repo without issue. If the problem is consistent what happens if you try to update via the CLI?

sudo rpm-ostree rebase fedora/36/x86_64/silverblue
3 Likes

I was already on Silverblue 36 Beta, so I was just trying to do a normal rpm-ostree upgrade.

It’s working now. Thanks for the fix!

I am now on:

Fedora Linux 36.20220511.0 (Silverblue)

I’m on that version too and I’m having the same problem:

The software app is unusable. What can I do? :confused:

1 Like

The GNOME Software application appears to have lost its repository configuration. I recall, from the fedora 36 release notes, that package configuration has moved from /var to /lib and I wonder if it’s related to that. The problem seemed to arise with gnome-software-42.1.

Until the problem is fixed you can update your flatpaks with “flatpak update” and your OS image and layered packages with “sudo rpm-ostree upgrade” in a terminal.

1 Like

I did my rpm-ostree upgrade in the terminal, and that went fine, but my GNOME Software is not working, just like the others in this thread:

I have the same issue. Just rebased from 35 to 36, and got this window:

1 Like

I just rebooted and got that exact same error too. Is there some issue or thread where to track progress of this? Not being able to add/remove/update software (graphically) is not nice :frowning_face:

1 Like

I get the same error… I’m kinda new to silverblue so I was thinking I’ve done something wrong but it seems to be broken everywere…

I guess It will be fixed soon… Until then just uptade with rpm-ostree upgrade and flatpak update and well installation are also in CLI I guess until there is a fix.


1 Like

I’ve found a temporary “workaround”:
sudo chmod 757 /var/cache/rpm-ostree/solv/

This gives everyone write access to this directory, whereas it used to be limited to root. Do this at your own discretion and accept the possible risks that comes with that.

This looks to be the best place to track it for now: 2083715 – [Silverblue] cannot create temporary file: /var/cache/rpm-ostree/solv/fedora-cisco-openh264.solv.XuN0fQ

Edit: Note that rpm-ostree upgrade command is unaffected. So if you want to, you can use the command line to manage your system instead of the GUI in the meantime.

4 Likes

Thanks for the bug report link. Now we can follow along as this gets fixed.

Thanks. There it also explains the workaround we can apply as this gets fixed:

rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2022-7a894b6507
systemctl reboot
2 Likes

Thanks for the tip. But as you warned, perhaps is better to keep using the command prompt for the time being and keep security in place.

Yep, I can confirm this command works. It downgraded the offending library and now all seems back to normal, after a reboot of course.

The fix has been moved to stable:

https://bodhi.fedoraproject.org/updates/FEDORA-2022-af207692d6

To get it, just do a regular rpm-ostree update in the terminal:

$ rpm-ostree update
$ systemctl reboot

When the system rebooted, my GNOME Software was working.

I think I need to wait a little bit. Just did an update and the issue remains. :slightly_frowning_face:
Perhaps I did something wrong. This is the output I get, either using rpm-ostree update or rpm-ostree upgrade:

rpm-ostree upgrade
2 metadata, 0 content objects fetched; 788 B transferred in 2 seconds; 0 bytes content written
Inactive base replacements:
  dnf-4.11.1-1.fc36.noarch
  dnf-automatic-4.11.1-1.fc36.noarch
  dnf-data-4.11.1-1.fc36.noarch
  dnf-plugins-core-4.1.0-1.fc36.noarch
  dnf-utils-4.1.0-1.fc36.noarch
  libdnf-debuginfo-0.66.0-1.fc36.x86_64
  libdnf-debugsource-0.66.0-1.fc36.x86_64
  libdnf-devel-0.66.0-1.fc36.x86_64
  microdnf-3.8.1-1.fc36.x86_64
  microdnf-debuginfo-3.8.1-1.fc36.x86_64
  microdnf-debugsource-3.8.1-1.fc36.x86_64
  python3-dnf-4.11.1-1.fc36.noarch
  python3-dnf-plugin-kickstart-4.0.16-1.fc36.noarch
  python3-dnf-plugin-leaves-4.1.0-1.fc36.noarch
  python3-dnf-plugin-local-4.1.0-1.fc36.noarch
  python3-dnf-plugin-modulesync-4.1.0-1.fc36.noarch
  python3-dnf-plugin-post-transaction-actions-4.1.0-1.fc36.noarch
  python3-dnf-plugin-rpmconf-4.0.16-1.fc36.noarch
  python3-dnf-plugin-show-leaves-4.1.0-1.fc36.noarch
  python3-dnf-plugin-showvars-4.0.16-1.fc36.noarch
  python3-dnf-plugin-snapper-4.0.16-1.fc36.noarch
  python3-dnf-plugin-system-upgrade-4.0.16-1.fc36.noarch
  python3-dnf-plugin-torproxy-4.0.16-1.fc36.noarch
  python3-dnf-plugin-tracer-4.0.16-1.fc36.noarch
  python3-dnf-plugin-versionlock-4.1.0-1.fc36.noarch
  python3-dnf-plugins-core-4.1.0-1.fc36.noarch
  python3-dnf-plugins-extras-common-4.0.16-1.fc36.noarch
  python3-hawkey-0.66.0-1.fc36.x86_64
  python3-hawkey-debuginfo-0.66.0-1.fc36.x86_64
  python3-libdnf-0.66.0-1.fc36.x86_64
  python3-libdnf-debuginfo-0.66.0-1.fc36.x86_64
  yum-4.11.1-1.fc36.noarch
Inactive requests:
  fedora-workstation-repositories (already provided by fedora-workstation-repositories-35-3.fc36.noarch)
Checking out tree 37a0304... done
Enabled rpm-md repositories: fedora-cisco-openh264 fedora-modular updates-modular updates fedora rpmfusion-free-updates-testing rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree updates-testing updates-archive
⠁ Updating metadata for 'fedora-cisco-openh264'   0% [░░░░░░░░░░░░░░░░░░░░] (0s)⠙ Updating metadata for 'fedora-cisco-openh264'  95% [███████████████████░] (0s)⠚ Updating metadata for 'fedora-cisco-openh264' 100% [████████████████████] (0s)Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'fedora-modular'... done
Updating metadata for 'updates-modular'... done
Updating metadata for 'updates'... done
Updating metadata for 'fedora'... done
⠁ Updating metadata for 'rpmfusion-free-updates-testing'   0% [░░░░░░░░░░░░░░░░░⠙ Updating metadata for 'rpmfusion-free-updates-testing'  95% [█████████████████⠚ Updating metadata for 'rpmfusion-free-updates-testing' 100% [█████████████████Updating metadata for 'rpmfusion-free-updates-testing'... done
Updating metadata for 'rpmfusion-free'... done
⠁ Updating metadata for 'rpmfusion-nonfree-updates-testing'   0% [░░░░░░░░░░░░░░⠙ Updating metadata for 'rpmfusion-nonfree-updates-testing'  95% [██████████████⠚ Updating metadata for 'rpmfusion-nonfree-updates-testing' 100% [██████████████Updating metadata for 'rpmfusion-nonfree-updates-testing'... done
Updating metadata for 'rpmfusion-nonfree'... done
Updating metadata for 'updates-testing'... done
Updating metadata for 'updates-archive'... done
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264'; generated: 2022-04-07T16:52:38Z solvables: 4
rpm-md repo 'fedora-modular'; generated: 2022-05-04T21:12:01Z solvables: 825
rpm-md repo 'updates-modular'; generated: 2022-05-08T01:14:17Z solvables: 862
rpm-md repo 'updates'; generated: 2022-05-13T01:50:57Z solvables: 7930
rpm-md repo 'fedora'; generated: 2022-05-04T21:16:11Z solvables: 67992
rpm-md repo 'rpmfusion-free-updates-testing'; generated: 2022-05-13T10:08:26Z solvables: 12
rpm-md repo 'rpmfusion-free'; generated: 2022-05-04T04:48:11Z solvables: 506
rpm-md repo 'rpmfusion-nonfree-updates-testing'; generated: 2022-05-13T10:33:46Z solvables: 3
rpm-md repo 'rpmfusion-nonfree'; generated: 2022-05-04T05:11:55Z solvables: 225
rpm-md repo 'updates-testing'; generated: 2022-05-14T02:04:01Z solvables: 15678
rpm-md repo 'updates-archive'; generated: 2022-05-14T03:31:43Z solvables: 7681
Resolving dependencies... done
No upgrade available

Not sure if this is related, but now GNOME Software is working again, but this update of the RPMFusion repos persists. Updating via GNOME Software doesn’t apply it, and it doesn’t show when doing rpm-ostree update: