Stuck On 41, rpmfusion-nonfree-nvidia-driver failed to download gpg key Error

Bazzite
1

Evening all,

I got stuck on Bazzite 41 a while back and am just now getting back to this again.

Error when I try to update is below.

ujust update

── 21:26:57 - System update ────────────────────────────────────────────────────
Pulling manifest: ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
Checking out tree 2de7827... done
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:ilyaz:LACT copr:copr.fedorainfracloud.org:matte-schwartz:sunshine copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager copr:copr.fedorainfracloud.org:rodoma92:rmlint copr:copr.fedorainfracloud.org:rok:cdemu fedora-cisco-openh264 updates fedora copr:copr.fedorainfracloud.org:phracek:PyCharm google-chrome rpmfusion-nonfree-nvidia-driver rpmfusion-nonfree-steam copr:copr.fedorainfracloud.org:codifryed:CoolerControl updates-archive
Updating metadata for 'rpmfusion-nonfree-nvidia-driver'... done
error: Updating rpm-md repo 'rpmfusion-nonfree-nvidia-driver': Failed to download gpg key for repo 'rpmfusion-nonfree-nvidia-driver': Curl error (37): Could not read a file:// file for file:///usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-nonfree-fedora-42 [Couldn't open file /usr/share/distribution-gpg-keys/rpmfusion/RPM-GPG-KEY-rpmfusion-nonfree-fedora-42]
System update failed: 
   0: Command failed: `/usr/bin/rpm-ostree upgrade`
   1: `/usr/bin/rpm-ostree` failed: exit status: 1

Location:
   src/steps/os/linux.rs:228
Retry? (y)es/(N)o/(s)hell/(q)uit

OSTree Status

$ rpm-ostree status
State: idle
Deployments:
● ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:d016756dcb02570f7ed39c2bf636e8a31cdee1319ccdeca84ceb977ae6909665
                  Version: 41.20241125 (2024-11-26T03:44:46Z)
          LayeredPackages: ckb-next gnome-boxes java-1.8.0-openjdk.x86_64 java-17-openjdk java-latest-openjdk.x86_64 virt-manager

  ostree-unverified-registry:ghcr.io/ublue-os/bazzite-gnome:stable
                   Digest: sha256:d016756dcb02570f7ed39c2bf636e8a31cdee1319ccdeca84ceb977ae6909665
                  Version: 41.20241125 (2024-11-26T03:44:46Z)
          LayeredPackages: ckb-next coolercontrol gnome-boxes java-1.8.0-openjdk.x86_64 java-17-openjdk java-latest-openjdk.x86_64 virt-manager

  fedora:fedora/41/x86_64/silverblue
                  Version: 41.1.4 (2024-10-24T13:24:56Z)
                   Commit: 308868a0660c0231a0c039896647a5db43f1a258cd211890ce83b06953384c4c
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1
                   Pinned: yes

I am not using a nvidia card so I have tried removing the driver, updating the driver, checked for dependencies, etc and am still as stuck as I was back in November of last year.

Any thoughts on where to go from here?

2

You layered a bunch of packages you shouldn’t have.

rpm-ostree reset will remove all your layers, reevaluate your usage of java on the host Frequently Asked Questions - Bazzite Documentation

  • use containers for development, don’t layer them
  • gnome boxes and virt manager are flatpaks + work fine with the preinstalled system qemu.

then you rpm-ostree update

3

Ok, I reset the ostree and am now on 42 but now when I try to install a rpm package via the bazarr or command line, I get a checksum error from flatpak. If I used flathub it seems to work.

Do you have a recommendation for the proper way of installing/running Java? I need it to run Tunerstudio. I had it working before but without Java on the system anymore its borked.

Thanks

4

This should explain how to install different types of packages.

5

Yeah, I got that, I am asking what y’all recommend as the best practice here.

I.E. is there a preference for a particular method specific to Java?

Since I am redoing it, I want to do it properly. If it doesn’t matter which option I use that is also fine. I just don’t want to have to reset stuff again later.

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.