Can't rebase back to Bazzite 39 because of GPG issue
I am having a problem with black screen after login in Bazzite 40. I was told to rebase to 39 with the following command:
rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39. I did so but I got the following GPG error I don't know how to resolve:
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39 (digest: sha256:fe357496bb5ac67edd223e8cf27ed8d29384eb6948a082b98c265ec8a9d9ac90)
ostree chunk layers already present: 65
custom layers already present: 3
Checking out tree 07112c1... done
Inactive requests:
plasma-workspace-x11 (already provided by plasma-workspace-x11-5.27.11-1.fc39.x86_64)
Enabled rpm-md repositories: copr:copr.fedorainfracloud.org:matte-schwartz:sunshine copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager copr:copr.fedorainfracloud.org:rok:cdemu fedora-cisco-openh264 updates fedora rpmfusion-free-updates-testing rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates-testing rpmfusion-nonfree-updates rpmfusion-nonfree google-chrome copr:copr.fedorainfracloud.org:codifryed:CoolerControl updates-archive
Updating metadata for 'copr:copr.fedorainfracloud.org:matte-schwartz:sunshine'... done
Updating metadata for 'copr:copr.fedorainfracloud.org:rodoma92:kde-cdemu-manager'... done
Updating metadata for 'copr:copr.fedorainfracloud.org:rok:cdemu'... done
Updating metadata for 'fedora-cisco-openh264'... done
Updating metadata for 'updates'... done
Updating metadata for 'rpmfusion-free-updates-testing'... done
error: Updating rpm-md repo 'rpmfusion-free-updates-testing': Failed to download gpg key for repo 'rpmfusion-free-updates-testing': Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39]Solution:Jump to solution
I had same issue (note there's another question with my solution below):
cd /etc/pki/rpm-gpg
sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-2020 RPM-GPG-KEY-rpmfusion-nonfree-fedora-39...
16 Replies
Solution
I had same issue (note there's another question with my solution below):
cd /etc/pki/rpm-gpg
sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-2020 RPM-GPG-KEY-rpmfusion-nonfree-fedora-39
Thanks! This worked.
Actually it is not working again. Somehow I rebased to Aurora 40 which is not working for me. I wanted to go back to Aurora 39 and I get the following error: "sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-2020 RPM-GPG-KEY-rpmfusion-nonfree-fedora-39 1 (12.769s) < 12:23:59
ln: failed to create symbolic link 'RPM-GPG-KEY-rpmfusion-nonfree-fedora-39': File exists"
And then "error: Updating rpm-md repo 'rpmfusion-free-updates-testing': Failed to download gpg key for repo 'rpmfusion-free-updates-testing': Curl error (37): Couldn't read a file:// file for file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39 [Couldn't open file /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-39]"
Here is the symbolic link in /etc/pki/rpm-gpg:
what are the permissions on the linked to file?
lrwxrwxrwx@
not sure they should all be world r/w. Can you open the target file in VI/less? Have you tried deleting and recreating the link?
I can delete the link ("sudo rm RPM-GPG-KEY-rpmfusion-nonfree-fedora-39") and recreate it ("sudo ln -s RPM-GPG-KEY-rpmfusion-nonfree-fedora-2020 RPM-GPG-KEY-rpmfusion-nonfree-fedora-39"), but I get the same failure.
Are you able to open the file it links TO? like in vi or nano or just cat it?
I'm having this problem as well
Trying the solution marked by @missalexis of symlinking the file didn't work
rpm-ostree reset and then running rebase again did work for me, however. I've swapped between :stable and :39 quite a few times, FWIWSame, been trying for hours last night.
Did you try ostree reset? I only had two layers so nbd for me, but it definitely worked to fix it
I will try it later when I get home
I gave up. It didn't work. I install a 4Tb SSD and reinstalled everything from scratch.
For Aurora, we just disabled all of the RPM Fusion repos on the image. Hopefully that stops this GPG error. Bazzite should also be doing this as well (unsure if only in testing or in main)
Do you know anyone in particular in the bazzite maintainers group we mention this to?
Kyle has done the same thing.