How to report selinux issues?

On my machine (Fedora Silverblue), I get quite a few selinux errors on every boot. I’d like to report them to get them fixed. Here is the current list:

SELinux is preventing bootupctl from read access on the directory /proc.
SELinux is preventing lsblk from read access on the file swaps.
SELinux is preventing lsblk from open access on the file /proc/swaps.
SELinux is preventing lsblk from getattr access on the file /proc/swaps.
SELinux is preventing usbguard-daemon from write access on the sock_file org.gnome.DisplayManager.
SELinux is preventing systemd-logind from getattr access on the directory /dev/shm/qb-1012-2367-14-k96UKU.

In addition to that, i’m getting a few errors like these:

SetroubleshootPrivileged.py[1403]: failed to retrieve rpm info for path '/etc/selinux/targeted/active/modules/100/bootupd':
setroubleshoot[1163]: failed to retrieve rpm info for path '/proc/swaps':
SetroubleshootPrivileged.py[2882]: failed to retrieve rpm info for path '/etc/selinux/targeted/active/modules/200/usbguard':
setroubleshoot[4427]: failed to retrieve rpm info for path '/dev/shm/qb-1012-2367-14-k96UKU':
SetroubleshootPrivileged.py[4456]: failed to retrieve rpm info for path '/etc/selinux/targeted/active/modules/100/systemd':

On my previous Fedora installation, I would use sealert (a GUI tool from package setroubleshoot), which would guide me to report a bug on Fedora’s section of Red Hat Bugzilla. If I remember correctly, that feature was using GNOME Abrt, which is now defunct and scheduled for removal from Fedora.

On my current Fedora installation, this doesn’t work any more. In the SELinux Alert Browser, after clicking on Report Bug, a bug report shows up:


After reviewing, I click Submit Report, but nothing happens (I just get an empty window):

The top left icon gives a context menu, opening a preferences dialog:

However, that dialog doesn’t seem like it provides any useful configuration.

What is the recommended way to report SELinux issues in 2026? Are we back to manually reporting these issues, manually creating bug reports in bugzilla? And if yes, how do I find out whether to report it against a selinux-policy package or other packages that are supplementing the selinux policy for these packages specifically?

Raise tickets in the fedora bug tracker - see Making sure you're not a bot!

Fedora uses bugzilla for bug tracking:

bugzilla.redhat.com

Following these steps in reporting is helpful:

Thanks! I just reported a few of them:

Some of the issues I am seeing were reported before already, especially against usbguard (which has its own subpackage -policy).