Where do I report an issue with the missing RPM?

Ask Fedora
, ,
1

Hi! I wanted to ask where do I report the missing RPM?

I suppose I need to add more of a context to the issue

So, the issue which I encountered a few months ago (3 months ago if to be precise) is that I couldn’t install Steam from RPMFusion using GUI, same with Nvidia drivers (although I do not use them - they were still impacted as I couldn’t see them anymore as well), so, I did my little investigation into what is going on which you can find in my Reddit post here: Reddit - Please wait for verification (You can also see all of the troubleshooting in the comments under the post as well)

After I got some free time I just asked myself again “Why should I use console when previously I could’ve used my App center to install Steam RPM?”

So it led me here, as after I reviewed the issue again, and now also reviewed the documentation onto how to report a bug - I needed to choose a particular RPM with which I had an issue, and… Yeah, how do I report an issue with a missing RPM within a system which requires to choose a particular RPM?

2

You would report that against the app that cannot install the RPM you want.
gnome-software of plasma-discover., etc depending on which desk top you are using.

3

Just to clarify, my issue is with rpmfussion appstream rpm which impacts both gnome-software, and plasma-discover, do I fill two bug reports or the one I see fit? As this issue is basically common to any fedora spin and impacts all of the methods of installations, as the package is seemingly missing from the repository itself

4

According to the Reddit thread, you did not have the rpmfusion-free-appstream-data package installed.

If you haven’t yet installed that, try installing it and the corresponding nonfree package.

Per the RPMFusion docs, this command should work:

sudo dnf install rpmfusion-\*-appstream-data
5

It’s present as far as I can see:

$ dnf list "rpmfusion*appstream*" --available
Updating and loading repositories:
Repositories loaded.
Available packages
rpmfusion-free-appstream-data.noarch    43-2.fc43 rpmfusion-free-updates
rpmfusion-nonfree-appstream-data.noarch 43-2.fc43 rpmfusion-nonfree-updates
6

I did not receive the same result, it says No matches found

7

Interesting, which RPMFusion repos do you have configured?

dnf repolist | grep rpmfusion

I get:

rpmfusion-free                                                      RPM Fusion for Fedora 43 - Free
rpmfusion-free-updates                                              RPM Fusion for Fedora 43 - Free - Updates
rpmfusion-nonfree                                                   RPM Fusion for Fedora 43 - Nonfree
rpmfusion-nonfree-updates                                           RPM Fusion for Fedora 43 - Nonfree - Updates
8

Can you give specific commands for rpm-ostree? I am right now on Fedora Kinoite temporarily, but will check this for Fedora Workstation really soon as well

9

For Kinoite, you can check which repos you have configured by running rpm-ostree status.

If the RPMFusion repos are correctly installed, you should see something like:

LocalPackages: rpmfusion-free-release-43-2.noarch rpmfusion-nonfree-release-43-2.noarch

However, AFAIK (someone who knows Atomic Desktops better can correct me if I’m wrong), you wouldn’t expect to see any RPM packages in Discover in Kinoite. The intention in Kinoite and other atomic Fedora variants is that all your normal software installs are Flatpaks. “Installing” RPMs (i.e. layering them into your deployment) is a special-case process that uses the command line.

10 
                      ├─ copr:copr.fedorainfracloud.org:phracek:PyCharm (2026-02-24T05:51:20Z)
                       ├─ fedora (2026-04-14T08:46:01Z)
                       ├─ fedora-cisco-openh264 (2026-03-24T10:37:04Z)
                       ├─ rpmfusion-nonfree-nvidia-driver (2026-04-02T15:26:48Z)
                       ├─ rpmfusion-nonfree-steam (2026-03-21T10:06:58Z)
                       ├─ updates (2018-02-20T19:18:14Z)
                       └─ updates-archive (2026-02-07T16:15:35Z)

It is possible to install steam using rpm-ostree install steam - yes, but nothing in GUI stores…

11

Understandable, but I still encounter this bug on fedora workstation, and by manually adding repos from rpmfusion website, and installing manually metadata through that repo - they appear and work through GUI stores

12

So they do appear and work when you follow the documented procedure?

13

Only when using manual procedure from rpmfusion website, previously - it worked by turning on the Enable Third Party Repositories button (which is linked to a simple rpm fedora-third-party, which I queried with running it in a console with added flag -v to have verbose logs and it was notifying me of some errors of fetching some packages as those do not exist)

Maybe it is regional issue? I am not living in the US or NA after all

14

OK, this would have been ideal information to put in your first post :grinning_face:

So, rereading your original question in the light of this, I think you want to know how to categorise this in Bugzilla? I think it should be:

  • Product: Fedora
  • Component: fedora-third-party

There’s no requirement to specify a specific RPM package beyond the component.

15

Okay, now I got the access to my second machine and now I am full on CS major it seems, running those commands on Fedora Workstation, Fedora Kinoite, AND Silverblue - causes No matching packages, as to the command to which you said later (dnf repolist one) I have the following EXACT output:

rpmfusion-nonfree-nvidia-driver
rpmfusion-nonfree-steam

16

In that case, you most likely need to enable the main RPMFusion repos too.

sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

Then reboot, then install the appstream data:

sudo dnf install rpmfusion-\*-appstream-data
18

That fixed it for me! Thank you very much for help! I just wanted to say that it also fixed itself with a new update apparently on a different machine.. (For a testing purposes I had 3 machines at hand, with 2 additional virtual machines trying to debug this stuff, basically - the installations which were done a few months ago - have been fixed with the instruction which you gave as the issue persisted even after being updated, and the new, fresh installation of Fedora Workstation 43 needed no fix after the update)

Oh well, I guess Linux is just like that sometimes… :sweat_smile: anyways, I am really grateful for your help, and support! Thank you for sticking with me till the end!