-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install rpm-fusion packages due to missing gpg key #708
Comments
Almost forgot to add explictly, but I'm running the
I know the base images are strictly not recommended, but I am really uninterested in the other tweaks that are done in Bluefin and the likes (even though they are fantastic projects, not discounting that!). |
You'll want to use qemu instead, virtualbox modules won't work here. For other things you need from rpmfusion, use distrobox. |
We strongly recommend qemu over virtualbox. That said if it is absolutely a requirement, you can install the kmod as part of a custom image. Since you are using a base image, I'm assuming that you have quite a few things layered already. Moving to a custom image would allow you to have those be apart of the image directly. |
That would be wrong, I didn't have anything layered. I actually have the output of One of the biggest reasons I went to Fedora in the first place is because I honestly prefer to run stock GNOME, I like the out of the box experience from Fedora and I would not know what I'd need to layer at this point. As IDE I develop in GNOME Builder, and have a Pycharm install in a container for non-GNOME projects (the Flatpak is too unreliable for me). Otherwise I've got everything as Flatpak actually, with CLI tools in distrobox.
I strongly prefer qemu over VirtualBox myself as well, apart from being more reliable if it was only to avoid Oracle this would be a plus. In this particular case however, I've got a course that explictly uses VirtualBox images as containers for some reasons, where we then should ssh into. I tried to get away with converting the image to qcow2 and work from there, but I also have a job to do and would just like to be able to follow the instructions as is. As far as I understood, VirtualBox relies on dkms modules, which don't work with Silverblue (and by extension ublue) in the first place. Otherwise I'm happy layering them if needed. For now, I simply installed Workstation on my work computer instead, as it's not out of the question there'll be other tools where I run into issues. My home machines are all still running ublue variants though (since 2022 if I recall correctly). Now I'm kinda drifting off-topic with regard to the main point though, which was about the missing gpg keys. As I said in the initial post the same error popped up when trying to layer Google Chrome. As I'm at my work PC at the moment running Workstation, I can't test right now. But I can give it a shot this evening when I'm at my laptop (running the UBlue Base image, no layers). |
Just to re-iterate, the report was not about VirtualBox (which I know is unsupported), but the error popped up at any RPM-Fusion package (see google chrome). Honestly I'm assuming it has been resolved by now, if not purely due to the lack of more reports. But I can double check this evening. |
Just checked on my private work laptop, and still getting the same issue with e.g. chrome as well:
Here's the image I've got, base image no layers on this machine either:
|
Hey,
I was trying to get VirtualBox to work on my install (universal blue base image with nvidia), however it seems like I'm running into issues with anything that has to do with rpm-fusion. I need VirtualBox specifically as part of a course I'm following through my employer (there's set-up images available in the course which we ought to use), so going with some KVM tool is not an option.
In short, when I try to install virtualbox, I'm getting:
As far as I understood (and these logs seem to kinda confirm this), rpmfusion is enabled by default in ublue. But after this error, I wanted to check what happens if I try to add them manually, maybe that would shake things into place and go through the proper procedues with regard to signing these keys:
But the same issue occurs. As this seems to be coupled to the repo setup, and this is an immutable distro, I think this is the proper place to file this issue as it looks like a misconfiguration. However, I don't rule out this being an upstream issue at rpm-fusion or even just Fedora Silverblue, so feel free to close this issue if that is the case.
Edit: Seems like VirtualBox might be somewhat problematic due to requiring out-of-tree kernel modules, but that seems to be unrelated to the issue here. I'm getting the same result with
rpm-ostree install google-chrome
for instance.The text was updated successfully, but these errors were encountered: