How to Submit Effective Bug Reports for GNOME Packages in Fedora

Introduction

If you’ve ever reported a bug against a GNOME package in Fedora, you’ve likely received an automated response stating the report isn’t actively monitored and suggesting you file the issue with GNOME upstream. This practice has caused friction with the Fedora Engineering Steering Committee (FESCo) policy, which requires maintainers to handle bugs in a timely manner. In April, FESCo discussed the disconnect and opted only to tweak the auto-reply wording. This guide will walk you through the correct process to ensure your bug report gets the attention it deserves, while respecting both Fedora’s and GNOME’s workflows.

How to Submit Effective Bug Reports for GNOME Packages in Fedora

What You Need

A Fedora Account (for the Fedora Bugzilla instance)
A GNOME GitLab account (for upstream bug tracking)
Basic understanding of the GNOME package you’re reporting against
Clear steps to reproduce the bug
System information (e.g., Fedora version, GNOME version, relevant logs)

Step-by-Step Guide

Step 1: Identify Whether the Bug Is Fedora-Specific or Upstream

Before filing anything, determine if the issue originates from Fedora’s packaging, configuration, or environment, or if it’s a general GNOME problem. For example, a crash in the GNOME Control Center that only happens on Fedora with a particular kernel module is likely Fedora-specific. A missing feature in a GNOME core app is usually an upstream issue. Check existing Fedora bug reports and upstream GitLab issues to avoid duplicates.

Step 2: File Upstream First If Appropriate

If the bug is clearly an upstream GNOME problem, file it directly on GNOME GitLab. This is what the Fedora auto-reply suggests and it aligns with best practices: upstream developers can fix the root cause, and Fedora can then pull the fix. Provide a detailed description, steps to reproduce, and attach logs. Tag the appropriate component.

Step 3: File in Fedora Bugzilla for Fedora-Specific Issues

If the bug is Fedora-specific (e.g., packaging error, distro patch regression), use the Fedora Bugzilla. Choose the component matching the GNOME package. Be explicit that this is a Fedora-side issue. The auto-reply you receive is a standard message; don’t interpret it as dismissal. It merely says the Fedora team may not actively monitor every package bug, but the FESCo policy still expects timely handling.

Step 4: Monitor the Auto-Reply and Follow Up

When you file in Fedora Bugzilla, you’ll get the automated response stating the bug is “not actively monitored” and suggesting upstream reporting. This message is being revised by FESCo to reduce confusion. In the meantime, do not assume your bug is ignored. Add a comment if you don’t hear back within two weeks, referencing the FESCo policy (link). You can also reach out to the package maintainer via the Fedora devel list or tag the bug appropriately.

Step 5: Use Keywords and Tagging to Attract Attention

To make your report more visible, add keywords like “Fedora-specific” or “regression” in the bug title or description. Use the ‘Whiteboard’ field to note “FESCo-policy: needs timely handling”. This helps maintainers prioritize. Also, if the bug is already filed upstream, include a link to the upstream report to avoid duplicate work.

Step 6: Engage with the Community if Stalled

If your bug remains unresolved and the auto-reply has not been followed by any human interaction, consider posting on the Fedora Forums or the GNOME Discourse. Politely ask for an update, referencing the bug ID and the FESCo policy expectation. Maintainers appreciate constructive follow-ups. Avoid pinging multiple times in a short period.

Tips for Success

Check the FESCo policy – It’s public and states that maintainers “deal with reported bugs in a timely manner.” If you feel ignored, you can escalate to FESCo.
Use the correct component – For example, gnome-shell is a common component. Wrong components lead to longer delays.
Attach logs and screenshots – Detailed evidence speeds up triage.
Avoid filing duplicate bugs – Search both Bugzilla and GitLab before creating a new report.
Understand the auto-reply – It’s being improved, but for now it’s a standard notice. Don’t let it discourage you.
Be patient but persistent – Fedora and GNOME are volunteer-driven projects; respectful follow-ups work best.