Breaking News: Fedora GNOME Bug Reports Are Not Being Actively Monitored – FESCo Responds with Minor Wording Change
For years, users submitting bug reports against GNOME packages in Fedora have received an automatic reply stating their reports are not actively monitored. Instead, they are directed to file bugs with GNOME upstream. This practice has now come under fire for directly conflicting with the Fedora Engineering Steering Committee (FESCo) policy requiring package maintainers to “deal with reported bugs in a timely manner.”
On April 28, FESCo held an urgent discussion to address the gap between stated policy and actual practice. Yet, sources confirm the committee’s only action so far has been to adjust the wording of the automated response—leaving deeper systemic issues untouched.
Background
Fedora’s FESCo policy mandates that all package maintainers handle bugs promptly. However, for GNOME packages, the automated reply has long implicitly exempted Fedora maintainers from that obligation. “It was a convenience measure that became a policy loophole,” said Alex Fedora, a longtime Fedora contributor. “Users felt abandoned—they’d follow Fedora’s reporting guidelines, only to be sent elsewhere.”
The disconnect was flagged by community members in early 2024, gaining momentum as more users reported receiving the canned response for critical bugs. The issue escalated to FESCo’s agenda after multiple maintainers admitted they lacked the resources to monitor both Fedora and GNOME bug trackers.
What This Means
The committee’s decision to only tweak wording suggests a reluctance to overhaul the bug-monitoring pipeline. According to a FESCo member who spoke on condition of anonymity, “We recognize the policy conflict, but a full solution would require either assigning dedicated Fedora GNOME maintainers or integrating Fedora’s tracker with GNOME’s—both costly and time-consuming.”
For now, users will still see an automated reply, but with revised language that acknowledges Fedora may eventually review reports “at its discretion.” Critics argue this falls short. “A subtle word change does not fix the broken promise of timely bug handling,” stated Dr. Sarah Linux, a Fedora community advocate. “It only masks the problem.”
Community Reaction and Next Steps
Fedora’s GNOME user base has expressed frustration in forum threads and bugzilla comments. Many feel the committee is prioritizing convenience over quality. “If Fedora can’t monitor GNOME bugs, it should stop claiming it does,” wrote one user in a high-traffic discussion.
FESCo has promised to revisit the issue in a follow-up meeting within 30 days. In the meantime, users are advised to file bugs directly with GNOME upstream and to tag Fedora-specific issues with a special label to ensure visibility.
This is a developing story. Stay tuned for updates as FESCo’s next meeting approaches.