File a Bug to Fedora? How to Report Issues

Yes, you should file a bug to Fedora when you find a genuine problem, and the process is straightforward: use the Bugzilla instance at bugzilla.redhat.com, search for an existing report first, and if none exists, create a new one with clear reproduction steps. This article explains exactly how to do that, what information to include, and what happens after you submit.

What Is Fedora’s Bug Tracking System?

Fedora uses Red Hat Bugzilla, a web-based bug tracker that has been in use for decades. It is the same system used by Red Hat Enterprise Linux, and it is the official place where developers, testers, and users report defects, request features, and track progress. While Fedora also has discussion forums and mailing lists, Bugzilla is the authoritative channel for bug reports. When you file a bug there, it becomes visible to package maintainers, quality assurance volunteers, and other users who might have the same issue.

Each bug report gets a unique number, a severity rating, and a status that changes as it is triaged, assigned, fixed, and verified. The system is public, so anyone can search and comment on bugs, but only registered users can file new ones. Creating an account is free and only requires a valid email address.

Before You File: Search First

The single most important step is to search for an existing bug before creating a new one. Duplicate reports waste maintainers’ time and split the discussion across multiple tickets. To search effectively:

• Go to bugzilla.redhat.com and click “Searchâ€� in the top menu.
• Use the “Advanced Searchâ€� and set the Product to “Fedoraâ€�.
• Enter keywords that describe the symptom, not your guess at the cause. For example, if GNOME Settings crashes when you change the wallpaper, search for “GNOME Settings crash wallpaperâ€� rather than “gsettings segfaultâ€�.
• Filter by status: include “NEWâ€�, “ASSIGNEDâ€�, and “ON_DEVâ€� to see open bugs; also check “CLOSEDâ€� to see if the issue was already fixed or rejected.
• If you find a bug that matches, add a comment with your system information and a “me tooâ€� if you can reproduce it. Do not file a new one.

If you are unsure whether your issue is a bug or user error, ask on the Fedora Ask forum or the relevant mailing list first. Maintainers appreciate when users have already ruled out configuration problems.

Step-by-Step: How to File a Bug

Once you have confirmed the bug is not already reported, follow these steps:

1. Create an account at bugzilla.redhat.com if you do not have one. Use a real email address; you will receive updates there.
2. Log in and click “New� in the top menu, then select “Fedora� as the Product.
3. Choose the correct Component. This is the package or subsystem that is failing. If you are unsure, use the package name from the error message or run rpm -qf /path/to/file to find which package owns a file.
4. Fill in a concise, descriptive Summary. Good: “gnome-shell crashes when toggling dark mode�. Bad: “Something is broken�.
5. Write a detailed Description that includes:
   • The exact version of Fedora (e.g., Fedora 40) and the package version (from rpm -q packagename).
   • Your hardware and environment (CPU, GPU, desktop environment, Wayland or X11, etc.).
   • Steps to reproduce, from a clean state. Number them.
   • What you expected to happen and what actually happened.
   • Any error messages, crash logs, or screenshots. Attach files if they are small.
6. Set the Severity. Use “high� for crashes or data loss, “medium� for major functionality broken, “low� for minor annoyances. Most bugs are “medium�.
7. Click “Submit Bug�. You will get a bug number immediately.

Be prepared to answer follow-up questions. Maintainers often ask for additional logs or test commands. The more cooperative you are, the faster the bug gets resolved.

What Happens After You Submit?

After submission, your bug enters the triage queue. A Fedora contributor (often the package maintainer or a bug triager) will review it. They may:

• Confirm the bug and assign it to a developer.
• Ask for more information if the report is incomplete.
• Mark it as a duplicate of an existing bug.
• Close it as “NOTABUGâ€� if it is user error or a feature request.
• Move it to “ON_DEVâ€� when someone starts working on a fix.

You will receive email notifications for every status change. If the bug is fixed, it will be marked “MODIFIED�, then “ON_QA� for testing, and finally “CLOSED� with a resolution like “CURRENTRELEASE� (fixed in a recent update) or “ERRATA� (fixed in a future release). You can comment on the bug at any time to provide additional info or test the fix.

It is important to note that not all bugs get fixed quickly. Some low-priority issues may remain open for years. If your bug is urgent, you can escalate by commenting politely and asking for a maintainer’s attention, but avoid spamming.

Common Mistakes and How to Avoid Them

Many bug reports are low quality, and maintainers appreciate well-written ones. Avoid these pitfalls:

• Vague summaries like “Update breaks everythingâ€�. Instead, say “NetworkManager fails to connect to WPA2-Enterprise after update to 1.44â€�.
• Missing reproduction steps. Always include a numbered list of actions that lead to the problem. If you cannot reproduce it consistently, say so.
• Insufficient system info. Include the output of uname -a, cat /etc/fedora-release, and the package version. For graphical issues, mention your GPU and driver.
• Attaching huge files. If a log is large, compress it or paste only the relevant portion. Do not paste entire config files unless asked.
• Reporting multiple bugs in one ticket. File separate bugs for separate issues, even if they seem related.
• Using the bug tracker for support. If you just need help, use Ask Fedora or the mailing lists. Bugzilla is for confirmed defects.

Another common misconception is that you must be a developer to file a bug. That is false. Fedora explicitly encourages end-user bug reports. Even if you cannot diagnose the root cause, a clear description of the problem and how to reproduce it is extremely valuable.

Alternatives to Bugzilla

While Bugzilla is the primary channel, there are other ways to report issues:

• Fedora Discussion – For community support and to confirm whether others see the same problem before filing.
• Package maintainer email – Some maintainers prefer direct contact for minor issues, but always use Bugzilla for anything that needs tracking.
• Red Hat Issue Tracker – For Red Hat Enterprise Linux, but Fedora bugs are still on Bugzilla.
• GitLab – Some individual projects (like the Fedora website) use GitLab issues, but the official bug tracker remains Bugzilla.

If you are unsure where to report, Bugzilla is always a safe bet. The maintainers will redirect you if needed.

Frequently Asked Questions

Do I need a Red Hat account to file a bug?
Yes, you need a free account on bugzilla.redhat.com. It takes less than a minute to create and only requires an email address.

What if I don’t know which package is causing the problem?
Try to identify the package from the error message or by running rpm -qf on the executable or file involved. If you cannot, describe the symptom and the component field can be set to “Otherâ€�. Maintainers will help re-categorize.

Can I file a bug anonymously?
No, you must log in to file a bug. This is to prevent spam and to allow maintainers to contact you for more information.

How long does it take for a bug to be fixed?
There is no set time. Critical security bugs may be fixed within days, while minor issues can take months or years. It depends on the maintainer’s availability and the complexity of the fix.

What should I do if my bug is closed as NOTABUG?
Read the comment from the maintainer. If they explain it is user error, try their suggestion. If you believe it truly is a bug, you can reopen it with additional evidence, but do so respectfully.

Is it okay to file a bug for a feature request?
Yes, but use the severity “enhancement� and clearly state that it is a request, not a defect. Many features start as bug reports.

Related

• Claude Smart Home Access: Is It Really Scary?
• Smart Home Purchases I Won’t Make Again
• NEC Residential Load Calculator: How It Works

in t | Time to reproduce (minutes) | min | 10 | 0
in s | Steps to reproduce | - | 3 | 0
out r | Report quality score | /10 | min(10, t / 5 + s) | 1